Skip to content
Legal

Privacy Policy

Last updated November 15, 2026

Your privacy matters. This policy describes what data StreamRove collects, how we use it, and the choices and rights you have.

1. Introduction

This Privacy Policy explains how StreamRove, Inc. ("StreamRove", "we", "us") collects, uses, and shares information when you use our websites, apps, and services (the "Service").

By using the Service, you agree to the practices described here.

2. Information we collect

We collect the following categories of information:

  • Account information: your name, email address, and password (stored hashed).
  • Sign-in information: the IP address and browser of each device you are signed in on, kept with the session so you can see your devices and end one. It is deleted when the session ends or expires.
  • Channel connections: tokens and keys for the platforms you connect, stored encrypted at rest.
  • Usage data: streams created, destinations, analytics events, and device and log information. Website analytics on our public pages — Google Analytics and our own Umami — are described under Analytics below.
  • Billing information: handled by our payment processor; we do not store full card numbers.

3. How we use information

We use the information we collect to:

  • Provide, maintain, and improve the Service, including relaying your streams to your chosen destinations.
  • Authenticate you and secure your account.
  • Process payments and manage subscriptions.
  • Send service notifications and, where permitted, product updates.
  • Detect, prevent, and address fraud, abuse, and technical issues.

4. Sharing and disclosure

We do not sell your personal information. We share data only with service providers who help us operate the Service — hosting, live-streaming and storage providers, our payment processor, our email provider, and Google Analytics for public-website measurement — and when required by law or to protect rights and safety.

5. Service providers we use

These companies process data on our behalf so the Service can run. Each is bound by a contract that holds it to the obligations we have to you.

Our studio media server and our own website analytics run on our servers rather than a third party's.

Connecting a platform such as YouTube, Twitch, Kick or Facebook sends your video there because you asked us to publish it. Those platforms are your recipients, under their own policies, not our providers.

If you process other people's personal data through StreamRove, our Data Processing Addendum at /dpa sets out the terms and keeps this list current.

  • Hetzner Online GmbH (Germany) — the servers that run the application and its databases.
  • netcup GmbH (Germany) — the ingest relay at live.streamrove.com, which receives your encoder's stream and passes it straight on to our video provider. Nothing is recorded there.
  • Cloudflare, Inc. (United States, global network) — live video ingest, delivery and recording storage, our CDN, and the bot check on our forms.
  • Brevo (France) — the transactional email we send you: verification, login codes, alerts and support replies.
  • Creem — checkout, subscriptions, invoices and refunds, as merchant of record.
  • Google Analytics (United States) — public-website measurement, and only after you accept it on the consent banner.

6. Third-party platforms

When you connect a platform like YouTube, Twitch, Kick, Facebook, or TikTok, you authorize StreamRove to act on your behalf to publish streams. Those platforms process your data under their own privacy policies, which we encourage you to review.

If you connect your TikTok account, TikTok shares your open ID, display name and profile picture with us. We use them only to show which TikTok account is connected. We do not receive your videos, followers, messages or analytics, and we do not post to TikTok on your behalf. Removing the channel in StreamRove deletes this information together with the access token; you can also revoke StreamRove's access from the app permissions in your TikTok settings.

7. Cookies and tracking

We use cookies to keep you signed in and to remember preferences such as whether the sidebar is collapsed. These are necessary for the Service to work, and disabling them will break sign-in.

The only other cookies we set are the analytics cookies described in the next section, and they are set on our public marketing pages, not inside the signed-in app.

You can control cookies through your browser settings.

8. Analytics (Google Analytics)

We use Google Analytics 4 to understand how people find and use our public website — which pages get read, which links get clicked, roughly where visitors come from. It helps us decide what to build and what to explain better.

Where it runs matters, so we will be specific: the analytics tag is loaded on our public marketing pages only. It is not loaded inside the signed-in application, so what you actually do with the product — the streams you create, the channels you connect, who you broadcast to — is not sent to Google.

Google Analytics sets cookies (typically named _ga and _ga_*) and receives your IP address, approximate location derived from it, device and browser information, the page you are on, and the site that referred you. Google acts as our processor for this and processes the data under its own terms; Google Analytics 4 does not store full IP addresses.

