Data retention

Account deletion

Our operating target is to complete verified deletion requests within 30 days. Submitting a request is not immediate deletion. We revoke current sessions and remove active relay data when a signed-in deletion request is accepted. Account and linked support, device, trial and promotion records are removed during fulfillment.

Paid accounts, subscriptions and security-sensitive administrative records require manual review. Payment history alone is not a reason to keep an entire active profile indefinitely. If a specific record must be retained, we restrict it to accounting, dispute, fraud-prevention or legal purposes, explain the reason and expected period, and remove unrelated data. We aim to notify you of completion or any necessary extension within 30 days, subject to any shorter legal deadline. An automated completion button is currently available only for accounts without financial or administrative holds.

Operational periods

• Active account and entitlement records: kept while you maintain the account or need access to a purchased license. You may request deletion at any time, including after a trial expires.
• Email verification codes: expire after 10 minutes. Expired code and rate-limit rows are removed in bounded batches during later requests; expiry does not promise erasure at exactly 10 minutes.
• Sessions: expire after 30 days. Sign-out revokes the current session; an accepted deletion request revokes all current sessions. Expired database rows may remain until cleanup.
• Cookies: sign-in cookies last up to 30 days, Google sign-in challenges up to 10 minutes, and the trial browser cookie up to one year, refreshed on use. Clear browser cookies to remove local copies.
• Remote relay: queued requests expire after 90 seconds; completed responses expire 120 seconds after completion. Expired records are removed in batches on later relay requests, not by a guaranteed second-by-second purge. An accepted signed-in deletion request removes the account's stored relay requests and device registrations.
• Support and privacy requests: our manual retention target is 12 months after closure, unless a continuing dispute or legal requirement needs a limited record. Account-linked reports are removed with account deletion where no exception applies. A completion receipt without account, contact or device identifiers may remain.
• Payment records: we use a seven-year accounting retention policy from the transaction, unless applicable law requires a different period or an unresolved dispute requires a documented extension. Keep only the transaction and identification details needed for that purpose; these records are not used to keep a deleted account usable. Stripe may retain records under its own legal obligations.
• Security records: retain only what is necessary to investigate a specific incident or meet a legal obligation, with a recorded reason and review date. We do not treat every account as an indefinite fraud hold.

Support, accounting and exception reviews are operational procedures, not a claim that every row is already covered by an automatic timed purge.

Backups and third parties

Deleting active records does not immediately erase isolated infrastructure backups or provider security logs. Those copies remain subject to the provider's backup and retention lifecycle and restricted purposes; we do not promise an unverified fixed expiry for them. If data is restored for recovery, applicable deletion requests must be reapplied before normal use. We ask our processors to remove data where applicable and tell you about necessary exceptions. Independently selected AI providers, repositories and build services apply their own policies.

Your local phone projects are not erased by an account request. Delete files or clear Polariton's app storage separately. Contact us for a specific retention question or to request removal of particular data.