Privacy Policy

Only what the service needs to work.

• Account: your name, email address, password hash, language and timezone.
• Workspace: its name, members and their roles, and your plan and billing status.
• Destinations: the platform accounts you connect, the access and refresh tokens they issue, and any RTMP address and stream key you enter.
• Broadcasts: title, description, which destinations you published to, when it started and ended, and per-destination technical telemetry such as bitrate, frame rate and dropped frames.
• Chat messages read from platforms during a broadcast, so they can be shown in one column. They are deleted thirty days after they were sent.
• Operational: IP address and browser user agent for each session, and an audit entry for every state-changing action.

We do not run third-party advertising or analytics trackers. We do not sell personal data. We do not read or profile the content of your broadcasts beyond what is needed to relay them, and we do not use your video to train models.

Platform tokens, RTMP stream keys and webhook signing secrets are encrypted with AES-256-GCM before they are written to the database, and are decrypted only at the moment a broadcast starts or you explicitly ask to see one.

Passwords, session tokens, API keys and ingest keys are stored as digests, not as recoverable values. We cannot tell you your password or an old API key, because we do not have them.

Log output passes through a redactor that strips anything matching the shape of one of our credentials.

Streamer Hub uses YouTube API Services. By connecting a YouTube channel you agree to be bound by the YouTube Terms of Service (https://www.youtube.com/t/terms), and what Google itself does with your data is governed by the Google Privacy Policy: http://www.google.com/policies/privacy.

Connecting a YouTube channel grants this service two Google OAuth scopes: .../auth/youtube and .../auth/youtube.force-ssl. They exist here for one purpose — putting the broadcast you started on the channel you chose, and bringing that broadcast's live chat back to you while it runs.

Specifically, they are used to read the connected channel's name, handle and avatar so you can tell your destinations apart; to create a live broadcast and a live stream, bind them, and transition the broadcast to live once video is actually arriving; to apply the title, description, privacy and category you typed here; to read the live chat and the concurrent viewer count for the duration of the broadcast; and, when you act on your chat column, to send a message to that chat as the connected channel, to delete a message, to time out or ban its author, and to lift a ban we issued. The force-ssl scope is used for the chat and moderation calls and for nothing else.

We do not read, download or store your videos. We do not read your subscriptions, your watch history, your playlists, or any channel other than the one you connected. Google user data is never used for advertising, never sold, and never used to develop, improve or train generalised artificial intelligence or machine learning models. Who does receive it, and how it is protected, is set out in the two sections that follow.

Streamer Hub'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.

The OAuth tokens are encrypted at rest exactly as described above. Nobody here reads Google user data, except where you have asked for support and given permission, or where the law or an investigation of abuse requires it.

You can disconnect a YouTube account at any time under Destinations, which deletes our copy of its tokens, and you can revoke access independently of us at https://security.google.com/settings/security/permissions.

This is the complete list of information about you, your YouTube channel and its viewers that this service obtains through YouTube API Services: what each item is used for, where it is kept and when it is deleted. Nothing outside this list is requested, collected or stored.

• OAuth access and refresh tokens, and the scopes you granted. Used only by our servers to make the calls listed in this policy on your behalf. Stored encrypted with AES-256-GCM. Deleted the moment you disconnect the channel, or thirty days after the connection stops working.
• Your channel's id, title, handle and avatar address (channels.list for your own channel). Used to show which channel a destination is. Read again from YouTube every day while the connection works; deleted when you disconnect, and cleared thirty days after the connection stops working.
• The ids of the live broadcasts and live streams we create on your channel, and the broadcast's watch address. Used to start, end and link to your broadcast. Kept with the broadcast record. The ingestion address and stream key YouTube returns for a broadcast are handed to our relay while it runs and are not stored.
• Live chat of your own broadcast: each message's id, text and time, and its author's channel id, display name, profile picture address and moderator or owner flag (liveChatMessages.list). Used to show the chat in one column while you are live and to let you reply and moderate. Deleted thirty days after the message was sent.
• Moderation records: when you time out or ban a viewer, their channel id and display name and the ban id YouTube returns (liveChatBans.insert). Used to enforce and later lift the ban. Kept while the ban is in force; deleted thirty days after it is lifted or lapses.
• The concurrent viewer count of your live broadcast (videos.list, liveStreamingDetails.concurrentViewers). Shown, labelled as YouTube's own number, while you are live and in your analytics. YouTube viewer counts are neither shown nor stored for more than thirty days: after that they are deleted, even on plans whose analytics history is longer.
• What we send to YouTube rather than read from it: the title, description, privacy setting and category you type for a broadcast, and the chat replies you write in our chat column.
• We do not access your videos, uploads, playlists, subscriptions, comments outside your live chat, watch history, YouTube Analytics or revenue data, or any channel other than the one you connected. No metric is derived from YouTube data, and it is not combined with other platforms' data beyond being displayed next to it.

We do not sell Google user data. We do not share, transfer or disclose it to any third party for that party's own purposes: there is no advertiser, no data broker, no analytics company and no AI vendor anywhere in this product.

Apart from the providers listed below, we disclose Google user data only in three situations: where a binding legal request obliges us to, where it is necessary to investigate abuse or a security incident, or where you have asked us to — for instance when you attach a screenshot to a support conversation. If this service were ever sold or transferred to another company, Google user data would move with it only under a policy no less protective than this one, and you would be told before that happened.

The providers below are processors. Each acts only on our instructions, receives only what its job requires, and has no right to use your data for anything of its own.

• OVHcloud, our hosting provider. The servers and the database that hold your encrypted YouTube tokens, your broadcast records and your chat history are operated by them.
• The provider that delivers our transactional email, which receives the email address on your account together with the message we are sending you. We will name the current provider on request.
• Google itself, when we call the YouTube Data API on your behalf — the data goes back to where it came from.

Google user data, and the OAuth tokens above all, is treated as the most sensitive thing in this database, because a token is the account.

• In transit: every connection to hub.streamer.ge is HTTPS over TLS 1.2 or higher, and every call we make to Google's APIs is made server-side over TLS.
• At rest: access and refresh tokens are encrypted with AES-256-GCM before they are written to the database. The encryption key lives in the server's environment and not in the database, so a copy of the database alone yields nothing usable.
• Never in the browser: Google tokens are used only by our server processes. They are never sent to your browser, never written to a cookie or to client-side storage, and never placed in a URL.
• In logs: log output passes through a redactor that strips anything shaped like a credential, so a token cannot survive into a log file or an error report.
• During authorisation: the OAuth exchange uses PKCE and a single-use, short-lived state value, so an intercepted redirect cannot be replayed.
• On the machine: administrative access is key-based SSH to named accounts with root login disabled, the firewall denies by default, repeated failed authentication is banned automatically, the environment file holding the encryption key is readable only by the account that runs the service, and the database grants access to this application's own role alone.
• Inside the product: a member sees only the workspaces they belong to, every state-changing action is written to an audit log, and nobody here reads Google user data except with your permission during support, or where investigating abuse or complying with the law requires it.
• Minimisation: we hold the tokens, the connected channel's name, handle and avatar, the ids of the broadcasts we created for you, the chat of those broadcasts and their concurrent viewer counts, exactly as listed under YouTube API Data above. Nothing else from your Google account is requested or kept.
• Retention: chat is deleted thirty days after it was sent, and YouTube viewer counts thirty days after the broadcast. The connected channel's name, handle and avatar are read again from YouTube every day while the connection works; once a connection has been broken for thirty days, its tokens are deleted and those details are cleared.
• Deletion: disconnecting a destination deletes our copy of its tokens immediately. Deleting your account revokes every session at once and permanently erases the account fourteen days later. You can revoke our access independently at any time at https://security.google.com/settings/security/permissions.

Only the processors the service depends on, and only what each one needs.

• The destination platforms you choose, which receive your video and the broadcast metadata you set.
• Keepz, our payment provider, if you are on a paid plan. We never see or store your card details.
• OVHcloud, which hosts the servers and the database this service runs on.
• The provider that delivers our transactional email, which receives your email address and the message being sent to you.

Your video is not stored at all • it is relayed as it arrives and nothing is written down. Broadcast telemetry, which is bitrate, frame rate and viewer counts rather than pictures, is kept for the analytics history window in your plan, except that viewer counts from YouTube are deleted after thirty days.

Chat messages read from any platform are deleted thirty days after they were sent, and a chat block thirty days after it was lifted or lapsed. A block still in force is kept for as long as it is in force.

When you delete your account, it is deactivated immediately and every session is revoked. Fourteen days later, a job permanently removes your account and the workspaces you solely own, and cancels any subscription. The grace period exists so an accidental or hostile deletion can be reversed.

Audit entries are retained after deletion in a form that no longer identifies you, because they are the record of what happened to other people's data too.

You can see and correct most of your data directly in Settings. For a copy of everything we hold, or for erasure ahead of the normal timeline, write to us and we will respond within thirty days.

If you are in the EEA or the UK you have the rights granted by the GDPR, including the right to complain to your supervisory authority.

For any question about this policy, about your data or about how this service uses YouTube API Services, or to ask for a copy or the deletion of your data, contact us:

• Operator: Streamer Hub is operated by Darejan Natelashvili, Georgia.
• Address: 88 Ivane Javakhishvili St, Tbilisi, Georgia.
• Email: info@streamer.ge. Privacy, data and YouTube questions are answered within thirty days, usually within two working days.
• Inside the product: paid workspaces can also write to us from Support.

We set two cookies. One holds your session and is strictly necessary. One remembers your light or dark theme preference. Neither is used for tracking. See the Cookie Policy.