Otter Beam

Delete Your Account

Last updated: August 11, 2026

You can permanently delete your Otter Beam account without contacting support. In the app, open Profile → Account → Delete account, then confirm with your account password or request and enter a fresh verification code sent to your account email.

If you cannot use the app

Email peter@otterd.com from the email address on the account. We will send verification steps before deletion. Never send us a password, sign-in code, SSH key, or access token.

Data deleted

Deletion hard-deletes your Auth user and removes renewable sign-in sessions, cloud profile, registered cloud devices, uploaded public-key records, database push-token copies, sealed project metadata, navigation state, composer drafts, browser dials and the synced Continue On address, saved ideas, transcription usage totals, database relay-usage rows, and other deletable database rows tied to the account. This is not a reversible soft deletion. A normal self-service deletion does not retain your email in a post-deletion ban list.

Before deleting the Auth user, Otter Beam sends a separately authenticated purge request to Otter relay. Relay closes the account's known machine and display sockets, deletes known routing, reconnect, notification, usage, and abuse-prevention state, and confirms every current registered machine plus its bounded recent-machine history. If any known target cannot be confirmed, deletion stops and reports an error instead of claiming success. Known objects retain only a 24-hour anti-race tombstone so late socket callbacks cannot recreate deleted state.

The endpoint cannot actively reach every Cloudflare Durable Object because Cloudflare does not provide namespace-wide enumeration. A legacy orphan removed before machine-history registration existed and absent from the bounded history cannot be synchronously discovered. Opaque metric receipt IDs and provider-controlled logs follow the limited retention described in our Privacy Policy; they are not used to recreate the deleted account.

Data stored only on your devices or machines is not remotely erased. Use app and operating-system storage controls for local copies, and separately remove authorized SSH keys already installed on connected machines; uninstall behavior varies by platform.

Data retained

We retain only minimized pseudonymous billing records in our database: subscription and refund evidence for six years from creation of the deletion archive, store event identifiers used to prevent duplicate processing of Apple and Google billing notifications for up to two years from receipt, refund records referenced only by a subscription for up to six years, and a pseudonymous deletion receipt for two years from the request. A documented legal hold or unresolved payment dispute may extend the applicable period; a daily database job deletes the record after its deadline and any hold ends. Pseudonymous means the record is still protected as personal data, not that it is anonymous.

These records do not contain your email, terminal content, source code, files, transcripts, SSH private keys, push tokens, readable project names, or readable paths. Apple, Google, Stripe, Supabase, Cloudflare, or Alibaba Cloud may separately retain provider-controlled transaction records, logs, backups, or identifiers under their own legal and retention rules.

Subscriptions

Before deleting an account, Otter Beam automatically turns off renewal for all active Stripe subscriptions; deletion stops if any cancellation cannot be completed. Deleting an Otter Beam account does not cancel an Apple App Store or Google Play subscription. Cancel or manage a store subscription in the store that sold it.

Timing and confirmation

In-app deletion is processed immediately after verification and reports success only after the Auth user hard delete succeeds. If you use the email alternative, we aim to complete a verified request within 30 days and will confirm completion or explain any lawful delay. Provider-controlled backups, logs, and transaction records follow the provider's own retention cycle; they are isolated from normal product access and are not restored to recreate a deleted account.