Privacy Policy

Effective 6 November 2026

Who we are

Stream Ease is operated by Mile End Media Limited, a company registered in England & Wales under company number 17030248, with its registered office at 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ, United Kingdom. We are the data controller for the personal data described in this policy, and we are registered with the Information Commissioner’s Office under registration reference ZC187020.

For any privacy question or request, contact privacy@streamease.co.uk.

What we collect and why

Our lawful basis is performance of a contract with you — we cannot provide the service without this data — except for server logs, which we keep on the basis of our legitimate interest in operating a secure and reliable service.

In a show, its hosts and co-hosts can mute and unmute a participant’s microphone, mute their camera, and change how they sound on the stream (their volume and their microphone’s noise suppression, echo cancellation and automatic gain control). If a host or co-host does this while the person is in the room, the person sees a message on their own screen saying so and who did it. A change made while a signed-in member is away applies the next time they join. A camera is never turned on remotely.

Recording a show

Recording is off unless the people running a show turn it on. A show is recorded to the cloud only if it was created as a recording-only show, which is never broadcast to YouTube, or if its owner, a host or a co-host has chosen to record a live show. The recording starts when one of them presses Record or Go live, and stops when the show is stopped or ended. Only the workspace owner, hosts and co-hosts can start a recording.

A recording is a single video file of the show as it is broadcast: the composed picture and the mixed sound, including everyone on stage and anything shown on screen, such as a shared screen, an image or a video. Stream Ease never puts viewer chat into a recording: while a live show is being recorded, the chat overlay and the featured chat message are not shown on the broadcast either, because the recording is the same picture as the broadcast. We do not record each person separately.

While a recording is running, a REC sign is shown in the room to guests who joined with a link. In the studio, it is shown to the person who started the recording, and to the workspace owner, hosts and co-hosts when they open or reload the studio page. Before a guest joins a show that is set to be recorded, the page they join from tells them so and asks them to agree.

Recordings are stored privately in Cloudflare R2, in its European Union jurisdiction, and are never public. While a show is being recorded, the whole recording is kept on the disk of the server that makes it, in Germany, until it is uploaded to R2 when the recording stops, then deleted from that server. If that server fails during a recording, the unfinished file can stay on its disk until we remove it. If saving a recording to R2 fails, a copy may be kept on that server. It is deleted no later than 28 hours after it was made, unless we are still recovering the recording for its workspace then. Only the workspace owner, its hosts and its co-hosts can download a recording. Each download uses a link our server creates for that one recording after checking their role, and the link stops working after 5 minutes. A copy someone has downloaded is outside Stream Ease, and what happens to it is up to them.

The workspace owner or a host can delete a recording once it has finished saving, which deletes its video file. Deleting a show does not delete its recordings. How long recordings are otherwise kept is set out under “How long we keep it” below.

If you appear in a recording and want a copy of it, or want it deleted, email privacy@streamease.co.uk. We will pass your request to the show’s host and act on it within one month.

Google user data and Limited Use

When you connect your YouTube channel, we request a single OAuth scope: https://www.googleapis.com/auth/youtube.force-ssl. We use it only to read your channel’s name, ID and picture when you connect it and again about every 25 days while it stays connected, so the copy we hold stays current, create a broadcast and a stream on your channel, bind them together, tell YouTube to start and stop the broadcast around your show, read your broadcast’s live chat while it is running, delete a broadcast or stream we created if the broadcast fails to start, and delete a stream left over from an earlier broadcast of the same show when you go live again. After you disconnect, we use the one copy we may keep (see “How long we keep it”) only to read your channel’s ID again at least about every 25 days and to withdraw our access at Google.

Stream Ease’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically, we do not sell Google user data, we do not use it for advertising, it is not used to train artificial intelligence or machine learning models, and it is not read by any person except with your explicit consent, where necessary for security purposes, or where we are required to do so by law.

Your Google authorisation is stored as an encrypted refresh token in Supabase Vault. It is never sent to your browser and never written to our logs.

How we protect your data

These protections are properties of how Stream Ease is built rather than promises about how we behave. The first of them is that we hold very little in the first place: your broadcast is recorded only when the people running it choose to record it, your YouTube stream key is never stored, and viewer chat is deleted an hour after the show ends (Stream Ease does not show it on screen while a show is being recorded, so our recordings never hold it).

