Log in

Privacy Policy

Last updated 16 September 2026

This policy explains what Stream Repeater collects, why, and your choices. By using the service you agree to it.

Information we collect

  • Account data — your name, email, and password (stored hashed).
  • Stream configuration — workspaces, streams, and destinations you create. Destination credentials are encrypted at rest. If you sign in with Twitch or Kick to set up a destination, we use that connection only to read your channel’s ingest URL and stream key so we can create the destination for you; the key is then stored encrypted like any other destination credential. YouTube and Facebook issue a key only for a specific broadcast, so for those we create the live broadcast you asked for on your own channel or Page and use the ingest URL and key it returns.
  • Operational data — relay status, throughput and viewer metrics, stream health and stability diagnostics (for example detecting a source that keeps dropping so we can flag an unstable connection), and security/audit logs.
  • Recordings — if you turn on recording for a stream, we store the recorded media on our infrastructure for a limited, plan-based retention period and then delete it automatically. Recording is off by default and you control it per stream.
  • Branding assets — any logo you upload for a public watch page and, if enabled, the custom domain name you point at that page.
  • Viewer lead data — if a workspace owner enables lead capture for a public watch page, the name and email a viewer enters to unlock that stream. The workspace owner is the data controller for those details; we process them only on the owner’s behalf so they can grant access and export their leads.
  • Connected-platform tokens — if you connect a destination account such as YouTube or Twitch for unified viewer analytics, its authorisation token, stored encrypted and used only to read aggregate viewer counts.
  • Integration & automation data — if you use Integrations, the credentials, webhook URLs or device details you enter for connected services, all encrypted at rest; the automation rules you build; and a short rolling log of the live events that drive them, with the small amount of context each event carries. Twitch events are received through Twitch EventSub webhooks.
  • AI provider keys — if your plan includes AI Streams and you use it, your API key for the video-generation provider you choose, encrypted at rest. We retain the last four characters and a one-way fingerprint in the clear to distinguish keys and detect a re-paste, together with your instructions and the result of our abuse gate. The key and billed provider account are yours; we use the key only to request the clips you ask for.
  • Local Agent data — if you run the optional Local Agent on your computer, a pairing record and per-agent signing key. The agent runs on your machine and forwards events to your workspace; we receive only those events, not your device contents.
  • Safety reports — report category and details, reporter contact details if supplied, content snapshots, moderation decisions, and a hashed IP address for abuse prevention.
  • Technical data — IP address and request metadata, used for security and rate limiting.

How we use it

To operate the service — authenticate you, run and supervise your relays, show you metrics, take payment, and keep the platform secure. We do not sell your personal data.

Support access. Our administrators may securely access or sign in to your account to provide support, investigate issues, or enforce these terms. Such access is restricted to staff, recorded in our audit trail, and used only for those purposes.

Legal bases (GDPR)

  • Contract — to provide the service you sign up for (account, streams, relays, billing).
  • Legitimate interests — security, abuse prevention, and service improvement, balanced against your rights.
  • Legal obligation — retaining invoices and financial records as required by law.
  • Consent — optional marketing emails (opt in/out anytime in Settings, or via any email’s unsubscribe link).

Who we share data with

We use a small set of processors to run the service, each under their own data-protection terms:

  • Hetzner — hosting in EU data centres.
  • Amazon Web Services (S3) — encrypted off-site backups stored in the UK (London, eu-west-2).
  • Amazon SES — transactional and account emails.
  • Stripe — payment processing; we never store full card details.
  • Cloudflare — bot/abuse protection (Turnstile) and, where enabled, CDN/edge delivery and web-application firewalling for the control plane.
  • Google, Twitch & Kick — only if you choose to sign in with or connect one of these accounts; each handles your data under its own privacy policy.
  • Meta (Facebook) — only if you connect a Facebook Page as a restreaming destination; Meta handles what it receives under the Meta Privacy Policy.
  • AI video-generation providers — only if you enable AI Streams and save your own provider key; your chosen vendor receives your instructions under your own account with it.

The hosting, backup, email, payment and security providers above are our sub-processors: they handle data on our instructions so the platform can run. The platforms and vendors you choose to connect — a restreaming destination, an integration, or an AI provider whose key you supply — are not our sub-processors. You choose them, your relationship is with them, and they handle what they receive under their own terms. We send them only what the feature you enabled needs.

