perplexity← Home

Your questions. Your choices.

Privacy policy

Updated 2 November 2026. Paid pilot availability is checked in Billing.

Review-account update: 2 November 2026. An operator-provisioned temporary review account additionally uses an application password stored as a salted password hash. This is separate from Google sign-in; we do not receive a Google password. Review access expires within seven days. Account/security records and saved test content are retained under the policies below until removed through the relevant support or deletion process; expiry does not promise immediate data erasure.

This notice describes the independent perplexity research application at perplexity.jacked.dev and its deployment-hosted entry. Contact the project operator at trainwithchirag@gmail.com about privacy or your data.

What we collect

Why we use it

We use this information to sign you in, keep conversations private to their owner, retrieve sources, generate and check answers, save history, process feedback, enforce quotas, prevent abuse and diagnose failures. Basic Google profile details are used for account access; they are not automatically added to AI prompts. Information you include in a question may be sent to research providers.

Who processes research data

These services have their own privacy policies and operational obligations. Infrastructure and providers may process data outside India; the production database is configured in Singapore. We do not sell user data or use it for advertising.

Payments and durable research

When paid checkout is available, Razorpay collects payment-method and mandate details directly in its checkout. The application will retain subscription, invoice and payment identifiers, payment state, verified paid-through dates, cancellation status, limited signed-event records and usage counters to provide access and reconcile payments. We do not store card numbers, CVVs or payment PINs. Payment and reversal records may remain after content deletion for financial reconciliation and to prevent duplicate grants.

Deep Research uses private saved questions, step checkpoints, progress and cited reports. Trigger.dev hosts the configured durable worker and receives job identifiers and execution data; its environment is separate from the browser. Access and new purchases depend on the configured paid offer and funded capacity.

Cookies and guest sessions

Essential cookies keep you signed in and protect account actions. Sessions have a seven-day rolling validity and a separate thirty-day absolute limit. A guest-trial marker lasts thirty days to prevent repeated free grants. Turnstile may use its own browser verification mechanisms. Clearing cookies can remove access to unlinked guest history; sign in with Google to retain that history.

Retention and deletion

Saved registered conversations remain until you delete them. Scheduled cleanup targets unlinked guest conversations, retrieved excerpts and private planning/non-content safety records after thirty days; cleanup occurs when the maintenance job runs. Approved answers retain citation links after excerpts expire.

For Deep Research, scheduled cleanup removes private evidence and intermediate checkpoints from terminal jobs after 24 hours. The approved report, its citation links and original question remain until you delete the research. Export is available on completed reports. Delete research stops active work and removes its saved question, report and private checkpoints; content-free tombstones, progress metadata and financial usage records remain to preserve settlement and replay protection.

Deleting a conversation removes its visible messages and associated research content from the active application database and stops active work from saving a late answer. Content-free deletion markers, abuse controls and financial usage records remain for reconciliation and replay protection. This does not promise immediate erasure from backups or third-party systems. Backup, security-log and external provider retention follow the applicable service settings and provider policies; contact us for current details or help with a deletion request.

Your choices

Use the conversation menu to export approved messages and citation links as JSON or to delete a conversation. Contact us for account-level access, correction or deletion requests; identity verification may be needed. You can revoke Google access in your Google Account, which does not itself delete saved conversations here. Do not submit credentials, confidential information or personal data you are not entitled to share.

Changes and contact

We will show a revised date when this notice changes. Material changes to how research data is used should be communicated before they take effect. Send questions or concerns to the contact address above.