• Your Google authorisation is encrypted and held apart from everything else. The refresh token that lets us act on your YouTube channel is stored in Supabase Vault, encrypted at rest and kept out of our ordinary application tables. It can be read only by a dedicated database function, and only by a privileged server-side key that never leaves our server and is never sent to a browser. The token is not written into any page, API response or log.
• Your YouTube stream key is never written down anywhere. YouTube issues it when a broadcast starts; it is passed straight to the encoder that needs it and held only for the life of that broadcast. It reaches no database, no log and no response body.
• Encryption in transit. The site is served over HTTPS only, with HTTP Strict Transport Security set for two years and including subdomains, so a browser will not connect to us unencrypted. Live audio and video between participants and our streaming servers travel over WebRTC, which is encrypted by the standard and cannot be turned off.
• Encryption at rest. Our database and file storage are hosted by Supabase on Amazon Web Services in London, and are encrypted at rest by the provider. Cloud recordings are stored in Cloudflare R2, which encrypts every file it stores at rest.
• One customer cannot reach another’s data. Every table enforces row-level security inside the database, denying access by default and permitting it only to members of the workspace that owns the row. Because the rule is enforced by the database rather than by application code, a mistake in the application cannot step around it. We maintain automated tests whose only purpose is to prove that one workspace cannot read another’s data.
• Least privilege. We request a single Google permission, and use it only against the channel you connected. Joining a live room requires a short-lived token issued by our server for one room and one role, so a browser never holds a credential that would work anywhere else. When a show is recorded, the server that makes the recording is given a temporary credential that can only upload that one recording: it cannot read, list or delete any recording.
• Hardened in the browser. We serve a Content Security Policy that restricts what a page may load and where it may send data, refuse to be embedded in other sites, stop browsers guessing file types, and allow camera, microphone and screen capture only on our own pages while blocking location access entirely.
• Credentials are kept out of our source code. They live in an encrypted configuration store, never in the code repository. Every proposed change is checked automatically for credentials, and a change that fails that check cannot be merged, so it cannot reach the live service. The same check also runs on our developers’ machines before a change is committed.
• We keep the software patched. Our dependencies are checked automatically for known vulnerabilities, and our own source code is scanned for insecure patterns. A change cannot be merged, so it cannot reach production, unless our automated tests, the dependency check and the credential check all pass.
• We never handle your password. Signing in is delegated to Google, so no password for your account is seen, received or stored by us.
• If something goes wrong. Where a personal data breach occurs, we will report it to the Information Commissioner’s Office within 72 hours where the law requires it, and tell affected users directly where the risk to them is high.

What we do not do

• We do not record a show unless the people running it choose to. Audio and video pass through our streaming infrastructure in real time and are composed into the picture sent to YouTube. Unless a show is being recorded (see “Recording a show” above), no part of Stream Ease writes the audio or video from your broadcast to storage. YouTube may keep its own recording of the finished broadcast on your channel, governed by YouTube’s terms rather than ours.
• Background effects stay on your device. Background effects are applied on your own device, in your browser, before your video is sent, whether you blur your camera background or replace it. An image you choose from your device is kept in that browser and is never uploaded to us.
• Uploaded media is stored, until you delete it. Files you choose to upload to your media library — video, audio and images — are stored in our Supabase file storage in London (eu-west-2) until you delete them. For videos and images we may also store a small preview picture beside the file, made in a studio browser from the file itself. Deleting a file removes it and its preview.
• We never store your YouTube stream key. It is passed directly to the streaming service that needs it and is not saved to any database, log or response.
• We do not sell your personal data, and we do not use it for advertising.
• We do not use analytics, advertising or third-party tracking services.

Who processes data for us

• Supabase — database, authentication, file storage and encrypted secret storage. Your data is held in the London (eu-west-2) region.
• Cloudflare — application hosting and server logs (Cloudflare Workers), the domain name service, network proxy and email forwarding for streamease.co.uk, and rate limiting, by IP address, of the public links guests use to join a show, and storage of cloud recordings (Cloudflare R2), in the European Union.
• Hetzner — hosting, in Germany, for our real-time audio and video servers (open-source LiveKit software we run ourselves), which carry your studio’s audio and video, compose your scene into the broadcast picture and, when a show is recorded, make the recording, keep it on that server’s disk while the show runs, and upload it to Cloudflare R2 when the recording stops, after which it is deleted from that server (unless that server fails during a recording, when the unfinished file can stay on its disk until we remove it, or saving it to R2 fails, when a copy can stay there for no more than 28 hours, unless we are still recovering the recording for its workspace then); and for the service that reads your broadcast’s live chat.
• Google / YouTube — sign-in, the destination your broadcast is sent to, and the source of viewers’ public channel pictures shown beside their chat messages and of your channel’s picture shown in your studio, which our website fetches from Google’s servers.
• Google — email hosting for our support mailbox, where mail sent to privacy@streamease.co.uk is delivered and kept, including requests to exercise your rights.

