Account deletion

How to request deletion

1. Enter the email address associated with your Whytype account.
2. Optionally tell us why you are requesting deletion.
3. Confirm that you are requesting deletion, then submit the form.
4. The request must be verified as yours before an account can be deleted. The public form does not authenticate you and does not delete an account by email address alone.

Do not enter a password, one-time code, session token or payment details. A form receipt is only confirmation that a request reached the contact intake; it is not confirmation of identity verification or completed deletion.

Information that may be included in a verified deletion

The app repository identifies account and profile rows, sessions and session messages, embeddings, meeting records and private audio, journal screenshots, AI usage ledger and AI event records, watch pairings, phone sessions and uploaded avatars. These categories are the intended scope for a complete account deletion, subject to verification of actual production schema, dependencies and storage ownership. In particular, private meetings and screenshots objects and user-owned objects in the public avatars bucket must be handled as storage objects, not merely by deleting database rows.

The website does not currently invoke a Supabase authenticated deletion function. The audited Whytype backend repository did not containdelete-account, request-account-deletion or028_account_deletion_requests.sql. The public form uses the existing Formspree contact intake; it does not persist a deletion job in Supabase or perform data deletion. The Supabase schema audit could not verify all production foreign keys, storage paths, profile relationships or RLS rules, so no automated deletion is claimed or attempted here.

Identity verification and completion

The account owner must be verified before deletion is performed. This form does not provide that verification, and submission alone does not authorize deletion. The operator must establish a secure verification process and authenticated, user-scoped deletion endpoint before it can complete account-wide deletion. Do not send credentials or tokens in the form or by email.

No processing deadline is published. A request remains pending until the operator confirms verification and separately confirms completion. Retention periods for backups, security logs, provider records and legal records have not been established in the audit. Data may remain in those systems for their applicable retention periods even after primary account data is deleted; the operator must set and disclose those periods.

Subscriptions must be cancelled separately

Deleting a Whytype account does not cancel a recurring subscription. Cancel through the store or provider that billed you, such as Apple Subscriptions or Google Play subscriptions. The code includes RevenueCat integration, but production configuration and the exact purchase path were not verified. Confirm cancellation in the billing provider before assuming future renewal has stopped.

Related information

See the Whytype Privacy Policy and Child Safety Standards. For a general question about a request, use the DizByte contact form. No Whytype-specific privacy contact or deletion operations contact has been verified.