Notion AI’s default no-training commitment does not mean no data is processed or stored. Before using it for confidential work, distinguish model training, provider retention, saved Notion content, search indexes and connected-app access. A claim that discarded output disappears immediately from every system is not supported.
How Notion AI Uses Workspace Context
Notion describes two processes: creating embeddings for workspace retrieval, and sending a request with relevant context to models that generate the answer. Providers are not limited to an unchanging pair of companies. Notion uses models hosted by itself and providers such as Anthropic and OpenAI; consult its current subprocessor list through the security and privacy documentation.
Notion Agent works within your existing permissions and can use pages, database content and approved connected sources. It also supports chat history. Therefore, “I did not insert the answer into a page” is not proof that no conversation record exists. See the Agent guide.
For an internal review, list the specific feature and sources you intend to use. A page-writing task, connector search, external agent and automated workflow can have different data paths.
Separate No Training From No Retention
Notion says it and its AI subprocessors do not train models on Customer Data by default, and its provider contracts prohibit such training. For provider retention, the default is zero retention for Enterprise workspaces and 30 days or fewer for non-Enterprise workspaces. Certain features require administrator-enabled data-retaining models, and External Agents have separate controls. These are qualified defaults, not a universal zero-storage promise. Read the current retention terms.
Provider retention is also separate from pages, chats and embeddings held for the Notion service. Do not make a procurement decision by reading one number in isolation. Ask your administrator or Notion representative to confirm the feature-specific terms that apply to your workspace, including any enabled exceptions and contractual requirements.
An old tutorial’s “Allow workspace data for model improvement” toggle is not a verified current procedure. Do not infer that training is enabled merely because you cannot find that invented setting.
Review Actual Controls and Connected Sources
- As workspace owner, open Settings → Notion AI and inspect the available controls. Document the current values before changing anything.
- Review Enable web search for workspace and Require confirmation for web requests. These govern web access, not all model processing.
- Inventory connected applications and their source permissions. Connect only the systems needed for the approved task, and verify who can see the underlying content.
- Check whether External Agents, data-retaining model options or automated agents are enabled. Evaluate their specific scope separately from ordinary Notion AI chat.
- Review the applicable processing terms and subprocessor list with the person responsible for privacy and security.
Enterprise Search’s privacy documentation describes indexing of connected sources and access filtering. Permission changes and deletion can require synchronization; do not assume an immediate global purge when a source permission changes. Verify the specific connector’s timing and controls.
A Practical Privacy Check Before Rollout
Test with synthetic documents and accounts that have deliberately different permissions. Confirm an ordinary user cannot retrieve restricted content, including through a connector. Record the source and role used in each test instead of relying on an administrator account that can already see everything.
Keep secrets and highly restricted records out of prompts unless the workflow has been explicitly approved for them. When reviewing an answer, check both correctness and whether sharing the new output could disclose source information to a broader audience.
Notion’s current AI access is generally included with Business and Enterprise, while other plans can have complimentary access; a flat historical add-on price does not describe today’s privacy or access model. Use the current AI FAQ for plan questions, and assess data handling independently of the price.
If your requirement prohibits processing by the relevant providers altogether, do not run the affected feature on that data while waiting for approval. A no-training clause alone does not satisfy that requirement. This is a product-control checklist, not a determination that a particular regulated workflow is compliant.
Official documentation checked: October 14, 2026.