Some of these providers may process data outside the United Kingdom. Where they do, the transfer is covered by the provider’s standard contractual clauses or an equivalent safeguard.

How long we keep it

Except where this section says otherwise, we do not delete data automatically. Your account, workspace, shows and scenes are kept until you delete them, or ask us to delete them or to close your account. The owner of a workspace can delete it from the dashboard, which deletes everything in it, including its shows and scenes, its recordings and their video files, its media library and uploaded images, and guests’ agreements to be recorded. A large workspace may take more than one press of Delete, and anything already deleted stays deleted; it cannot be undone. Your YouTube authorisation is held until you disconnect YouTube in Stream Ease, which deletes every copy we store for that workspace, or ask us to delete it. On a disconnect we may keep one copy, used only to withdraw our access at Google and, at least about every 25 days, to check that it still works and which channel it reaches (if it no longer works, we delete it): for as long as we wait to withdraw that access because another connected workspace may use the same Google account (see below), which we check every night, and then until Google confirms the withdrawal, retrying every night if Google cannot be reached. You can always withdraw our access yourself at once at Google (see below). Revoking access at Google stops it working at once; we delete our stored copy when we next check it, which we do about every 25 days while the channel is connected. If you ask us to erase your data, we will do so within 30 days.

Your YouTube channel’s name, ID and picture are kept only while they are current. While the channel stays connected we read them again from YouTube about every 25 days. We delete them when you disconnect YouTube, except the channel ID, which we keep with the copy of the authorisation described above for as long as we keep that copy, reading it again at least about every 25 days; when we find we can no longer read them (for example because you revoked our access at Google), together with the authorisation that stopped working; and in any case within 30 days of the last time we read them.

When you disconnect YouTube from a workspace, we also delete the YouTube data we stored for that workspace’s shows (the IDs of their YouTube broadcasts, streams and live chats, and the last viewer count) within 7 days. Live chat messages, Super Chats and poll votes are deleted on their own, shorter schedule described below.

An invite is kept until it is accepted, revoked or expires (after 14 days). Revoking deletes it at once. An accepted or expired invite is deleted 30 days later. To limit how many invites can be sent, we keep a note of who sent an invite and when, without the address, for 2 days.

The website’s server logs are kept by Cloudflare for 7 days and then deleted automatically.

When you email privacy@streamease.co.uk to exercise your rights, or about a recording you appear in, we keep your request, our replies and a note of how we dealt with it, so that we can show what we did. We delete them no later than 2 years after we have finished dealing with your request.

Records of who muted or unmuted whom are kept with the show they happened in, and are deleted with it.

A guest’s agreement to be recorded is kept with the workspace of the show they joined, and is deleted with that workspace. It is not deleted with the show, because a show’s recordings are not either.

Cloud recordings are deleted automatically 90 days after the recording ended, by a job that runs every night. A recording that is still being saved is not deleted until it has finished. Each workspace owner also has a storage allowance for recordings: when their recordings take up more than that, the same job deletes their oldest recordings until they fit, but never their newest saved recording or one that ended less than 3 days ago. Download anything you want to keep before then. Deleting a recording, by hand or by this job, deletes its video file; a note that it existed, with its title, date, length and size, stays with the workspace and is deleted with it. A copy kept on the server that makes recordings after a failed save is deleted no later than 28 hours after it was made, unless we are still recovering the recording for its workspace then, whether or not the recording is deleted.

Links to images you upload are time-limited and expire after 12 hours, but the images themselves stay in your workspace until you delete them.

Chat messages captured from a YouTube broadcast are different: we delete them an hour after the broadcast ends. YouTube keeps its own record of live chat on the video’s replay, so Stream Ease is not the system of record for it and has no reason to hold it. Deletion is performed by a scheduled job, not by hand. Chat does not outlive that hour in a recording either: Stream Ease does not show viewer chat on screen while a show is being recorded.

