Sourcegraph Cody and Amp

Data-handling profile

Trains on input

Unknown / not publicly stated

Retention

Cody Enterprise: zero data retention — partner LLMs do not retain input/output/embeddings beyond generation time, and customer code is never used to train models. SOC 2 Type II, GDPR, CCPA compliant; only anonymous usage metrics (no code content) collected. Amp Free Mode is ad-sponsored and uses behavioral/codebase-derived signals for ad relevance — data-handling terms for Amp specifically are less clearly documented than Cody Enterprise, so treat as unknown/mixed pending direct confirmation.

Data region

US

Certifications

SOC 2 Type II

DPA available

Yes

Breach history

none known

EU AI Act

Cody Enterprise's contractual zero-retention/no-training terms with model providers are strong for EU AI Act purposes; Amp Free Mode's ad-sponsorship model (data use for ad relevance) needs separate scrutiny before extending the same low-risk rating.

Sources

• https://sourcegraph.com/terms/cody-notice
• https://sourcegraph.com/blog/cody-is-enterprise-ready
• https://sourcegraph.com/terms/privacy
• https://sourcegraph.com/docs/cody/faq

Every fact above is drawn from the vendor's public documentation, reviewed by a human, and version-stamped. Monitored daily for changes.

Control mapping

Obligations this vendor triggers, each attributable to the fact it rests on — for your supplier register, not a compliance determination.

• EU AI Act Art. 50 — Transparency obligations for AI systemsunknown

  Vendor does not publicly state whether it trains on inputs. Unresolved: treat as a question for the vendor, not as a pass.

• EU AI Act Art. 26 — Obligations of deployers of high-risk AI systemsapplies

  Applies to your organisation as deployer, independent of vendor. Assign human oversight, keep logs, and monitor operation where this tool is used in a high-risk context (Annex III duties apply from 2 Dec 2027).

• ISO/IEC 27001 A.5.19 — Information security in supplier relationshipsapplies

  Sourcegraph Cody and Amp processes organisational data as a supplier. Include this vendor in the supplier register and risk assessment.

• ISO/IEC 27001 A.5.20 — Addressing information security within supplier agreementsok

  dpa_available = true. A data processing agreement is available and should be executed.

• ISO/IEC 27001 A.5.23 — Information security for use of cloud servicesapplies

  Cloud AI service; trains_on_input = unknown. Define acceptable-use and configuration rules for this cloud service.

• ISO/IEC 42001 A.10.3 — Suppliers of AI systems and servicesapplies

  certifications: SOC 2 Type II No AI-management certification identified; assurance must come from your own supplier assessment.

• GDPR Art. 44–49 — International transfers of personal dataattention

  data_region = US. Processing occurs outside the EU/EEA — a transfer mechanism (SCCs or adequacy) must be in place.

• NIS2 Art. 21(2)(d) — Supply chain securityapplies

  AI vendor forms part of your ICT supply chain. In scope for entities covered by NIS2; include in supply-chain risk measures.

• DORA Art. 28 — General principles for ICT third-party riskapplies

  AI vendor is an ICT third-party service provider. For financial entities: register of information and contractual requirements apply.

Change history

No material changes recorded since monitoring began.