Perplexity updated its Perplexity Search Addendum, a search-specific addendum for its Search Services API, with important changes about how search data is used and retained. Why should you care if you use or plan to integrate its Search API? Because it defines rights, limits of liability and rules about data that affect developers, products and compliance. (perplexity.ai)

What the addendum says (key points)

• Version date: the document shows a recent update dated September 22, 2025. This is useful to know from when the changes apply. (perplexity.ai)

• Scope and priority: the addendum supplements and supersedes the general API agreement specifically for the Search Services. In other words, where there is a conflict between the base contract and this addendum, the latter takes priority over everything related to search. (perplexity.ai)

• Data use: Perplexity may retain, copy, distribute and use search data (Input and Output) for legitimate business purposes, including developing and improving its products. Also, that "Search Data" is not considered Customer Confidential Information. (perplexity.ai)

• Restriction on personal data: the addendum prohibits sending personal data to the search service unless Perplexity authorizes it in writing. If your app processes sensitive information or personal data, this changes how you integrate the API. (perplexity.ai)

• Disclaimers and limits of liability: the company makes clear that the Search Services are offered "as is", without warranties of any kind; it also limits its liability and notes that results may contain incorrect or biased information, so the customer must verify the accuracy of outputs. (perplexity.ai)

"The Search Services are provided 'as is' and without warranties of any kind.". (perplexity.ai)

• Nature of the output: the /search endpoint returns indexed results of public content (snippets, URLs, titles, metadata) and does not generate responses using large language models. That implies different rules about intellectual property and warranties regarding outputs. (perplexity.ai)

What does this mean for developers, companies and products?

If you integrate Perplexity's Search API, there are practical decisions you need to make:

• Data assessment: avoid sending personal or sensitive data unless you have explicit authorization; review your data flows and your forms so you don't violate the addendum. (perplexity.ai)

• Ownership and use of output: you will not receive an assignment of ownership over search results. If your product depends on guaranteeing exclusivity over content, you need to rethink that or negotiate different terms. (perplexity.ai)

• Human verification: since Perplexity warns about inaccuracies and biases, add human verification steps when results affect critical decisions (legal, medical, financial). This isn't optional if you require rigor. (perplexity.ai)

• Legal risk and compliance: if your service operates in regions with strict regulations (for example, data protection), consult your DPA and consider additional clauses with Perplexity or technical alternatives to anonymize inputs. (perplexity.ai)

Practical recommendations and quick checklist

1. Review the addendum in full and compare it with your current contract. Read the sections on Search Data, Personal Data and Limitation of liability. (perplexity.ai)

2. Identify in your stack which requests hit the /search endpoint and what type of data they contain. If there is personal data, remove or pseudonymize it before sending. (perplexity.ai)

3. Add a layer of source verification in the frontend or backend: show URLs and metadata so a human can verify before trusting a result. (perplexity.ai)

4. If you need additional guarantees (service levels, non-retention, IP indemnities), negotiate a separate agreement with Perplexity instead of relying only on the standard terms. (perplexity.ai)

Where to read the official text

You can consult the addendum directly on Perplexity's legal page to see the full text and exact clauses: Perplexity API Terms and Conditions - Perplexity Search Addendum. (perplexity.ai)

This news isn't just legal paperwork: it forces you to think about data design, responsibility and user experience. Does your team already have a plan to avoid sending personal data to external APIs? If not, this addendum is the signal to prioritize that now.