Legal

Twist Account Deletion

Twist automatically creates an anonymous guest service account when it begins synchronizing viewer state. This page describes, honestly, what deletion tools Twist currently provides and where the current app falls short.

Effective July 24, 2026Last Updated July 24, 2026
01

What Twist does today

  • Clear History (in My List) removes local watch history on this device and requests removal of synchronized watch history, while preserving your saved shows.
  • Reset Viewing Data (in Profile) removes local saves, likes, watch history, onboarding, preferences, pending viewer mutations, and legacy compatibility state on this device, and requests deletion of your synchronized saved-show and watch-progress rows for the current guest session. If that synchronized reset fails, the request is queued and retried.

Reset Viewing Data is not full account deletion. It does not delete the underlying Supabase anonymous Auth user, the default profile row created for you, the legacy starter-ledger row, or provider infrastructure logs. Uninstalling Twist removes the active app container from that device but is not guaranteed to remove the Keychain session or the server-side guest account.

02

Current limitation

The current Twist app and backend do not yet offer a verified way to delete the anonymous guest Auth account and all associated records. This is a pre-release engineering blocker.

Apple requires apps with automatically created guest accounts to support account deletion. This page therefore does not represent Twist as currently compliant with that App Store requirement, and this page does not represent Reset Viewing Data as satisfying it. Do not read this page as legal advice or as a claim that Banana Apps has completed the deletion work.

03

If you would like help

You can email Twist Account Deletion Help and we will explain what deletion tools are currently available. We will not claim that emailing support currently guarantees deletion of an unidentified anonymous guest account. Because Twist has no name, email, password, or payment identifier tied to a session, we cannot reliably verify who is behind a specific guest account from an email alone.

There is no form on this page. There is no automated deletion API. There is no ticketing system.

04

Publication requirement

Publication requirement

[DO NOT PUBLISH AS A COMPLIANT DELETION FLOW UNTIL IN-APP AUTH ACCOUNT DELETION, CASCADE VERIFICATION, SESSION CLEARING, SUPPORT IDENTIFICATION, RETENTION EXCEPTIONS, AND COMPLETION NOTICE ARE TESTED]

05

What this page will document once deletion is operational

When the engineering work is complete and verified, this page will document:

  • The exact in-app path to request account deletion.
  • The data that will be deleted (Auth user, profile row, viewer-state rows, legacy compatibility rows, and Keychain session where applicable).
  • Any data that will be retained and the specific lawful reason for retaining it: [LAWFUL RETENTION EXCEPTIONS].
  • The expected completion time: [ACCOUNT DELETION COMPLETION TIME].
  • How subscription state would be handled if commerce is ever introduced.
  • How completion will be confirmed to you.

Those statements will not be added until each item is implemented and verified.