Notion AI

Data-handling profile

Trains on input

No — does not train on customer inputs

Retention

States it does not train models on customer data; subprocessors used

Data region

US

Certifications

SOC 2 Type IIISO 27001

DPA available

Yes

Breach history

none known

EU AI Act

Embeds third-party GPAI (OpenAI/Anthropic)

By plan and surface

Vendor-level answers are often wrong for a specific tier. These are the precise claims, each with the verbatim sentence we relied on.

• enterprise/unknown: “When using Notion AI, by default our LLM providers utilize zero data retention for Enterprise plan workspaces, so no data is stored with LLM providers.”
• unknown/unknown: “In addition, by default for all non-Enterprise plan workspaces, LLM providers only retain Customer Data for 30 days or fewer before deletion.”

Sources

Everything above rests on a single document. That is not the same evidence as two independent documents agreeing. If the vendor moves or rewrites that page, the whole profile goes with it — treat these claims as uncorroborated and check them yourself before relying on them.

• https://www.notion.so/help/notion-ai-security-practices

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 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

  Notion AI 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 = 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, ISO 27001 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.