When the business customer stops using Perplexity AI's services, the DPA typically requires Perplexity AI to delete or return personal data processed under the agreement, at the customer's choice, within a specified timeframe.
This analysis describes what Perplexity AI's agreement states, permits, or reserves. It does not constitute a legal determination about enforceability. Regulatory applicability and practical outcomes may vary by jurisdiction, enforcement context, and individual circumstances. Read our methodology
The deletion or return obligation ensures that personal data does not remain with Perplexity AI indefinitely after a contract ends. The scope of what is deleted, the timeline, and whether any exceptions exist (such as legal retention requirements) are material to assessing data governance risk.
Interpretive note: The specific deletion timeline, scope, and certification process defined in the DPA could not be confirmed from the truncated document text.
Business customers using Perplexity services are now governed by an updated DPA with two material operational changes. First, subprocessor disclosures have shifted from a static document attachment (Annex 2) to a live online list maintained at https://trust.perplexity.ai/subprocessors, with notifications of changes coming through in-product notification or email rather than through formal amendment. Second, certain Perplexity services (specifically Embeddings API and Perplexity Search) now operate under product-specific data postures and terms that control over the main DPA, meaning the data handling for those services may differ from the baseline agreement. Business customers should review the Trust Center list regularly and check for in-product notifications regarding subprocessor changes, as the updated terms no longer require static amendment cycles.
View change record →Individuals whose personal data was processed through a business's Perplexity AI integration should expect that data to be deleted from Perplexity AI's systems when the business terminates its relationship with Perplexity, subject to any legal retention obligations. The DPA governs the timeline and completeness of that deletion.
How other platforms handle this
If you use your Roblox ID to sign in to a non-Roblox website or service, and later delete your Roblox account, you may lose access to that website or service.
You agree to (a) provide accurate, current, and complete information as may be prompted by the registration forms via the Site ("Registration Data")...
Use another user's account or share your account with another person;
(1) REGULATORY LANDSCAPE: GDPR Article 28(3)(g) requires processor agreements to include deletion or return obligations upon termination.
Enforcement risk, jurisdiction flags, contract triggers, and due diligence action items.
Get the research letter
Companies change their terms quietly. We read every version and catch what actually changed. One email a week on the changes that matter and what they mean.
The deletion or return obligation ensures that personal data does not remain with Perplexity AI indefinitely after a contract ends. The scope of what is deleted, the timeline, and whether any exceptions exist (such as legal retention requirements) are material to assessing data governance risk.
Individuals whose personal data was processed through a business's Perplexity AI integration should expect that data to be deleted from Perplexity AI's systems when the business terminates its relationship with Perplexity, subject to any legal retention obligations. The DPA governs the timeline and completeness of that deletion.
ConductAtlas has identified this type of provision across 265 platforms. See the full comparison.
No. ConductAtlas is an independent monitoring service. We are not affiliated with, endorsed by, or sponsored by Perplexity AI.