Skip to content

In short: we collect what we need to relay your streams, show your live comments and bill you. Creem handles payments and Mux relays your video. Live comments are kept for 30 days. Stream keys and tokens are encrypted at rest. We do not sell your data or use it for ads.

Who we are

Beamcast sends your live video to many platforms at once and shows the comments from all of them in one place. Beamcast is the service described on this website. This policy explains what personal data we handle when you use the website and the Service, and what we do with it. Contact us about privacy at support@beamcast.stream.

What we collect

  • Account details: your name, email address and password. Passwords are stored only as a salted hash. If you sign in with Google or Zoom instead, we receive your name, email address and profile picture from that provider.
  • Session and security data: the IP address and browser user agent of each signed-in session, used to keep your account secure.
  • Streaming setup: the channels you add (platform, name, server URL and stream key), your Beamcast ingest key, live status reported by the relay, and the start and end times of each broadcast so we can measure monthly streaming hours.
  • Connected platform accounts: when you connect Zoom, Google (YouTube), Twitch, Facebook or Kick, we store your account ID on that platform, the permissions you granted and the OAuth access and refresh tokens it issued. For one-click channels we also store the destination's ID and name (YouTube channel, Facebook Page, Twitch or Kick channel) and, for Facebook Pages, a Page access token.
  • Zoom meetings and webinars: the topic, ID and start time of your meetings and webinars, read when you pick one to stream. When you go live we set that meeting's custom live stream settings (stream URL, stream key and page URL) and start or stop its live stream, and Zoom tells us when the meeting starts and ends.
  • Connected social accounts: for each account you connect, the platform, account ID, username, display name, avatar and related account details returned by Zernio.
  • Messages and comments: conversations, comments and replies are fetched through Zernio when you use the inbox, and the replies you write are sent through Zernio. Notifications from our providers about new activity may include message details and are logged so they can be processed reliably.
  • Live comments and viewer counts: while you are live, the public comments people post on your live streams (their display name, profile picture link, message, time and platform) and the viewer counts each platform reports. Where you tell us your channel (for example your YouTube @handle or TikTok @username), we use it to find your live stream.
  • Watch page visitors: people who watch on your Beamcast watch page can chat there. We store the name they choose, their message and a random ID in a cookie, and we use their IP address briefly to stop spam. To count viewers, their browser sends a small “still watching” signal.
  • Live Helper and Cloud Helper: if you use the Live Helper browser extension, we store a name for the device and a scrambled (hashed) copy of its access token, plus which platforms it is reading. The helper sends us the comments and viewer counts it reads from your own live pages. If you use the Cloud Helper, we run a browser for you with a separate profile that keeps your sign-in for the sites you sign in to there, so it can read your comments and post your replies while you are live.
  • Instagram stream details: the one-time stream address and key Instagram gives you for each live, which you send toBeamcast so we can deliver your tall (9:16) video.
  • Billing records: your plan, billing period, subscription status, renewal date and the customer and subscription IDs Creem gives us. We never receive or store your full card details.

Your live video

When you go live, Zoom or your streaming software sends video to Mux, which relays it to the channels you switched on. For Instagram, and for TikTok if you choose it, our servers also read the stream and make a tall (9:16) version. We use your video only to provide these features, we don't record it, and the platforms you stream to receive it under their own terms and privacy policies.

How we use data

We use the data above to:

  • create and secure your account and keep you signed in;
  • relay your streams and show each channel's status;
  • create the live events and fetch the stream keys your one-click channels need before each broadcast, and start and stop the Zoom live stream you chose;
  • show live comments and viewer counts, and your messages and post comments if you turn that on, and deliver your replies;
  • apply plan limits, process subscriptions and send account and billing emails;
  • prevent abuse, fix problems and keep the Service running.

We do not sell your personal data, and we do not use your messages or video for advertising.

Google and YouTube data

Beamcast uses YouTube API Services. When you connect a Google account for YouTube, we use the access you grant to read the ID and name of the YouTube channel you choose and to create, update, bind and end the live broadcasts and live streams for your shows on that channel. Separately, to show live chat and viewer counts, we read the public live chat and viewer count of the YouTube channel you tell us about, using YouTube API Services with our own API key. We do not use YouTube or other Google user data for advertising, and we do not sell it or share it except to run the features you asked for.

Our use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements. Google's own handling of your data is described in the Google Privacy Policy.

You can disconnect Google from Settings in Beamcast, which deletes the tokens we hold. You can also revoke Beamcast's access at any time from the Google security settings page. Questions about these practices: support@beamcast.stream.

Who processes your data

We share data only with the providers that run parts of the Service, and only what each needs:

  • Creem is our merchant of record. It runs checkout, processes payments, calculates taxes and hosts the billing portal. Your payment details go directly to Creem.
  • Mux receives your live video and the stream keys of your enabled channels so it can relay the stream to them.
  • Zernio connects your social accounts through each platform's sign-in flow and provides access to your messages and comments.
  • Zernio is used only if you turn on messages and post comments.
  • Railway hosts the Service, its database and our own browser and video servers. Cloudflare runs our domain's DNS. Resend sends account emails such as password resets.
  • Euler Stream receives the TikTok @username we are reading so it can open the connection to your TikTok LIVE comments.
  • Social Stream Ninja's public service may be asked for viewer counts or profile pictures when the Live Helper reads YouTube or Twitch pages.

The destinations you stream to and the social platforms you reply on receive your stream and replies because you asked us to send them. Zoom, Google (YouTube), Twitch, Meta, Kick and TikTok receive the requests we make to read your live comments and viewer counts, and the requests we make on your behalf for the accounts you connected. We may also disclose data where the law requires it.

Security

Stream keys are encrypted at rest with AES-256-GCM and decrypted only when they are handed to the relay; the dashboard shows them masked. OAuth tokens for connected platforms are encrypted at rest and only decrypted to call that platform for you. Passwords are hashed, connections to the Service use HTTPS, and access to production data is limited to what is needed to operate the Service. No system is perfectly secure, so please tell us at support@beamcast.stream if you find a problem.

Cookies

We use a session cookie to keep you signed in and a small cookie that remembers whether your sidebar is open. Your watch page sets a random ID cookie for viewers who chat. We do not use advertising or cross-site tracking cookies. Creem may set its own cookies on its checkout and billing pages.

How long we keep data

Live comments and viewer counts are kept for 30 days and then deleted. Watch page “still watching” signals are kept for one day. Everything else is kept while your account is open. You can delete channels, remove Live Helper devices, turn off the Cloud Helper and choose to forget its saved sign-ins, disconnect social accounts and disconnect Zoom, Google, Twitch, Facebook or Kick at any time from the dashboard (disconnecting deletes the tokens we hold), and you can also revoke Beamcast's access from each platform's own settings. When you ask us to delete your account we delete its data, except records we must keep for legal, tax or accounting reasons. Creem keeps its own transaction records as the merchant of record.

Your rights

Depending on where you live, you may have the right to access, correct, export or delete your personal data, and to object to or restrict how we use it. Email support@beamcast.stream and we will respond within the time the law requires. You may also complain to your local data protection authority.

International transfers

Our providers may process data in the United States and other countries. Where the law requires it, these transfers rely on appropriate safeguards such as standard contractual clauses.

Children

The Service is not directed at children, and you must be an adult to create an account.

Changes to this policy

We will post any changes here and update the date at the top. For material changes we will also notify you by email before they take effect.