We have not enabled Google Signals, advertising features, or remarketing, and we do not send Google any identifier that would let it link a visit to your StreamRove account.

  • To opt out in any browser: install Google's opt-out add-on at tools.google.com/dlpage/gaoptout.
  • Blocking cookies or using a tracker-blocking extension also stops it, and nothing on the site breaks if you do.
  • We ask before loading it. The analytics tag is not requested and no analytics cookie is set until you choose Accept on the consent banner — and if you decline, nothing is loaded at all. You can change your mind by clearing this site's data in your browser.

9. First-party analytics (Umami)

We also run Umami, an analytics tool hosted on our own servers. It counts page views on our public pages — which page, which site referred it, and a coarse device and country.

It sets no cookie and stores nothing on your device, which is why it is not behind the consent banner: there is nothing on your device to ask permission for. Your IP address and browser are turned into a short-lived, non-reversible identifier so one visit is counted once; the address itself is not stored.

Like Google Analytics, it runs on the public website only, never inside the signed-in application. We rely on our legitimate interest in knowing which pages are read; to object, write to [email protected].

10. The Chrome extension

The StreamRove extension for Chrome shows which of your streams are live and lets you switch destinations on and off from the toolbar. It is optional. This section covers only what it adds to the rest of this policy.

It signs in through the same device link as the OBS plugin: you approve a code on streamrove.com, and the extension collects a key that works only on the extension's own routes. That key cannot read a stream key, change your account or delete anything.

  • Kept in your browser, on your computer only: the key you approved, your account's name and email, the names of your workspaces and plans, the streams of the workspace you picked (title, status, source and the platforms of the destinations that are on), your latest 20 notifications (title, text and link), and two settings, desktop alerts on or off and the workspace you chose.
  • While you sign in, the one-time code the extension collects its key with is held in memory only and dropped once the key arrives.
  • The extension talks only to streamrove.com, with its own key and without your browser's cookie for the site. It has no other servers, no analytics, no ads and no remote code. Its only host permission is streamrove.com, so it does not read web pages, tabs or your browsing history.
  • Desktop notifications are shown by your browser on your computer. You can switch them off in the extension's menu.
  • Signing out in the extension revokes its key on StreamRove and deletes everything it keeps. Removing the extension deletes the stored data too, and you can revoke the key at any time under Account settings, API keys.
  • On our side, the key is listed under API keys with a name such as “Chrome extension · Google Chrome on Windows” and the time it was last used. A revoked key's row is kept, marked as revoked, for the audit trail.
  • The IP address of the browser that started the sign-in is stored with the sign-in request and shown on the approval page. Once an hour has passed since the request's ten-minute code expired, it is deleted the next time anyone starts a sign-in.

11. Data retention

We keep your information for as long as your account is active or as needed to provide the Service. When you delete your account, we delete or anonymize your personal data within a reasonable period, except where retention is required by law.

One thing outlives the account: if you used a free trial, paid for a plan or used a discount code, we keep a keyed hash of the email address it was under, so that one-per-person trials and first-purchase offers are not reset by deleting the account and creating it again. The hash cannot be turned back into your address, and it is used for nothing else.

Some things have a shorter, fixed life whatever your plan: chat messages collected from a connected platform for the chat panel and the OBS overlay are deleted six hours after they arrive. Chat you choose to show on a broadcast — in a chat column or as a featured message — becomes part of the broadcast's picture: it stays in the recording, and on the platforms you streamed to, for as long as they are kept. Recordings and analytics follow the retention windows your plan lists.

A name and email address left at an access gate belong to the customer who put the gate up, and we hold them on that customer's behalf: they are deleted twelve months after that viewer last used the link, and immediately if the gate or the account is deleted.

When your encoder connects through our ingest relay, we keep a record of the connection — the encoder's IP address, the protocol, when it started and ended, and how much data arrived — for 90 days, to investigate faults and abuse. The video itself is passed on through the relay, not stored there.

12. Security

We use technical and organizational measures to protect your data, including encryption of sensitive credentials at rest and in transit. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

13. Your rights

Depending on your location, you may have the right to:

  • Access, correct, or delete your personal information.
  • Object to or restrict certain processing.
  • Request a portable copy of your data.
  • Withdraw consent where processing is based on consent.

14. International transfers

We may process and store information in countries other than where you live. Where required, we use appropriate safeguards to protect your data when it is transferred internationally.

15. Children's privacy

The Service is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has provided us data, contact us and we will delete it.

16. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email or through the Service before they take effect.

17. Contact us

If you have questions or requests about your privacy, contact us at [email protected].