Data export & deletion process
Draft operational disclosure — privacy/legal review required before launch.
Export
Signed-in users can request a JSON export from Settings → Privacy & data. Export is a sensitive action and requires trusted-origin checks plus recent sensitive-action authorization. Provider credentials, session tokens and other users' private graph data are excluded.
Account deletion
Signed-in users can request account deletion from the same settings page. The deletion workflow first inventories and closes external account contracts. Active Stripe subscriptions are canceled immediately and the external cancellation must be confirmed before local erasure can continue; provider access, API keys and outbound automations are closed or disabled. Shared provider-source event subscriptions are retained when other demand still exists.
After external closure is confirmed, sessions, private/tokenized feeds, user-owned links and workspace membership are removed and the local account is erased. Global public creator/content records can remain shared infrastructure. Legally required or integrity-critical billing, refund/dispute, referral, creator-balance, payout and legal-acceptance evidence may be retained under a pseudonymous former-user identifier.
Account deletion does not automatically create a refund. Refund eligibility and statutory withdrawal rights remain governed by the reviewed refund/cancellation policy.
For a request that cannot be completed in-product, use the operator's reviewed support/contact channel published for the production service.