A chat message that someone in your studio hides from the show is taken off the screen, but it is not deleted at that moment: we keep it, marked as hidden, so that it can be restored, and delete it with the rest of the show’s chat an hour after the broadcast ends, or 24 hours after we captured it if that comes first. With the mark we record which member of your workspace hid it (their account ID), and that record is deleted with the message.

A chat message that the owner, a host or a co-host of your workspace stars as a favourite is kept with the rest of the show’s chat and deleted at the same time, by the same rules; favourites are also cleared when the same show goes live again. With the star we record which member of your workspace starred it (their account ID), and that record is deleted with the message.

The one-way identifier we derive for polls is deleted at the same time, an hour after the broadcast ends, together with the random value that poll used to derive it. That random value is unique to a single poll and is never reused, so once it is gone the identifier cannot be worked back to a YouTube channel. We never hold the channel itself: the identifier is calculated as a chat message is read and it is the only form we store.

The results of a poll are kept, and are not deleted on that timetable: the question, the options and the running totals stay with your show, so a series of polls can be compared over a season. Once the votes and that random value have been deleted, those results are counts and averages with nothing in them that identifies a viewer.

How to revoke our access to your YouTube channel

You can withdraw our access at any time:

• Choose Disconnect beside YouTube in each workspace’s box under “Your workspaces” on your Stream Ease dashboard. This deletes the YouTube authorisation we store for that workspace from our systems, including any earlier copies from previous connections, except one copy we may keep while we may still need it to withdraw your access at Google. If no other Stream Ease workspace may be connected with the same Google account, it also withdraws the access you granted Stream Ease at Google. Google’s permission covers the whole Google account, so we do not withdraw it while another connected workspace may still use it. If another workspace is connected to the same channel, we delete our copy at once and leave Google’s permission in place; it is withdrawn when that workspace is disconnected too. If another workspace may use the same Google account, because it was connected to YouTube by, or is owned or hosted by, the person who connected this one, you, or another owner or host of this workspace, we keep the copy, check every night, and withdraw the permission once none of those workspaces is connected any more. We also wait while we cannot yet read which channel this connection reaches, or which channel a connection reaches in a workspace that one of those people belongs to. Before you disconnect, the dashboard names those workspaces only if you belong to them, and otherwise says only that the account may also be in use elsewhere. The next option always withdraws it at once. Withdrawing it also removes the permission you gave Stream Ease to sign you in with Google, if you sign in with the same account. An owner or host of the workspace can disconnect, but not while a show is live or scheduled on YouTube.
• Remove Stream Ease at myaccount.google.com/permissions. This revokes the authorisation at Google directly and stops us being able to create or control broadcasts on your channel. Google treats Stream Ease as one app, so this removes its access for that whole Google account: every Stream Ease workspace connected with that account stops being able to broadcast, and the permission you gave Stream Ease to sign you in with Google is removed too.
• Email privacy@streamease.co.uk and we will disconnect the destination and delete the stored authorisation.

Your rights

Under UK data protection law you have the right to access your personal data, to have it corrected or erased, to restrict or object to how we use it, and to receive it in a portable form. To exercise any of these, email privacy@streamease.co.uk.

If you are not satisfied with our response, you can complain to the Information Commissioner’s Office, the UK supervisory authority, at ico.org.uk.

Cookies

We set only the cookies the service needs to work: a session cookie that keeps you signed in, a short-lived cookie that protects the YouTube connection flow against cross-site request forgery and remembers which of your workspaces you are connecting, and a workspace cookie that remembers which of your workspaces is active. The workspace cookie is set only when you add a second workspace or choose the active workspace, holds your account ID and that workspace’s ID, is deleted when you sign out, choose “All workspaces” or delete the active workspace, and otherwise lasts up to a year. It is ignored for any other account and while you belong to only one workspace.

When you join a show as a guest from a link, we set a guest cookie for that show. It holds a random guest ID and a code that proves we issued it, and nothing else about you. It keeps your place in the show if you reload the page or open the link again in the same browser: you come back as the same guest, and a microphone or camera a host turned off stays off until a host allows it again. Your browser sends it only when you join a show from a link, we use it only for the show it was set for, the page cannot read it, and it lasts 12 hours from the last time you joined that show.

These cookies are strictly necessary for the service you ask us for, so we do not ask for cookie consent. We do not use analytics, advertising or tracking cookies.

Children

Stream Ease is not intended for anyone under 18, and you must be 18 or over to create an account.

Changes to this policy

If we change how we handle personal data we will update this page and change the effective date above. If the change is significant, we will tell account holders by email.