Perplexity enterprise and the Sonar API
The developer documentation states that Perplexity does not use customer data to train its models or for any purpose beyond processing the immediate request, and maintains a zero data retention policy for the chat completions API. Only billing metadata is kept, with no prompt or response content. The document reached governs the API rather than a seat licence.
The verdict
Verified
The document exists. The ledger fetched it at its publisher and quotes it.
Key facts
What the sources say
- Record ID
- AVD-2026-0023
- Kind
- Business tier
- Jurisdiction
- United States
- Last verified
- Added
- The developer documentation states Perplexity does not use customer data to train its models or for any purpose beyond processing the immediate request.
- Perplexity maintains a zero data retention policy for the chat completions API and does not retain data sent through it.
- Only billing metadata is collected, being token counts, model used, request timestamp and duration and the API key identifier, and it carries no prompt or response content.
- The page names a SOC 2 Type II report, a HIPAA gap assessment and a CAIQlite assessment.
Dimension by dimension
10 dimensions, each one stated, silent or open
Used for training by default, Retention period, Deletion on request, Storage region and residency, Subprocessor list published, Human review of content, Opt out available, DPA available, Persistent memory across sessions, Last change to the terms. Stated means the document you can open below says it; silent means the ledger read the document and it does not.
- Used for training by defaultStated
- No. The documentation states Perplexity does not use customer data to train its models or for any purpose beyond processing the immediate request.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- Retention periodStated
- Zero for content on the chat completions API. Billing metadata is kept and is described as carrying no content from prompts, responses or other user data.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- Deletion on requestSilent
- No deletion process is described because no content is retained to delete. The page addresses retention rather than a deletion right.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- Storage region and residencySilent
- No storage region or residency commitment is printed on the developer page. The consumer notice describes transfers to the United States under the data privacy framework.Perplexity privacy notice, primary source, 8 July 2026.
- Subprocessor list publishedStated
- A subprocessor notification subscription is published in the legal centre, and the developer page directs readers to the trust centre for the list itself.Perplexity privacy notice, primary source, 8 July 2026.
- Human review of contentSilent
- No human review is described on the developer page or in the legal centre notice.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- Opt out availableStated
- Nothing to opt out of. Zero data retention is presented as the standing posture of the API rather than a setting the customer enables.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- DPA availableStated
- A data processing addendum is published in the legal centre, and the privacy notice states it does not cover the enterprise and API offerings, which the addendum governs instead.Perplexity privacy notice, primary source, 8 July 2026.
- Persistent memory across sessionsSilent
- No memory feature is described for the API or the enterprise tier.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
- Last change to the termsSilent
- The developer privacy and security page prints no date at all. The privacy notice in the legal centre prints Last updated 8 July 2026.Perplexity developer documentation, privacy and security, primary source, 15 September 2026.
What it changes
For a buyer or a workplace AI policy
The strong no training and zero retention language here belongs to the API documentation, which is not the same instrument as a seat licence. If you are buying enterprise seats, ask for the commitment in the enterprise agreement rather than citing a developer page, and note that the page carrying the strongest statements carries no date, so you cannot tell from its face when it last changed.
Sources
What this record was verified against
- Perplexity developer documentation, privacy and securityPrimary · 15 September 2026
- Perplexity privacy noticePrimary · 8 July 2026
Related
Records that sit beside this one
Perplexity on the free and paid consumer plans
United States · verified 15 September 2026
The privacy notice lists improving or creating services and products, including its AI models, among the uses of data collected.
Does zero data retention survive an abuse investigation?
Global · verified 15 September 2026
OpenAI states a flagged image is retained for manual review even where zero data retention, modified abuse monitoring or eyes off is enabled.
Amazon Bedrock
United States · verified 15 September 2026
Amazon Bedrock uses a zero data retention security model, so by default it does not store model inputs or outputs.
GitHub Copilot Business and Enterprise
United States · verified 15 September 2026
GitHub states it does not use Copilot Business or Copilot Enterprise customer data to train AI models.
Cursor and its privacy mode
United States · verified 15 September 2026
The terms of service state that Cursor will not use content to train any AI models unless you have explicitly agreed.
The Grok API and enterprise platform
United States · verified 15 September 2026
The enterprise FAQ states the vendor does not use business data, including inputs or outputs, to train its models.
Cite this record
Free to reuse under CC BY 4.0, with attribution. The record ID AVD-2026-0023 is permanent and is never reused.
- In a sentence
- According to the GAGE AI Vendor Data Ledger (as of 15 September 2026), perplexity enterprise and the sonar api.
- APA
- GAGE (Global Academy of Generative-AI Education). (2026). Perplexity enterprise and the Sonar API. AI Vendor Data Ledger. Retrieved 15 September 2026, from https://www.gage.academy/tools/ai-vendor-data-ledger/records/AVD-2026-0023-perplexity-enterprise-and-sonar-api
- MLA
- "Perplexity enterprise and the Sonar API." AI Vendor Data Ledger, GAGE (Global Academy of Generative-AI Education), 15 September 2026, https://www.gage.academy/tools/ai-vendor-data-ledger/records/AVD-2026-0023-perplexity-enterprise-and-sonar-api.
- Chicago
- GAGE (Global Academy of Generative-AI Education). "Perplexity enterprise and the Sonar API." AI Vendor Data Ledger. Last modified 15 September 2026. https://www.gage.academy/tools/ai-vendor-data-ledger/records/AVD-2026-0023-perplexity-enterprise-and-sonar-api.
- Permalink
- https://www.gage.academy/tools/ai-vendor-data-ledger/records/AVD-2026-0023-perplexity-enterprise-and-sonar-api
Last updated . Every record re verified . The ledger is checked weekly, every Monday, and the same day for any terms change a vendor announces.
Back to the full ledger, or every record for United States and every business tier record.
GAGE briefings tell you which AI regulation deadlines are coming, what they actually require of you, and when a program opens.