Replicate

Data-handling profile

Trains on input

No — does not train on customer inputs

Retention

Predictions (inputs and outputs) are stored indefinitely unless explicitly deleted by the user via the API or dashboard; standard system and execution logs are retained for 30 days.

Data region

United States (AWS)

Certifications

SOC 2 Type II

DPA available

Yes

Breach history

In April 2024, Replicate resolved a container-escape vulnerability that could have allowed unauthorized access to other customers' private model inputs and API tokens. No evidence of active exploitation by malicious actors was found.

EU AI Act

As an AI model hosting and infrastructure provider, Replicate acts as a hosting platform. Compliance obligations under the EU AI Act largely fall on the developers and deployers who build and configure the specific models hosted on the platform.

Sources

• https://replicate.com/privacy
• https://replicate.com/terms
• https://replicate.com/blog/container-escape-vulnerability-patchedlink no longer resolves

Every fact above is drawn from the vendor's public documentation, reviewed by a human, and version-stamped. Monitored daily for changes. 1 of these 3 links no longer resolve. We record what we relied on rather than deleting it, so the trail stays auditable — but a struck-through source cannot be re-checked today.

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 systemsok

  trains_on_input = no. Vendor states inputs are not used for training.

• 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

  Replicate 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.22 — Monitoring, review and change management of supplier servicesattention

  breach_history: In April 2024, Replicate resolved a container-escape vulnerability that could have allowed unauthorized access to other customers' private model inputs and API tokens. No evidence of active exploitation by malicious actors was found. Prior incident on record — justify continued use and monitor.

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

  Cloud AI service; trains_on_input = no. 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 = United States (AWS). 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.