Cookies

We use strictly-necessary cookies (such as your login session and a CSRF security token) to operate the platform. With your consent, we also load analytics tools (Google Analytics and our self-hosted tracking system) to help us measure site traffic and improve performance. You can accept or decline these optional cookies through our consent banner. We do not use advertising cookies.

Our custom analytics tracking is hosted at https://tracking.zurg.co.uk/ and handles data in a privacy-respecting, GDPR-compliant manner.

International transfers

Your data is hosted in the EU (Germany), with encrypted backups stored in the UK. Where a processor handles data outside the EU/UK, it is covered by appropriate safeguards (for example Standard Contractual Clauses).

Media content

Stream Repeater relays your live streams to the destinations you configure. By default we do not retain stream media — it passes through and is delivered onward. Two optional features change this, and only when you enable them:

  • Recording — if enabled, we store the recorded media for a limited, plan-based retention window and then automatically delete it. You can delete recordings at any time.
  • Public watch page — if enabled, the stream is viewable by anyone with the link and through any site where you embed it. Disable it and the link stops working.

We may generate a short-lived still preview thumbnail of a live stream for your dashboard; it is cached briefly and automatically replaced or expired.

Third-party destinations such as YouTube and Twitch handle delivered content under their own policies. If you configure outbound webhooks or an alert URL, we send stream-event metadata, not media, to the endpoint you specify.

Watch-page protection, leads & connected platforms

These optional features are off by default, available only on plans that include them, and controlled by you per stream:

  • Watch-page password. If you protect a watch page, we store only a one-way hash of the password, never the password itself, and a short-lived access cookie in each viewer’s browser.
  • Lead capture. If a workspace owner requires a name and email before viewing, that workspace owner is the data controller and we act as processor. We collect the details only to grant access and make the leads available to the owner for export. We do not market to those viewers or use their details for our purposes. Viewers are told the details go to the stream owner. They may ask us to forward a deletion request; the owner may delete a lead at any time; records are removed when the watch page is deleted.
  • VOD clips. A clip created from a recording is stored on the same plan-based basis as the underlying recording and is deleted when you delete it or its parent recording.
  • Custom domain. If you point a domain at a watch page, we store its hostname, perform DNS lookups, and issue a TLS certificate through a certificate authority such as Let’s Encrypt. Remove the domain and we stop using it.
  • Unified viewer analytics. If you connect a destination account, we use its API only to read aggregate concurrent-viewer counts. We store the access token encrypted, never post on your behalf, and you can disconnect the account at any time to revoke access.

Integrations & automations

Integrations let you connect third-party platforms and devices and run rules that react to live events. They are off by default, available only on plans that include them, and entirely under your control:

  • Connecting a service. When you connect Twitch or Kick we store its OAuth token encrypted and register the event subscriptions or webhooks needed for your channel events. For other services we store the API key, webhook URL or device details you provide, encrypted. You can disconnect any integration at any time, which removes its credentials and tears down subscriptions we created.
  • YouTube (Google) data. Connecting YouTube grants access to your own channel using the youtube.force-ssl scope, only for actions you request: reading live-chat messages, Super Chats and new-member events for automations and moderation; sending replies and performing deletions, timeouts or bans you initiate in your live chat; and creating a live broadcast plus ingest endpoint and stream key when you request YouTube restreaming. We do not read, modify or delete existing videos, captions, playlists or other channel content, never touch another channel, and make only the broadcasts, replies and moderation actions you request. Stream keys and OAuth tokens are encrypted. Chat is retained briefly: each event copy in your private activity log is deleted after 7 days. You can revoke access from your Google account or disconnect YouTube. Limited Use. Our use and transfer of Google API information follows the Google API Services User Data Policy, including Limited Use: we do not use Google user data for advertising, sell it, use it to train generalised AI/ML models, or transfer it except to provide these features, protect security, or comply with law.
  • Unified chat & engagement. For connected Twitch, Kick, YouTube, or TikTok through Local Agent, we capture recent messages — public display name and text — in a moderation feed for reading, replies, moderation and overlays. Messages last only for the live moderation window and are removed when deleted, when a participant is removed, or as the feed rolls over; moderation soft-deletes them from feed and overlay. Giveaways, polls and chat commands retain only participants’ public chat names for that activity and clear them when it ends.
  • Data we send to connected services. When a rule fires, we send the configured action to the destination you chose, such as a Discord message, custom webhook request or light command. Those parties process it under their policies. We send only what the action needs and never sell or repurpose it.
  • TikTok & the Local Agent. TikTok has no official live API, so events are gathered by Local Agent on your computer and forwarded over a signed connection. Running it and connecting accounts or devices is your choice and responsibility under those platforms’ terms.
  • Event log. We keep a short rolling activity log to debug automations: inbound events and their limited context are automatically deleted after about 7 days, and rule-run records after about 30 days.

