Privacy Policy
In accordance with Regulation (EU) 2016/679 (GDPR) and the French Data Protection Act.
Last updated:
1. Data controller
The controller of personal data collected through RelayHalo is Neticop (SIRET 851 214 874 00022). For any question regarding your data: contact@relayhalo.com.
2. Data we collect
We collect the following data:
- Account data: email address, password (hashed), display name.
- Connection data: IP address, browser, connection date and time, language.
- Usage data: pages visited, features used.
- Billing data: payment information handled by Stripe — we do not store full card numbers.
3. Purposes
Your data is used to:
- provide and improve the service;
- manage your account and payments;
- send transactional emails (account, password reset, billing);
- ensure the security of the service;
- comply with our legal and accounting obligations.
4. Legal basis
Processing is based on the performance of the contract you accept on sign-up (Terms), your consent where required, our legitimate interest in improving and securing the service, and our legal obligations (notably accounting).
5. Retention
We keep your data as long as your account is active. After account deletion, certain data may be retained for legal and accounting reasons — typically up to ten years for invoices, in line with applicable tax obligations in France.
6. Sharing
We never sell your data. It may be shared with:
- Stripe — payment processing (transfers covered by the EU Standard Contractual Clauses).
- o2switch — data hosting, servers located in France.
- Any authority legally entitled to make such a request.
7. Your rights
Under the GDPR, you have the following rights:
- Access: obtain a copy of your data.
- Rectification: correct inaccurate data.
- Erasure: request deletion of your account and data.
- Portability: receive your data in a structured format.
- Objection: object to certain processing.
- Restriction: request the temporary suspension of a processing activity.
To exercise these rights, contact us at contact@relayhalo.com. You may also lodge a complaint with the French data protection authority (CNIL — www.cnil.fr).
8. Cookies and audience measurement
RelayHalo places no advertising cookie and no third-party tracker. The cookies used are:
- Strictly necessary: the authentication session cookie and your display preferences. These require no consent.
-
Audience measurement (
an_id): a first-party identifier valid for 13 months and not renewed on each visit. It lets us count visitors and see which pages and which sources actually bring people here. It is read only by this site, is never shared, and is never combined with data from any other site. Your IP address is masked (the last part is discarded) to derive a country and is then dropped — it is never stored. Detailed events are kept for 90 days, visit summaries for at most 25 months, and anonymous aggregates without time limit.
This measurement is carried out for our own account only and produces anonymous statistics, which is why French law exempts it from prior consent. It is not used to link your browsing to your account unless you accept analytics cookies in the banner — that link is a separate matter and it does require your consent.
You can object at any time. The button below stops the measurement for this browser, deletes its identifier and prevents any further recording. Your browser's Do Not Track and Global Privacy Control settings are also honoured automatically.
9. Security
Your data is protected by appropriate technical measures: encryption in transit (HTTPS), hashed passwords (Argon2id), restricted database access, and logging of sensitive accesses.
10. Minors
The service is not intended for persons under 15. If we learn that an account has been created by a minor without the consent of their legal representatives, we will delete it.
11. Updates
This policy may be updated. In the event of a substantial change, you will be notified by email or through the service. The last update date is shown at the top of this page.
12. Stream keys and linked platform accounts
- Destinations. The RTMP addresses and stream keys of your destinations (YouTube, Twitch, Kick and others) are stored encrypted (libsodium secretbox) and sent only to our relay servers, which forward your stream to those platforms. Our relay servers are located in France.
- “Connect with…”. When you link a YouTube, Twitch or Kick account, the platform gives us an access token and usually a refresh token. Both are stored encrypted, are never written to our logs, and are used only for the features described on this page. You can remove a link at any time with “Disconnect” in your dashboard: we ask the platform to revoke the grant and delete the tokens at once. The destination created from the link stays in your list, with its stream key, until you delete it.
- Account deletion. Deleting your RelayHalo account deletes your linked accounts, destinations and their keys, and we ask each platform to revoke the grants.
13. Google and YouTube data
RelayHalo uses the YouTube API Services. By linking a YouTube channel you agree to be bound by the YouTube Terms of Service; Google’s handling of your data is described in the Google Privacy Policy.
Limited Use. RelayHalo’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features you ask for below. We never sell it, never use it for advertising, never use it to train artificial-intelligence models, and no person reads it except with your explicit consent for support, for security, or to comply with the law.
Permissions we ask for
-
youtube.readonly(“View your YouTube account”). Used to read: your channel’s id and name; the ingest address and stream key of your live streams, so your YouTube destination is filled in and kept up to date before each live; your active live broadcast (its id, title and status), to find the live you are streaming; and that broadcast’s current number of concurrent viewers. -
youtube.force-ssl(“See, edit, and permanently delete your YouTube videos, ratings, comments and captions”). Asked only to change the title of your live: when you send a title from the “Titles” page, or when the video on air changes on a 24/7 channel whose title sync you switched on, we update the title of your currently active live broadcast and, if you chose a category, the category of that broadcast’s video. To do so we read the broadcast and its video details (description, tags, scheduled times) and send them back unchanged, because YouTube replaces them as a whole. We never upload, delete or edit any other video, and never touch comments, ratings, captions or playlists.
How we use it
- Destinations: the stream key and ingest address go to our relay so it can send your stream to YouTube.
- Viewer counts (paid plans): while you are live, the count is read at most about once a minute and added to your total across platforms.
- Title sync: the title and category you choose are written to your active live, as described above.
- Going-live notifications (if you set them up): the title and link of your active live are read when the message is sent and posted to the Discord webhook you configured. They are not stored.
- Public live page and overlays (only if you switch them on): your channel name, viewer count and an embedded YouTube player are shown on your public page or in your OBS overlays.
Storage and retention
- Tokens: encrypted, kept until you disconnect the account, delete your RelayHalo account, or revoke access from Google (we then delete them within a day).
- Channel id and name, stream key: kept with the link and the destination, as described in section 12.
- Per-minute viewer counts: deleted after 30 days. Only each live’s peak and average, totalled across platforms, stay in your live history.
- Title changes: the titles you type are kept as your settings; a log of each change (platform, result, quota used, no content) is deleted after 30 days.
- Data is stored on servers located in France (see section 6).
Sharing
Google user data is not shared with anyone, except: the stream key and ingest address, which go to our relay servers in order to reach YouTube; what you choose to publish yourself (public live page, overlays, your Discord webhook); and any authority legally entitled to request it.
Revoking access and deletion
- In RelayHalo: “Disconnect” on your YouTube link revokes the grant and deletes the tokens immediately.
- In your Google account: you can revoke RelayHalo’s access at any time on the Third-party apps & services page (also reachable at security.google.com/settings/security/permissions). We detect the revocation within a day and delete the link and its tokens.
- To have all YouTube data we hold deleted, delete your account or write to contact@relayhalo.com: we do it within 7 days.
Cookies
RelayHalo itself places no cookie for YouTube. An embedded YouTube player, shown only on public live pages whose owner switched it on, is served by YouTube, which may set its own cookies or read your device under the Google Privacy Policy.
Questions about this section: contact@relayhalo.com.