Last updated: October 25, 2026
This policy explains what personal data the MiniStream mobile application collects, why we collect it, who we share it with, and the choices you have. MiniStream is published by MozgoTech ("we", "our", "us"). It applies to the MiniStream app on Android and iOS, the MiniStream web client, and the backend services that support them.
It does not cover the third-party platforms you connect to MiniStream — YouTube, Twitch, Facebook, Instagram, TikTok, Vimeo and others. Those services handle your data under their own privacy policies, which are linked in Sections 5 to 7.
MiniStream is a multistreaming studio. You connect the channels you already own, and MiniStream broadcasts one live stream to all of them at once, merges the chat from each platform into a single feed, cross-posts recorded clips, and shows you how each broadcast performed. Everything MiniStream does is done on your own channels, with your explicit authorization.
When you create an account we collect your email address and an authentication identifier. You can sign up with an email and password, or with Google Sign-In or Sign in with Apple, in which case we receive the email address and account identifier those providers give us. You may optionally add a display name and profile photo. Authentication is handled by Google Firebase Authentication; we never see or store your password.
When you connect a streaming or posting destination, we store an OAuth access token and refresh token for that platform, together with the identifiers and display names of the accounts, channels or Pages you authorized (for example your YouTube channel ID and title, or your Facebook Page name). These tokens let MiniStream act on your behalf — start your broadcast, read your chat, publish your post — without you signing in again each time.
Tokens are stored encrypted at rest in our backend and are never shared with other users or with any third party other than the platform that issued them. If you add a destination manually rather than by signing in, we store the RTMP server URL and stream key you enter.
We store the content you make in the app so the app can work: stream titles and descriptions, scheduled broadcasts, branding assets you upload (logos, watermarks, overlays), clips and images you import or edit for cross-posting, the text of posts you compose, and the recordings and edits you make with Record and Record rooms. Branding and profile images are held in Google Cloud Storage. Videos you keep in cloud storage — your clip library, clips uploaded for scheduled streams, Record room recordings and the videos made from them — are held in object storage at Hetzner Online in Germany, under your account.
To show you your analytics and history, MiniStream reads statistics about your own broadcasts and posts from the platforms you connected — view counts, likes, comments, shares, concurrent and peak viewers, and follower or subscriber counts. We store these figures against your stream history so you can see how a broadcast performed over time. See Section 5 for the specific rules that apply to YouTube data and Section 6 for TikTok.
MiniStream has an optional Live Map that shows where public broadcasts are happening. It is opt-in: your location is never sampled or published unless you turn it on.
If you use MiniStream's follow features, we store who you follow so we can notify you when they go live. Following someone does not disclose you to them. Your name appears in another user's follower list only if you separately choose to make your profile visible. Follower counts are stored in a form that cannot be reversed into a list of who follows you.
Paid plans and storage packs are billed by Google Play Billing or the Apple App Store. Those stores process your payment; we never receive or store your card number or billing address. We store the store's identifier for each subscription, your plan tier, any storage packs and their status, so the app can unlock the right features and storage.
When you agree to our Terms of Service — when you sign up, or when we ask you to agree to an updated version — we keep a record of that agreement. It contains:
We rely on this record only to show that an agreement was made. We do not use it to profile you, to target you, or to build any history of where you have been. You can see the date and version of your own agreement in the app under Settings → About → Terms of Service.
To find and fix problems, the app sends crash reports and error reports to Google Firebase Crashlytics. A report contains the technical details of the failure (a stack trace, the app version, device model and operating system version), the screens you visited just before it, a few facts about the app's state at the time (for example your plan tier and whether a broadcast was live), and your MiniStream account identifier so we can match a problem you report to us with the crash behind it.
To understand which features are used, the app and the web client send a small set of usage events to Google Analytics for Firebase — for example that you opened a screen, signed up, connected a destination, started or ended a broadcast, created a schedule, uploaded a clip, published a cross-post, or opened the plans screen. Events carry categories and counts (such as which platform, or how long a broadcast lasted in broad bands), never your content. Firebase also records standard device information such as device model, operating system version, language and approximate region, and, where you buy a plan on iOS, a record of the purchase (product and price).
_ga) to recognise a returning browser. It sets no advertising cookies, and no analytics cookies while the setting above is off.Google processes this data on our behalf under the Firebase privacy and security terms.
In a Record room, each camera records on its own device, and the recording is uploaded to the room host's MiniStream storage. The host can edit those recordings and publish them, and they count toward the host's storage until the host deletes them.
While a room is open, a low-resolution live preview of each camera, and the microphone of each person in the room, is relayed to the others in the room so they can see and talk to each other. This live preview runs through LiveKit, Inc., our real-time video provider. LiveKit passes it through and does not store it; the full-quality recordings never go through LiveKit. To connect you, LiveKit processes the room's audio and video, the name shown for your camera, and your network address, only while you are in the room.
If you join someone else's room as a guest, you are shown that the room is recorded before you join, and we keep a record of that agreement (when, and which version of the notice), together with the name you join under. What you record there is the host's: it stays in the host's storage, and the host decides whether to keep it, including after you leave the room or delete your own account. If you scan a room's code on a device that isn't signed in, that device joins as one of the host's cameras: what it records goes to the host's storage, and it is not linked to any account of yours.
To line up the cameras and to suggest an edit, our servers analyse recordings automatically — for example, when each person is speaking and how loud each microphone is. This is done by software, only for the features you use, and nobody watches or listens to your recordings.
Captions. If the host asks for captions on a take, the sound of each person's microphone in that take is sent to OpenAI for speech recognition, and the words come back with their timings to make the captions. This happens only when the host asks, only for that take, and the audio copies made for it are deleted as soon as the words come back. The words are kept with the take in the host's storage until the host deletes it.
If you report a live broadcast on the Live Map or a public profile, we store who filed the report, what it is about, and when. There is no message field — a report carries no text you write. Reports are write-only: the person who files one can never read the tally back, and the person reported is never told who reported them. Reporting the same thing twice does not count twice. When three different people report the same broadcast or profile, it is automatically taken off the Live Map or removed from the public directory.
If you block someone, we store that on your own account — the account you blocked and the title of the broadcast you blocked them from, so the list means something to you later. Nobody else can read your block list, and the person you blocked is not told.
When you delete your account, the reports filed against you and the reports you filed about other people are deleted with it. A block that someone else placed belongs to their account and stays there.
MiniStream needs camera, microphone and screen-recording access to do what it does. To be explicit about what we do and do not do with it:
Face lock keeps you centred in the frame, and some of the looks (Glam in particular) adjust the picture around your face. To do that, the app works out where a face is in each frame while the camera is running.
storage.googleapis.com). That is an ordinary file download, checked against a fixed checksum before it is used; nothing about you, your account or your camera is sent with the request.MiniStream uses YouTube API Services. By using the YouTube features of MiniStream you agree to be bound by the YouTube Terms of Service.
Google's handling of data it receives is described in the Google Privacy Policy.
What MiniStream accesses through the YouTube API, and why:
All YouTube access is limited to the channel you authorized. MiniStream does not browse, collect or index other people's YouTube data, and does not combine YouTube data across users.
Storage of YouTube data. Authorization tokens are kept until you disconnect the destination or delete your account. Statistics about your own broadcasts are refreshed from the YouTube API and are not retained beyond the period permitted by the YouTube API Services Terms of Service; figures we can no longer refresh are removed or clearly marked as a historical snapshot rather than a current figure.
Revoking access. You can revoke MiniStream's access to your YouTube and Google data at any time from the Google security settings page: https://myaccount.google.com/permissions. You can also disconnect the destination inside MiniStream, which deletes the stored token on our side.
MiniStream uses the TikTok Login Kit and the TikTok Content Posting API to publish videos you choose to the TikTok account you connected. By using the TikTok features of MiniStream you agree to be bound by the TikTok Terms of Service and the TikTok Community Guidelines. TikTok's own handling of your data is described in the TikTok Privacy Policy.
What MiniStream accesses through the TikTok API, and why:
The choices you make before posting are yours. Every TikTok post composed in MiniStream requires you to pick who can view it, whether comments, Duet and Stitch are allowed, and whether the post discloses commercial content. MiniStream preselects none of these — it sends TikTok exactly what you chose, and nothing more.
All TikTok access is limited to the account you authorized. MiniStream does not browse, collect or index other people's TikTok data, does not combine TikTok data across users, and does not use TikTok data for advertising, profiling or training AI models.
Storage of TikTok data. We store your TikTok authorization tokens, your account identifier and display name, and — where you granted the optional analytics permission — the aggregate figures shown on your Analytics screen. Tokens are kept until you disconnect TikTok or delete your account. We do not store copies of your TikTok videos beyond the media you yourself imported into MiniStream.
Revoking access. You can revoke MiniStream's access at any time from the TikTok app (Profile → Settings and privacy → Security and permissions → Manage app permissions), or by disconnecting TikTok inside MiniStream. Either way we delete the stored tokens, and we delete the TikTok data we hold for you when you disconnect the account or delete your MiniStream account.
The same principles apply to every other platform you connect: MiniStream acts only on the accounts you authorized, only to do what you asked, and stores only what it needs to do so. Their privacy policies:
You can revoke MiniStream's access from each platform's own connected-apps or security settings, independently of anything you do in our app.
MiniStream can suggest captions, hashtags, stream recaps and clip highlights. When you use one of these features, the text you are working on — a stream title, a post draft, or a short summary of a broadcast — is sent through our backend to OpenAI to generate the suggestion, and the result is returned to you.
See the OpenAI Privacy Policy.
We do not sell your personal data. We do not share it with advertisers. We do not use your broadcasts, posts or analytics for advertising or profiling.
We share data only with service providers who help us run MiniStream, and only as far as they need it:
We may also disclose data if legally required to do so, or to protect the rights and safety of our users or the public.
You can, at any time:
Depending on where you live, you may also have the right to access, correct, export or restrict the processing of your personal data, to object to processing, and to lodge a complaint with your data protection authority. To exercise any of these, email [email protected] from your account's email address. We respond within 30 days.
MiniStream is an adult service. You must be 18 years or older to use it, and you must meet the minimum age of every platform you connect. MiniStream is not directed to children and we do not knowingly collect personal data from anyone under 18. If you believe someone under 18 has given us data, contact us and we will delete it and close the account.
Data is encrypted in transit and at rest. Platform tokens and stream keys are held in restricted backend storage and are never exposed to other users. Access to our systems is limited to the people who need it. No system is perfectly secure, but we take these obligations seriously and will notify you promptly if a breach affects your data.
Our backend runs on Google Cloud infrastructure and our streaming relay is hosted in Europe. Your data may be processed in countries other than your own, including the United States. Where required, transfers are made under appropriate safeguards such as the European Commission's Standard Contractual Clauses.
We may update this policy as MiniStream changes. The "Last updated" date at the top always reflects the current version, and we will notify you in the app of any material change before it takes effect.