YouTube API Services

Stream Repeater uses YouTube API Services to read and act in your live chat and set up restreaming to your channel. By connecting YouTube and using these features you also agree to the YouTube Terms of Service. Google’s handling of your information is described in the Google Privacy Policy.

  • What we access. With your explicit consent we use only https://www.googleapis.com/auth/youtube.force-ssl, on your own channel, to: (1) read live-chat messages, Super Chats and new-member events; (2) send replies and carry out the deletions, timeouts or bans you initiate; and (3) when requested, create a live broadcast plus ingest endpoint and stream key for restreaming. We never read, modify or delete existing videos, playlists, captions or other channel content, and never touch another channel.
  • How we store it. OAuth tokens and stream keys are encrypted at rest. Live-chat content runs your automations and moderation, and a copy of each event appears only in your private activity log.
  • How we delete it (data-deletion policy). Google user data is deleted automatically and on request: activity-log copies are deleted after 7 days; live-chat messages shown in dashboards and overlays after at most 30 days, or immediately when moderated, in line with YouTube API Services rules; disconnecting YouTube immediately deletes tokens and stream keys and stops access; deleting your account removes all associated YouTube data. You may also request deletion through a data request.
  • How to revoke access. Revoke at any time from Settings → Privacy → Connected accounts using “Revoke access”, by disconnecting YouTube in your workspace, or through Google security settings at https://security.google.com/settings/security/permissions (also myaccount.google.com/permissions). Revocation immediately deletes the stored token and stops access.
  • Limited Use. Stream Repeater’s use and transfer of Google API information follows the Google API Services User Data Policy, including Limited Use: we do not use Google user data for advertising, sell it, train generalised AI/ML models with it, or transfer it except to provide these features, protect security, or comply with law.

Twitch & Kick

If you connect Twitch or Kick, you grant access to your own channel for the same chat, moderation and restreaming features described above, and we store each OAuth token encrypted at rest. Your use is also subject to the Twitch Terms of Service and Twitch Privacy Notice, and the Kick Terms of Service and Kick Privacy Policy. Revoke access at any time from Settings → Privacy → Connected accounts or your workspace’s Integrations page, which immediately deletes the token; you may also review and revoke access in each platform’s account/connections settings.

Facebook (Meta)

If Facebook Live is offered, you can connect a Facebook Page so Stream Repeater can relay to it. Because a Facebook stream key is single-use, we create a live video on your chosen Page whenever you add Facebook as a destination and send video to Facebook’s ingest endpoint. Your use is subject to the Meta Terms of Service and Meta Privacy Policy.

  • What we ask for. Four permissions and nothing beyond a Live destination: pages_show_list to show Pages you manage; pages_manage_posts to create the live video; pages_read_engagement, required by Meta for the Page token, not used to read engagement for another purpose; and publish_video to publish live video to your own feed if streaming to a profile.
  • A fifth permission, only if the deployment’s Meta app grants it. business_management. We never request it and everything works without it. If an app administrator adds it to login, we use it only to find Meta Business portfolios you belong to and Pages in them that you may publish to. We do not read, create or change ad accounts, billing, business users or other business assets.
  • What we receive. Your Facebook name and user ID to label the connection; and each publishable Page’s ID, name and access token. If the fifth permission applies, we also receive Business portfolio IDs and record only how many Pages were found and how many are not publishable, to explain an empty list.
  • What we store. The above plus Facebook’s access token and expiry and your selected Page, all encrypted at rest. Facebook provides no refresh token, so access expires after about 60 days and you reconnect if needed.
  • What we send to Facebook. A request to create a live video on your selected Page or feed, titled with your workspace name, then your video over encrypted RTMPS. It is created “live now” and appears when video arrives. We do not read posts, comments, messages, insights, ads or friends and publish nothing except the live video you requested.
  • How to disconnect and delete this data. Disconnect Facebook in workspace Integrations: we ask Facebook to revoke the grant, immediately delete tokens and Page details, and remove destinations we created. You may also remove Stream Repeater in Facebook business integrations settings. Account deletion removes all Facebook data, and you may make a data request at any time. This is our Facebook data-deletion instruction.

