Privacy Policy
Last updated: 14 November 2026
This Privacy Policy explains how ZigZagStream ("we", "us", "our") collects, uses, shares and protects personal information when you use our multistreaming service (the "Service"). With the Service you send one stream from your streaming software (for example OBS) to our servers, and we pass it on to the destinations you choose: YouTube, Twitch, Kick, Facebook, any RTMP server and, in Iran, Aparat. We run the Service in two regions, Iran and Global. Your account lives in one of them, chosen from the country you stream from.
1. Information we collect
1.1. Your account. Your name, e-mail address, the language and time zone you choose and, if you sign in with Google, the stable ID of your Google account (we keep no Google token for a sign-in). We sign you in with a one-time code sent to your e-mail address and keep only a one-way fingerprint of each code, for a few minutes. For accounts in Iran we also keep your mobile number, verified with an SMS code at sign-in. We record the country you signed up from (worked out on our own servers from a local database, without sending your address anywhere) and, once you choose them, the country you stream from and the region your account lives in.
1.2. Your YouTube channel. When you connect a channel and give consent on Google's own screen, we receive the channel's ID, name, handle and picture, and the access and refresh tokens Google issues for that consent. We ask only for read-only access (see section 5).
1.3. Live streaming. Your stream passes through our servers on its way to the destinations you choose; we do not record it. We keep each destination's stream key and full server address encrypted (only the server's host name stays readable, so we can show it to you). If you choose to get a destination's key from Kick or YouTube instead of copying it, we receive that key directly from the platform and store it like any other key. If you allow us to set your stream title on Twitch or Kick, we keep the permission those platforms give for it (encrypted, with the channel's name) and the last title you wrote, and use them only to change that channel's title when you save it; you can withdraw the permission at any time on the destination's card. While your broadcast is live and the streaming studio is open, we show you the chat of your destinations and the live viewer count of YouTube, and keep them only as a temporary copy for at most three hours. If you turn on the chat bot, while your broadcast is live on Kick another of our servers reads that channel's chat through Kick's official interface, so that the bot can answer your commands, thank your supporters, post your timed messages and apply the filters you set. It keeps none of the messages: it remembers only when a viewer's message was last removed by a filter, for at most a day, and we keep the number of answers, removed messages and timeouts of each broadcast. While you prepare a broadcast, only you can watch its preview. Once you go live, the members of our team who manage live streaming can also watch it, to check its quality and that our terms are followed; each time they do, it is logged.
1.4. Overlays. If you use an overlay (an alert, chat or text layer you add to your broadcast through a link in your streaming software), it shows on your broadcast the names, messages and support events of your viewers that we already read for your live chat. For a goal bar or a counter we keep the running totals of a broadcast's support (amounts and counts, without names) for a day, and the totals of all your broadcasts (amounts and counts only) until you delete your account. For a "top supporter of the week or month" counter we keep the display name of each supporter and the approximate amount, only for the current and the previous week or month. So that you can replay an alert, the last support events of a broadcast (names, amounts and messages) are kept for an hour. If you turn on reading messages aloud, your own browser or streaming software reads them with your computer's speech voices; we send them nowhere for this. The images, sounds and videos you upload for an overlay are kept until you remove them or the overlay. Anyone who has an overlay's link can open it, so keep it private; you can replace the link at any time. If you turn on sharing for an overlay, anyone who has its share code can make a copy of its layout, texts and uploaded files in their own account until you turn sharing off or replace the code; copies already made stay with the people who made them. A copy never includes the overlay's link, your events or your supporters. When you create a ready-made skin, the handle of your connected YouTube channel is written into its social media widgets, which show on your broadcast; you can change or remove it.
1.5. Donations. If you turn on donations, viewers can support you on your donation page. In Iran, donations are paid through ZarinPal and your share goes straight to the bank account (IBAN) you enter: we keep that IBAN encrypted, show only its last four digits and send it only to the payment gateway, with each donation. Elsewhere, donations are paid through Stripe and your share goes to the Stripe account you connect, whose details Stripe collects on its own pages. For each donation we keep the amount, the time, the payment reference and the name and message the supporter wrote (both optional). The name and, once it is approved or needs no approval under the rules you choose, the message are shown on your broadcast through your overlays and, while "recent supporters" is on, on your donation page. If you support a streamer, you need no account: the name you write (or "anonymous") and your message are seen by the streamer and may be shown on their broadcast and donation page. Card details are entered only on the payment provider's own page and never reach us. The members of our team who manage live streaming can see donations, with the supporters' names and messages, to handle reports of abuse.
1.6. Plans and payments. If you buy a plan, we keep the plan, its price and period, and the result and reference of each payment. Payments are made on ZarinPal's page in Iran and on Stripe's elsewhere; we never receive your full card number, its expiry date or its security code.
1.7. Support and messages. Your support tickets and their attachments, the notifications we show you in the Service, and the e-mails we send you.
1.8. Sign-ins and technical data. The time, IP address, device, browser and country of each sign-in; how many wrong codes were typed from a network, so that guessing can be stopped; and the technical logs of our servers, which we use to keep accounts secure and to fix problems.
2. How we use your information
- to provide the Service: receiving your stream and passing it on, and running your destinations, overlays, chat bot, donations, plan and support tickets;
- to keep accounts secure: sign-in codes, stopping networks that guess codes, and detecting abuse and fraud;
- to tell you about your account and the Service, for example sign-in codes, replies to your tickets and problems with a broadcast;
- to understand and improve how the Service is used (section 4); and
- to meet legal, accounting and tax obligations.
Where data protection law requires a legal basis, we rely on performing our contract with you; your consent (for example connecting a YouTube channel, which you can withdraw at any time); our legitimate interests in security and in improving the Service; and our legal obligations.
3. Who we share information with
We do not sell personal information and we do not let anyone use it to advertise to you. We share it only as needed to run the Service:
- Google: sign-in with Google, the YouTube Data API (section 5) and Google Analytics (section 4);
- Microsoft: Microsoft Clarity (section 4);
- the platforms you stream to (YouTube, Twitch, Kick, Facebook, Aparat or the server you enter): your stream and, through their official interfaces, what you ask us to do there, such as getting a stream key, setting a title, reading chat or running the chat bot;
- Kavenegar (accounts in Iran): to deliver SMS sign-in codes to your mobile number;
- ZarinPal and Stripe: to process payments and donations and, for a donation, to pay the streamer's share;
- our e-mail delivery provider: to deliver the e-mails we send you;
- authorities: when the law requires it, or to protect the rights and safety of our users and of ZigZagStream.
Our own servers are in more than one country: your stream, the e-mails we send and the chat messages shown in the studio pass between them over encrypted connections. Our providers may process information in other countries, under their own privacy policies and security measures.
4. Analytics and cookies
4.1. Google Analytics. We use Google Analytics (Google LLC) to understand how the Service is used. Your browser loads Google's script and sends Google the address of the page without its query string (only campaign parameters such as utm_source are kept), the page's name, the domain of the site you came from, and your browser, device and approximate location. We never send your name, e-mail address, phone number or account ID. Google Analytics is not loaded on administration pages, on sign-in pages or on pages whose address contains a code or key. It uses the cookies _ga and _ga_*. You can learn more in the Google Privacy Policy and opt out with the Google Analytics opt-out browser add-on.
4.2. Microsoft Clarity. On the pages of your signed-in panel we use Microsoft Clarity to see how pages are used (clicks, scrolling and session replays), so that we can find and fix problems. The header and the whole content area of every panel page are masked, so a replay shows only the layout, the menu and where you click or scroll, never your channel, keys, messages or other content. Clarity is not used on administration pages, on sign-in pages or on pages whose address contains a code or key. It uses the cookies _clck and _clsk. See the Microsoft Privacy Statement.
4.3. Our own cookies. A session cookie and a security cookie (XSRF-TOKEN); a cookie with your browser's time zone, so that dates are shown in your local time; and your choice of language, kept with your session. Your browser's local storage keeps your theme and menu preferences. You can block or delete cookies in your browser's settings; signing in needs the session cookie.
4.4. Content from other services. The streaming studio can show YouTube's, Twitch's and Kick's own chat windows for your destinations; they are served by those platforms and may set their own cookies under their own privacy policies. Our pages load their fonts and styles from our own servers, but an overlay and its editor load the fonts you choose for it from Google Fonts, which receives your IP address and browser details; an overlay never sends it its link. When you add a Twitch or Kick destination we store its chat channel name, and while you are live one of our servers reads that public chat, so the studio can show it when the platform's own window cannot load.
5. Google user data and YouTube API Services
5.1. The Service uses YouTube API Services. By connecting 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.
5.2. What we access and why. We ask Google only for the access the features need: "View your YouTube account" (read only), to show your channel's name and picture, to get a stream key for a YouTube destination when you ask for it, and to read the live viewer count and chat of your own broadcast while it is live and the studio is open; and, to sign you in with Google, your e-mail address and basic profile. We never upload, change or delete anything on your channel.
5.3. Storage. The tokens Google issues for your channel are stored encrypted on our servers for as long as the channel stays connected, and are renewed regularly, also to check that the connection still works. What we read from YouTube about your channel (its name, handle and picture) is read again from YouTube every day while it is connected; if it cannot be read for 30 days it is deleted, and it is deleted at once when you disconnect the channel. A stream key you get from YouTube is treated the same way: it is read again every day while the channel stays connected, and deleted together with its destination if it cannot be read for 30 days or when you disconnect the channel. The live viewer count and chat are kept only as a temporary copy for at most three hours.
5.4. Sharing and access. We do not sell Google user data and do not use it for advertising. We share it only to provide the features described above or when the law requires it. No Google user data reaches Google Analytics or Microsoft Clarity (section 4). Authorized members of our team can see your connected channel's name and ID in our administration panel, only to give you support. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
5.5. Revoking access. You can disconnect your channel at any time on your account page. Its tokens and the data we read from YouTube are then deleted at once, and at the same moment we ask Google to revoke the access you gave the Service. The one exception is when another account on the Service has connected the same channel with the same Google permission: revoking it would end that connection too, so the access stays at Google until the last such connection is removed. You can also remove the Service's access yourself at any time on the Google security settings page; when we next find that the access is gone (we check every day), we remove the connection and its data. Deleting your account does the same.
6. Security
The Service is served over encrypted connections (HTTPS). Google tokens, stream keys, destination addresses and bank account numbers are stored encrypted, and our team's access is limited to the areas each person needs. No system is completely secure, and we cannot guarantee absolute security.
7. How long we keep information
- Account information: while your account exists.
- Google tokens and channel data read from YouTube: while the channel is connected (the data is read again every day and deleted if it cannot be read for 30 days); deleted at once when you disconnect it or delete your account.
- Destinations, stream keys, overlays and chat bot settings: until you remove them or your account.
- Payments and donations: the amount, time and payment reference are kept for our accounting and tax records, also after an account is deleted. A supporter's name and message are kept while the streamer's account exists.
- Support tickets: kept for our records, also after an account is deleted.
- Sign-in records: while your account exists; they are deleted with it.
- Server logs (which can contain your e-mail address and IP address): as long as needed for security and troubleshooting.
- Backups: kept for a limited time; information deleted from the Service remains in them until then.
Deleting your account. You can delete your account yourself on your account page, confirmed with a code sent to your e-mail address. Your name, e-mail address, mobile number, Google sign-in link, language, time zone, countries, connected channel and its tokens, notifications and sign-in records are then removed, and the account is anonymized. The records we must keep (listed above) stay, without your name.
8. Your rights
Depending on the law that applies to you, you may ask to access, correct, delete, restrict or receive a copy of your personal information, object to its use, and withdraw a consent you gave (for example by disconnecting your YouTube channel). You may also lodge a complaint with a data protection authority. You can correct most of your details yourself on your account page; for anything else, contact us (section 11). We answer within 30 days.
9. Children
The Service is not intended for children under 13, and we do not knowingly collect their information. If you believe a child under 13 has given us personal information, contact us and we will delete it.
10. Changes to this Policy
We may update this Policy. The new version is published on this page with a new date; if the changes are significant, we will also tell you in the Service or by e-mail.
11. Contact
For questions or requests about your personal information, open a ticket in the Support section of the Service.