Self-service data deletion

Delete your Threadglance account and saved app data.

Deletion is available on a dedicated signed-in page even if pilot access is later withdrawn. Email content can never request, approve or trigger it.

Protected workflow

How to delete the account

  1. Open the protected deletion page and sign in with the account email.
  2. Choose “Permanently delete Threadglance”. If your session is older than ten minutes, confirm your identity with a fresh email code.
  3. Continue to create a short-lived, one-use server challenge.
  4. Type DELETE MY ACCOUNT exactly and submit once.
  5. Keep the deletion-receipt page until it reports completion or tells you what provider-side step remains.

What is deleted

The workflow first stops scheduled and manual mailbox checks. It then removes every stored Outlook or Gmail credential, mailbox identity, message envelope, summary, draft, category correction, preference, signature, writing profile, usage row and scan record owned by the account. Finally, the Supabase Auth user is hard-deleted so its sessions and refresh tokens are removed.

Threadglance does not delete or modify messages in your provider mailbox. Google authorization revocation is attempted after the local token has been deleted. Microsoft consent may need separate removal in your Microsoft account or by your administrator.

Receipts and backups

A random, content-free deletion receipt remains for up to 30 days. It contains status and provider-revocation flags, not your email address or mailbox content. Deleted database records may remain in encrypted backups until the active backup window expires. The production deletion workflow records a random request ID, status, timestamps, checksum and an AES-256-GCM-encrypted Auth owner UUID in an independent Cloudflare Workers KV journal before local deletion. The encrypted UUID remains pseudonymous personal data, but Cloudflare receives no decryption key, email address, mailbox content or provider token. Unresolved pending tombstones remain until resolved; after completion, the pending and completion pair expire after up to 400 days without retry extending the date. The controlled-pilot period covers the current seven-day managed-backup window, one annual recovery-control review cycle and a 28-day exceptional recovery and advice margin. This is an internal policy, not a statutory requirement, and must be reviewed before general release. A restored environment must remain offline until the stable journal has been replayed and zero remaining rows, sessions and Auth user have been proved. The ledger endpoint rejects unauthenticated access and an authenticated smoke test returned a signed receipt. A destructive live account-deletion rehearsal and offline restore rehearsal are still outstanding.

The database-backed pilot access grant is deleted automatically. A legacy raw-email Vercel allowlist entry, if the receipt flags one, and a Google OAuth named-test-user entry sit outside the database and require the pilot operator to remove them. The receipt does not call that external cleanup automatic.

If the receipt says operator attention is required, scheduled retries continue every six hours. The worker sends the named pilot operator one content-free operational notice and keeps a visible alert count until recovery completes. The notice contains the random request ID, workflow status, bounded error code, timestamps and protected recovery path, but no email address, account identifier, mailbox details, message content or credential. Contact the person who invited you to the pilot and do not reconnect the mailbox while deletion is being resolved.