Data Processed
The framework processes authentication metadata, billing identifiers, and operational audit records. Sensitive payment card details are not stored in application databases and remain within Stripe-hosted surfaces.
How this independently operated deployment processes account and service data.
The framework processes authentication metadata, billing identifiers, and operational audit records. Sensitive payment card details are not stored in application databases and remain within Stripe-hosted surfaces.
Billing and orders: not yet published by the operator. Audit and fraud: not yet published by the operator. Usage: not yet published by the operator. Backups: not yet published by the operator. Retained records are not automatically purged by account deletion.
Use Account → Security to download local account data and delete your sign-in/profile after recent authentication. Deletion cancels subscriptions and revokes sessions and access tokens. Administrative and organization ownership must be transferred first; payable checkouts must finish or expire. Billing, orders, audit, fraud and usage records remain linked to a disabled, pseudonymized account. Provider records and backups require the operator’s separate retention/erasure process. Privacy requests: contact this deployment’s operator; a privacy contact has not yet been published.
Production deployments must enforce HTTPS, secure cookie policies, and webhook signature verification. Access to admin and runtime secrets should follow least-privilege access controls.