LEGAL

Delete your data

This page is the plain-language route to deleting the data BenchStream handles. It is the deletion page we give to Google Play and to Apple, and it describes the same routes as section 10 of our Privacy Policy, which stays the authoritative document.

BenchStream creates no BenchStream account. There is no BenchStream username, password or profile to close, and we do not operate an application server that receives your video or stores your app data. That changes what deletion means here: almost everything is removed by revoking Google access and removing the app, and only one small record is held by a third party on our behalf.

1. What data exists, and who holds it

  • On your device only. OAuth tokens (your Google access and refresh tokens), Manual destination credentials (any RTMP, HLS, or SRT URLs, stream keys, passphrases, and authentication headers you enter for protocols available in your app version), App preferences (microphone settings, default bitrate and resolution, scoreboard preset and team logos you have imported, custom thumbnails you have selected), locally cached YouTube profile and broadcast information, and, on Android, Cached entitlement status: whether Pro is currently active. On Android these credentials use encrypted storage backed by the Android Keystore; on iOS they are stored in the iOS Keychain, restricted to this device.
  • Held by Google. The grant you gave BenchStream when you signed in with the youtube.force-ssl permission, and the broadcasts and videos on your own YouTube channel. Access tokens are sent to Google with authenticated YouTube API requests; BenchStream does not receive or store them on a server it operates.
  • Held by RevenueCat, on Android. A pseudonymous RevenueCat app-user ID generated for the installation, the Entitlement status (whether Pro is active, in a grace period, cancelled, or expired), and Store purchase evidence: the purchase token or receipt issued for your subscription. This record exists only for an installation that has contacted RevenueCat, which happens when you choose to open a billing surface showing subscription prices or plan terms. Merely starting a broadcast does not contact RevenueCat. iOS billing and RevenueCat integration exist in draft source, not a public release.
  • Held by the store. Google Play holds the transaction record for a Pro purchase. Apple will hold its own records for future App Store purchases.
  • Held by us. Only the support correspondence you send to support@bench-stream.com, and any attachments you choose to include.

2. Deleting without the app

These steps work whether or not BenchStream is still installed, and whether or not you still have the phone.

  1. Revoke BenchStream's access to your Google account. Go to myaccount.google.com/permissions, or your Google security settings, select BenchStream and remove its access. This invalidates the access and refresh tokens stored on the device, so a copy of the app that still holds them can no longer reach your channel. Revocation can take time to propagate.
  2. Remove the local data. Uninstall BenchStream, or clear its data in your phone's app settings. This removes the OAuth tokens, app preferences, saved manual destinations, team logos and crests you imported, custom thumbnails, and the locally cached record of your broadcasts. On iOS, do not assume uninstalling erases all app data; see section 3.
  3. Deal with a subscription separately. Manage or cancel a Pro subscription in the Google Play app, under Payments and subscriptions → Subscriptions, or at play.google.com/store/account/subscriptions. When iOS ships, an App Store subscription is managed in Apple's own account settings. Revoking Google access, clearing app data and uninstalling do not cancel store billing and do not erase the store's transaction record.
  4. Ask us to delete the remaining records. Email support@bench-stream.com and say you want the RevenueCat entitlement record deleted, the support correspondence deleted, or both. No email address, Google account or YouTube channel is attached to the RevenueCat record, so we cannot look you up by name. Tell us the approximate date of the purchase and which store took the payment, so we can find the right record. If you never subscribed and never opened a paywall, there is nothing at RevenueCat to find.

3. Deleting from inside the app

On Android, open Settings → Account → Sign out. That clears your Google tokens from the app. Signing out is a local action: to end the grant at Google as well, still use the revocation link in step 1 above.

The unreleased iOS draft adds two separate controls in Profile. Disconnect Google clears the stored credentials only after Google confirms revocation, and reports a failure rather than pretending to have succeeded. Erase local app data is a confirmed next-launch local reset that you can cancel before restarting; it removes declared app files, imported images, caches, cookies, preferences, temporary files and scoped current and legacy Keychain services before repositories and SDKs start. System permissions, Safari sessions, remote data and backups are outside this scope. These are draft controls, not publicly released iOS instructions.

Erasing local data does not cancel a subscription. Cancelling recurring billing is done in the store that took the payment, as in step 3 above.

4. What we cannot delete for you

  • Your YouTube broadcasts and videos. They are yours and stay on your YouTube channel. Remove them in YouTube Studio.
  • The store's transaction record. Google retains its purchase record under its legal and operational obligations, and we cannot delete it on your behalf. Apple's own privacy policy will govern its records for future App Store purchases.
  • Anything a record we must keep depends on. Where accounting, security, dispute-resolution or other legal obligations require us to retain something, we keep only that, and only for as long as the obligation lasts.

5. How long a request takes

We aim to respond within one month, as required by UK GDPR, and we act on a deletion request where the law allows. If a request is complex we will tell you inside that month and explain the delay. Support correspondence and attachments are in any case retained for up to 12 months after a request is resolved, unless we need to keep them longer for security, legal, accounting, or dispute-resolution reasons.

The full retention position, including what RevenueCat and the stores hold and for how long, is in section 10 of the Privacy Policy. Your rights of access, rectification, erasure, restriction, objection and portability are set out in section 11 of the same document.

6. Contact

Email support@bench-stream.com.
Postal correspondence address: BenchStream, Unit 168641, PO Box 7169, Poole, BH15 9EL, United Kingdom.