How Stitch Uses And Retains Your Data

Requesting Account Erasure

You can permanently delete your account from account settings. You must type DELETE and confirm with your current password or a fresh SMS code sent to your verified phone number.

Once accepted, Stitch immediately disables the account, signs it out, revokes access, makes creator-owned events private, moves scheduled events back to draft, and unpublishes replays. Provider or background-job failures do not restore access; Stitch retries unfinished cleanup.

Data Removed Or Anonymised

Stitch removes account identity and profile details, phone identity, sign-in credentials, notification endpoints, telemetry, follows, votes, likes, reminders, viewing progress, chat messages, and other engagement data that has no continuing retention purpose. Descriptive personal fields and cover assets are removed from creator-owned events. The account becomes a neutral “Deleted user” record and the original email, username, and phone number can be used for a new account.

A linked Stripe billing Customer is deleted as part of durable cleanup, cancelling its subscription and removing stored payment methods. Stitch retains no local payment-method summary after erasure.

Payments, Safety, And Records We Retain

Stitch keeps a stable, anonymised account reference where it is required by settlement allocations, balances, payouts, moderation reports and actions, safety audits, copyright matters, or related legal records. This prevents account erasure from forfeiting earnings, bypassing a safety hold, or changing immutable financial history. Amounts, statuses, and timestamps remain linked to the neutral account tombstone.

A contributor’s Stripe Connect account identifier is retained only while an event may still settle, an advertising attribution window may create supplemental revenue, a positive payout is incomplete, or a moderation, copyright, safety, or legal hold remains active. Payouts continue to the anonymised account. Stitch asks Stripe to delete the Connect account only after those obligations are terminal and Stripe confirms its balance is zero.

Offline recordings and programme history continue under their existing media-retention and safety-hold rules. Erasing a contributor account does not automatically edit that contributor out of a programme owned by somebody else.

Protected-Data Retention

The default retention period for necessary financial and safety records is six years from account erasure or later protected activity. An unresolved payout, moderation report, copyright matter, safety review, or documented legal hold extends that period. Once the period and all holds have ended, a daily process removes residual provider identifiers and free-text details while retaining only the anonymous amounts, statuses, timestamps, and references that remain necessary.

Retention must remain necessary and justified. See the UK Information Commissioner’s guidance on the right to erasure and storage limitation.

Contributor Telemetry

After explicit consent for an event, Stitch may collect GPS location, motion or orientation, and device diagnostics such as browser capability, network type, battery level, camera and microphone labels, and user agent. This helps creators monitor stream quality, confirm event proximity, and diagnose live contribution issues.

Consent is recorded per event membership with a timestamp and notice version. You can withdraw it from the contributor screen at any time; withdrawal stops collection and deletes the stored telemetry for that event. Otherwise, telemetry rows are automatically deleted after the configured window, which defaults to 30 days.

Questions Or Rights Requests

Use the feedback and support form for a privacy question or rights request. Stitch will explain any information it cannot immediately erase because a legal obligation, claim, payout, or active safety matter still requires it, and will erase or anonymise it when that reason ends.