A live video we created remains on your Page after the stream ends, like any Facebook broadcast; only you can delete it there.

AI video generation

AI Streams, where available on your plan, generates clips from instructions you write. It runs on a bring-your-own-key basis: you save an API key for your chosen provider, which bills you directly under your contract.

  • Your key. Stored encrypted at rest and hidden from our interfaces, logs and API responses. We retain the last four characters and a one-way fingerprint to identify keys and distinguish re-paste from rotation. We test it with one authenticated provider call; provider errors are stripped of anything resembling the key before recording. Replace or delete it at any time; it is deleted with the workspace.
  • What goes to the provider. Your instructions and clip parameters (length, aspect ratio and model), sent to the vendor you chose and authenticated as you. We do not send account details, viewer data or stream media. The vendor’s handling is governed by its terms and privacy policy; read them before use.
  • What we keep. Your instructions and generated clips on our infrastructure so the stream can play them. Played clips are deleted from disk. We also record our abuse-review result, a short excerpt and a hash so refusals are auditable.
  • Our review. Our abuse gate reviews instructions before generation in addition to the provider’s checks. This runs on our own infrastructure; instructions are not sent to another party for moderation.

Retention

Account and configuration data are kept while your account is active. Recordings are kept only for your plan’s retention window and then automatically deleted, sooner if you delete them or storage fills. Operational logs are pruned on a rolling basis. Invoices are retained as long as law requires after closure and pseudonymised. Safety reports and account-moderation records, including strikes and suspension/ban reasons, are retained while needed for moderation, legal and audit purposes.

Inactive accounts

If a free, unpaid workspace goes unused — nobody signs in and nothing streams — we do not keep it forever. Paid, demo and internal workspaces are not subject to this process.

  • Days 14, 30 and 60. We email you at most three times to explain that the workspace is idle and how to keep it.
  • Day 90 — archived. The workspace is hidden and relays stop, but nothing is deleted. Signing in restores it immediately. We email you when archived and explain when deletion follows.
  • Day 120 — permanently deleted. Your account record is deleted outright, not anonymised or retained as a placeholder, and so is the workspace itself with streams and destinations. Recordings, VOD clips, overlay media, stream loops, soundboard uploads, chat, captured leads, event/automation logs, connected-service credentials, webhooks and paired devices are deleted.

We keep only what is required. Invoices and payment records remain for the legally required period. Each invoice keeps its own workspace-name copy so it remains meaningful but is not attached to your name. If you paid, Stripe retains its transaction record, including name and card details, under its own policy, and our invoice retains its payment reference. Deleting here does not erase Stripe’s copy and we cannot delete it for you; ask Stripe or ask us and we will forward it. An anonymous audit entry recording that deletion happened remains.

A workspace is deleted only when your account is its last member. A workspace with other members continues and you are removed. Shared demo, internal-system-stream and administrator workspaces are never deleted by this process; instead they are closed and stripped of your content because deleting them would affect others.

You do not need to wait. Delete your account and data at any time from Settings → Privacy & your data.

Your rights

Under GDPR you may access, correct, export, restrict, object to, or delete your personal data. Logged-in users can download a copy and delete their account directly from Settings → Privacy & your data. For anything else, or without an active login, make a data request; we respond within one month. You may also complain to your local data-protection authority, in the UK the ICO.

Contact

Questions about this policy, our use of YouTube API Services, or exercising your rights? Email [email protected] or get in touch. Stream Repeater is operated by Joseph Taylor (United Kingdom), the data controller for the personal data described here, registered with the UK Information Commissioner’s Office under reference ZC237739 (view our entry on the ICO register).