Does your organization use Perplexity? One sensor, and Openwake watches it on its own: the documents re-read daily, every moved clause told.Start free
Perplexity did not let our reader in: privacy policy (HTTP 403), dpa (HTTP 403), terms (HTTP 403). Facts below come only from what was readable; anything marked "not stated" may simply be behind that block. We retry daily and rebuild the record the moment the documents open. Work for Perplexity? Claim the profile and send us the text.
Trains on customer data
Training posture: does not train
for the product and account type the quoted document covers
“* No training by default: Under the API Terms of Service, Perplexity does not use Customer Content to train generative AI models.”
Opt-out mechanism
none described
Not stated in the documents we could read. An absence here is an unknown, not a no.
AI features
present
“* No training by default: Under the API Terms of Service, Perplexity does not use Customer Content to train generative AI models.”
Model providers named
none named
Not stated in the documents we could read. An absence here is an unknown, not a no.
Retention
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Hosting regions
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Subprocessor notice
not stated
Not stated in the documents we could read. An absence here is an unknown, not a no.
Downstream
Who's behind Perplexity, as listed in its own subprocessor documents. none listed.
Model providers
- none listed
Hyperscalers
- none listed
Other subprocessors
- none listed
Reviewer notes
Extracted by deterministic rules (rules/v1), no language model. Coverage is limited to recognisable clauses and a gazetteer of common subprocessors; absent values mean 'not matched', not 'not present'.
Documents read
- privacy policy https://www.perplexity.ai/hub/legal/privacy-noticeHTTP 403 · 2026-10-22
- subprocessors https://trust.perplexity.ai/subprocessorsHTTP 200 · 2026-10-22
- dpa https://www.perplexity.ai/hub/legal/dpaHTTP 403 · 2026-10-22
- terms https://www.perplexity.ai/hub/legal/terms-of-serviceHTTP 403 · 2026-10-22
- ai policy https://docs.perplexity.ai/docs/resources/privacy-securityHTTP 200 · 2026-10-15
Document changes
- high 2026-10-15 · ai policy +9 / −10 lines
show diff
+ API PRIVACY & SECURITY+ Perplexity’s API Platform is designed to process Customer Content to provide the requested API service. Retention, use, and security practices vary by API, model, and account configuration, so this page should be read together with the API Terms of Service, applicable product-specific terms, the Data Processing Addendum, and any written agreement between you and Perplexity.+ * No training by default: Under the API Terms of Service, Perplexity does not use Customer Content to train generative AI models. Certain APIs may be subject to product-specific terms.+ * Zero Data Retention is not default: ZDR is available only to eligible customers through an account-level configuration under a written agreement with Perplexity. If ZDR has not been enabled for your account, do not assume that Perplexity or its model providers apply zero data retention to your requests.+ * Model-specific limitations: Not every model supports ZDR. Where ZDR is enabled for an Agent API account, only models whose providers support ZDR may be used; requests to unsupported models will return an error.+ * Third-party model terms apply: Models served by third-party providers are also subject to those providers’ terms and policies. Some providers require limited retention as a condition of offering their models.+ * Service and account data: Perplexity collects limited usage metadata—such as request and token counts, model used, timestamps, duration, and API key—to operate and bill the service, along with account information such as name and email address.+ * Personal data: Perplexity processes personal data in accordance with its Data Processing Addendum, and information about subprocessors is available on Perplexity’s Trust Center.+ This section is provided for convenience and does not modify the API Terms of Service, product-specific terms, the Data Processing Addendum, third-party model provider terms, or any other agreement between you and Perplexity. Where those documents differ, they control.− DATA PRIVACY & RETENTION− ZERO DATA RETENTION POLICY− Perplexity maintains a strict Zero Data Retention Policy for the Chat Completions API. We do not retain data sent through the Chat Completions API, and we do not use customer data to train our models or for any purpose beyond processing the immediate request.− DATA WE COLLECT− The only data we collect through the Chat Completions API consists of essential billable metrics required for service operation:− * Number of tokens processed− * Model used for each request− * Request timestamp and duration− * API key identification (for billing purposes)− This billing metadata does not include any content from your prompts, responses, or other user data. - medium 2026-10-13 · ai policy +0 / −7 lines
show diff
− > DOCUMENTATION INDEX− > Fetch the complete documentation index at: /llms.txt− > Use this file to discover all available pages before exploring further.− Privacy & Security− Copy pageCopy page− Responses are generated using AI and may contain mistakes.− What is the Agent API?Which Agent API model should I use?How do I create an API key?
Fact changes
- low 2026-10-15 · 1 field change(s), +0/−0 subprocessors, +0 model providers
Corrections
No correction requests. Anyone may dispute a fact with a source; requests and resolutions are public and ledger-entered.
Facts are as stated in Perplexity's public documents on the date read. This is a record, not legal advice. Work for Perplexity? Claim this profile · Something wrong? Request a correction.