Privacy Policy
Last updated: October 18, 2026
Effective: October 4, 2026
The short version
CueIRL runs cloud streaming servers. We are not an advertising business. We collect what we need to run your server, keep it secure and answer you when you write to us.
- We do not sell your personal information, and we do not share it for cross-context behavioral advertising.
- Your live video and audio pass through your server on the way to the platforms you choose. We do not record them or keep them.
- Chat from Twitch and Kick is held in memory while your session runs and is gone when the session ends.
- The phone app asks for your camera and microphone, and on Android for permission to show a streaming notice. It does not ask for your location, photos, contacts or local network.
- Google Analytics runs on cueirl.com only if you say yes, and never if your browser sends Global Privacy Control.
- You can ask to see, correct or delete your data by emailing [email protected].
The rest of this page is the detail.
Who we are and what this policy covers
This Privacy Policy explains how CueIRL Corporation, a Delaware corporation ("CueIRL", "we", "us" or "our"), handles personal data. Personal data means information that identifies you or can reasonably be linked to you.
It applies when you use cueirl.com and its subdomains, including the browser studio at studio.cueirl.com, the links page at start.cueirl.com and our API at api.cueirl.com, the CueIRL iOS and Android apps, and the cloud servers we run for you (together, the "Services"). It also applies when you join our waitlist or contact us.
CueIRL Corporation is the controller of the personal data described in this policy, with one exception: for your viewers' chat messages and for people who appear in your stream, we act on your behalf (see Your viewers and people in your stream). You can reach us at [email protected] or at 1151 Walker Rd, Ste 100, PMB 895, Dover, DE 19904, United States.
This policy does not cover services that other companies run, even when you reach them through CueIRL. Twitch, Kick, YouTube, TikTok, any custom RTMP or SRT destination you add, and any app or encoder you connect to your server have their own privacy policies, and those policies govern what they do with your data.
If you buy a Custom plan under a separate written agreement, that agreement may add to how we handle data for that work. Where the two differ, the written agreement controls for that work.
Personal data we collect
What we collect depends on how you use CueIRL. Some of it you give us, some is created as you use the Services, and some comes from other sources.
Your account
- Username and password. You need these to create an account. We store your password only as a salted scrypt hash, never the password itself. An invite code is optional.
- Email address. We have your email address only if your account was created from the waitlist or from an invite. An account made through public sign-up has no email address on file.
- Account details. When the account was created, when you last signed in, how it was created (public sign-up, waitlist or invite), your role, and who invited you, if anyone.
- Login tokens. When you sign in, we issue a login token. Your device keeps the token, and our servers keep only a SHA-256 hash of it. Tokens expire after 30 days.
- Moderation records. If we suspend or ban an account, we record the reason, when the ban ends and which of our admins issued it.
Your streams and sessions
- Live video and audio. Your video and audio travel from your phone or encoder to your server, where they are mixed and re-encoded, and then go to the destinations you set up. We do not record or store them.
- Session setup. For each session we store your scene setup and snapshots of your OBS scenes, the overlay images and media you upload, your destination names and stream keys, and the chat channel names you enter.
- Chat. If you turn on unified chat, your server reads the public chat of the Twitch and Kick channels you name. It holds the last 300 messages of the session in memory so the studio, the app and your overlay can show them. We do not use your Twitch or Kick login to do this.
- Stream health. Your server keeps the incoming bitrate in memory to show you live stats. The phone app reads network round trip, packet loss, codec, battery level and connection type on your phone so it can show them to you. The app does not send those readings to us.
Logs and technical data
- Server logs. Our servers write operational events to a system log. These logs include the IP addresses of encoders that connect to your server, stream keys, and email addresses involved in admin actions and in emails we send.
- IP addresses for rate limiting. When you control your server from the studio or the app, we use your IP address in memory to limit how many requests can be made. This protects the Services from abuse. We do not save it for this purpose.
- Admin audit log. When our admins take an action, such as deciding a waitlist entry or moderating an account, it is recorded in an audit log, which can include your email address.
- Traffic through Cloudflare. All traffic to our websites, the studio and our API passes through Cloudflare, which sees your IP address and the details of each request, such as the address requested, your browser and the time.
Waitlist and support
- Waitlist. Your email address and, if you give them, your Twitch, Kick, YouTube and TikTok channel names. We also record when we checked your entry, its status and which admin decided it.
- Follower counts. When you give us channel names, we automatically look up the public follower counts on those Twitch, Kick, YouTube and TikTok channel pages. We use them to help decide the order in which we send invites.
- Support form. Your email address, your name if you give it, the topic, your message, the time you sent it and the status of your request.
- Emails you send us. Whatever you choose to include.
Website analytics, only if you say yes
On cueirl.com, including the links page at start.cueirl.com, we use Google Analytics 4. It runs only after you accept the cookie notice or turn analytics on at cueirl.com/privacy-choices, and it never runs when your browser sends Global Privacy Control. When it runs, Google Analytics collects the pages you view, the site that sent you, your device and browser type, your approximate location (which Google works out from your IP address), how you move around the site, and whether you sent the waitlist form, without the details you typed into it. Google Analytics does not run in the browser studio or in the phone apps. See Cookies and similar technologies.
Google Fonts in the browser studio
The browser studio loads its fonts from Google Fonts. When it does, your browser connects to Google, and Google receives your IP address and basic browser information. The main cueirl.com website does not load Google Fonts.
Payments, when billing launches
When you subscribe to a paid plan, payments are processed by Stripe, and Stripe handles your card details under its own privacy policy. We will not store full card numbers. Before we start charging for plans, we will update this policy to list exactly which billing details we keep.
What we do not collect
- Recordings of your streams. We do not record or store your video or audio.
- Your platform logins. We never ask for your Twitch, Kick, YouTube, TikTok or Google password, and we do not hold access tokens for those accounts. Chat is read from public channels by name.
- Your location. The app does not ask for your location, and we do not track where you are. The only location estimate involved is the approximate one Google Analytics works out from your IP address, and only if you allow analytics.
- Your contacts, photos, files, calendar or messages. The app does not ask for access to any of them.
- Advertising identifiers. We do not use Apple's advertising identifier or Google's advertising ID, and the apps contain no advertising code.
- Device metrics and crash reports. The app does not send us the network, battery or connection readings it shows you, and we do not use an outside crash reporting or error monitoring service.
- Push notification tokens. We do not send push notifications, so we do not collect push tokens. The Android notice you see while streaming is created by the app on your phone.
- Biometric data. We do not use face or voice recognition.
- Your content for AI training. We do not use your video, audio or chat to train machine learning models.
Permissions the phone app asks for
The app uses these permissions only to capture and stream. You can change the ones your phone lets you control at any time in your phone's settings.
| Phone | Permission | Why the app uses it |
|---|---|---|
| iOS | Camera | To capture video for your stream in camera mode |
| iOS | Microphone | To capture audio for your stream |
| iOS | Background audio | To keep the camera streaming while the app is in the background |
| Android | Camera | To capture video for your stream in camera mode |
| Android | Microphone (record audio) | To capture audio for your stream |
| Android | Foreground service for camera and microphone | To keep streaming while the app is in the background |
| Android | Notifications | To show the "streaming" notice on your phone while you are live. The app creates it on the phone. It is not a push notification. |
| Android | Wake lock | To stop the phone from going to sleep in the middle of a stream |
If you say no to the camera, camera mode cannot capture video. If you say no to the microphone, your phone sends no sound. If you say no to notifications on Android, you will not see the streaming notice. Background audio on iOS and the foreground service and wake lock on Android are not prompts; your phone grants them when you install the app.
The app does not ask for your photos or storage, your location, your local network or your contacts.
How we use personal data
- To run the Services. Create and manage your account, sign you in, start and run your server, take in your video and audio, mix them with your scenes and overlays, publish to your destinations, and show you chat and stream stats.
- To run the waitlist and send invites. Keep your place on the waitlist, look up public follower counts for the channels you give us, decide the order of invites and send your invite.
- To communicate with you. Send invites, temporary passwords and service notices, and answer support requests. We send this email through Resend.
- To keep CueIRL safe and secure. Limit request rates, prevent and investigate abuse, fraud and attacks, enforce our Terms of Service, moderate accounts, and keep a record of what our admins do.
- To troubleshoot. Use server logs to find and fix problems with streams and servers.
- To understand our website. If you allow it, use Google Analytics reports to see which pages of cueirl.com get read and where visitors come from.
- To run our business. Plan capacity and keep business records using counts that do not identify you, such as how many servers are running. When billing launches, take payments and keep accounting and tax records.
- To meet legal obligations and protect rights. Respond to lawful requests, comply with the law, and establish, exercise or defend legal claims.
We try to use the least personal data we need for each purpose. We do not use personal data for advertising, and we do not make decisions about you that have legal or similarly significant effects based only on automated processing.
Today we only send email about the Services, such as invites, temporary passwords and notices. If we start sending news or marketing email, every message will include our postal address and a working unsubscribe link, we will act on unsubscribes within 10 business days, and in the EEA and the UK we will send it only where the law allows, such as with your consent.
Legal bases for processing in the EEA and UK
If you are in the European Economic Area or the United Kingdom, the GDPR and the UK GDPR require us to have a legal basis for each use of your personal data. These are the bases we rely on.
| What we do | Legal basis |
|---|---|
| Create your account, run your server and sessions, publish your stream, show chat and stats | Performance of our contract with you |
| Keep your waitlist entry and send your invite | Steps you asked us to take before entering into a contract |
| Look up public follower counts to decide the order of invites | Our legitimate interest in deciding fairly who to invite first while space is limited |
| Send invites, temporary passwords and service notices | Performance of our contract with you, or steps you asked us to take before entering into one |
| Answer support requests | Performance of our contract with you, or our legitimate interest in helping people who contact us |
| Rate limiting, abuse prevention, moderation, the admin audit log, server logs and Cloudflare security | Our legitimate interest in keeping the Services secure and working, and legal obligation where a law requires it |
| Load fonts for the browser studio from Google Fonts | Our legitimate interest in showing the studio correctly |
| Google Analytics on cueirl.com | Your consent, which you can withdraw at any time at cueirl.com/privacy-choices |
| Payments, accounting and tax records, when billing launches | Performance of our contract with you, and legal obligation for tax records |
| Respond to lawful requests and establish, exercise or defend legal claims | Legal obligation, and our legitimate interest in protecting our rights and those of our users |
| Plan capacity and run the business using counts that do not identify you | Our legitimate interest in running CueIRL |
Where we rely on legitimate interests, we have weighed them against your rights and freedoms, and you can object (see Your rights). Where we rely on consent, you can withdraw it at any time, and withdrawing does not affect what we did before. A username and password are needed to create an account; without them we cannot provide the Services.
How we share personal data
We do not sell personal information, and we do not share it for cross-context behavioral advertising. Some US state laws use broad definitions, which we explain under US state privacy information. We share personal data only in these ways:
- Service providers. Companies that host, protect or deliver parts of CueIRL for us, listed in the next section. They may use the data only to provide their services to us, under terms that require them to protect it.
- The platforms you stream to. Your stream, and the stream key that identifies your account there, go to Twitch, Kick, YouTube or any custom destination you set up. What happens next is governed by that platform's privacy policy.
- The platforms we read public information from. To show chat and to look up follower counts, our servers request public chat and public channel pages from Twitch, Kick, YouTube and TikTok by channel name. Kick chat arrives through Pusher, the real-time messaging service Kick uses. Those platforms see that our servers asked for that channel.
- Law enforcement and other authorities. As described in Legal requests and law enforcement.
- To prevent harm. We may disclose personal data when we believe in good faith that it is needed to prevent fraud, abuse or attacks on the Services, or to protect the safety of CueIRL, our users or anyone else.
- In a business transfer. If CueIRL is involved in a merger, acquisition, financing, reorganization or sale of assets, personal data may be transferred as part of that deal, within the limits of the law and this policy. We will tell you before your personal data becomes subject to a different privacy policy.
- With your consent. In other cases where you ask us to share something or agree to it.
Service providers and other parties
These are the companies that handle personal data for us, and the platforms CueIRL works with.
| Provider | What they do for CueIRL | Personal data involved | Where |
|---|---|---|---|
| Cloudflare, Inc. | Delivers and protects our websites, studio and API, and connects our servers to the internet | IP addresses and request details of everyone who uses our websites, studio, apps or API | United States, and Cloudflare's global network |
| OVHcloud (OVH US LLC) | Hosts our platform servers | Account, session, waitlist, support and log data stored on those servers | Virginia, United States |
| CueIRL's own servers, including in a colocation facility | Run parts of the platform now, and the GPU streaming servers later | Any of the data described in this policy | United States |
| Akamai Cloud (Linode) and other cloud GPU providers | Run the GPU streaming servers at launch | Your live video and audio while it is processed, and your session setup, including stream keys | United States |
| Tailscale Inc. | Private, encrypted network between our servers | Network details about our servers. The traffic itself is encrypted end to end, and Tailscale cannot read it. | Tailscale's network |
| Resend | Sends our email | Your email address and the content of the email | United States |
| Google LLC (Google Analytics) | Website analytics on cueirl.com, only with your consent | Pages viewed, the referring site, device and browser details, approximate location worked out from your IP address, and cookie identifiers | United States |
| Google LLC (Google Fonts) | Serves the fonts used by the browser studio | IP address and browser details | United States, and Google's global network |
| Stripe, Inc., when billing launches | Processes payments for paid plans | The payment details you enter at checkout, and the plan you buy | United States |
| Twitch, Kick, YouTube and TikTok | Independent platforms, not our service providers. Your stream goes to the ones you choose as destinations, we read public chat from Twitch and Kick, and we read public follower counts from all four. | Your stream and stream key for each destination, and the channel names you give us | Wherever each platform operates |
Twitch, Kick, YouTube and TikTok decide for themselves how they use the data they receive, under their own privacy policies.
We will update this list when we add or change a provider that handles personal data.
Legal requests and law enforcement
We disclose personal data to law enforcement, regulators, courts or other public authorities only in response to legal process we believe is valid, such as a subpoena, court order or search warrant, or when we believe in good faith that disclosure is needed to prevent death or serious physical injury, or to protect our rights and safety or those of our users.
- We review each request to check that it is legally valid, and we push back on requests that are overbroad or unclear.
- We disclose only the data the request legally requires.
- We tell the affected user before we disclose, unless the law or a court order forbids it, or in an emergency where notice could put someone at risk.
- If we learn of apparent child sexual exploitation, we report it to the National Center for Missing and Exploited Children, as US law requires.
Because we do not record streams and do not keep chat after a session ends, we cannot produce them in response to a request.
Legal requests go to [email protected] or to our postal address in Contact us.
International data transfers
CueIRL is based in the United States, and we store and process personal data in the United States. If you use CueIRL from outside the United States, you send your data to us here directly.
When we pass personal data on to our service providers in the United States, we rely on the European Commission's Standard Contractual Clauses in their data processing terms, with the UK addendum for data from the UK, or on the EU-US Data Privacy Framework and its UK Extension where the provider is certified. CueIRL itself is not certified under the Data Privacy Framework. Some providers, such as Cloudflare and Google, run global networks, so a request may be handled at a location close to you. To get a copy of the safeguards we rely on for a particular provider, email [email protected].
Cookies and similar technologies
Cookies are small text files that a website stores in your browser so it can recognize the browser later. Local storage is a similar store in your browser that a website can write to and read back. Phone apps keep data on your device in a similar way. We use a small number of these, and none of them are for advertising.
| Name | Where | Set by | What it does | How long |
|---|---|---|---|---|
| Login token | Browser studio (local storage) and phone app (app storage) | CueIRL | Keeps you signed in | Until you sign out. It stops working 30 days after you sign in. |
| Studio preferences | Browser studio (local storage) | CueIRL | Remembers your panel layout and display preferences, and when your current stream started so the studio can show uptime | Until you clear your browser's storage |
| cue_hint | cueirl.com and its subdomains (cookie) | CueIRL, when you sign in to the browser studio | Holds your username so cueirl.com can show that you are signed in and link you back to the studio. It cannot sign anyone in | 30 days, or until you sign out |
| cueirl-analytics | cueirl.com (local storage) | CueIRL | Remembers whether you accepted or declined analytics | Until you change it or clear your browser's storage |
| _ga | cueirl.com (cookie) | Google Analytics, only if you accept | Tells one visitor apart from another so Google Analytics can count visits | 2 years from your last visit |
| _ga_ followed by our container ID | cueirl.com (cookie) | Google Analytics, only if you accept | Keeps track of your current visit | 2 years from your last visit |
| Cloudflare security cookies, such as __cf_bm | Our websites and studio (cookie) | Cloudflare | May be set to tell people from bots and to block attacks | Usually 30 minutes |
The login token, studio preferences, the cue_hint cookie, your analytics choice and Cloudflare's security cookies are needed for the Services to work or to remember a choice you made, so we do not ask before using them. The Google Analytics cookies are optional and are set only if you accept them.
Your choices
- The cookie notice. When you first visit cueirl.com, we ask before we load Google Analytics. Analytics stays off until you accept.
- Privacy choices. You can turn analytics on or off at any time at cueirl.com/privacy-choices. Turning it off stops Google Analytics from running in that browser. To remove cookies it already set, clear the cookies for cueirl.com in your browser.
- Global Privacy Control. If your browser sends a Global Privacy Control signal, Google Analytics never loads, even if you accepted it before.
- Your browser. Most browsers let you block or delete cookies and local storage, and some extensions block trackers. If you block local storage in the browser studio, you will not be able to stay signed in.
These choices apply to the browser you make them in. If you use another browser or device, make your choices there too.
Third parties and tracking over time
If you allow Google Analytics, Google may collect information about your visits to cueirl.com over time. We have turned off Google signals and ad personalization, so we do not use Google Analytics to link your visits to a Google account or to target ads. We do not run ad networks, social media pixels or other advertising trackers on our websites, studio or apps. Google handles the data it receives under its terms with us and its own privacy policy.
Do Not Track and Global Privacy Control
Some browsers can send a "Do Not Track" signal. There is no agreed standard for what websites should do when they receive it, so CueIRL does not change how it behaves in response to Do Not Track.
We do honor Global Privacy Control. If your browser sends a Global Privacy Control signal, Google Analytics does not load on cueirl.com, and we treat the signal as a request to opt out of any sale or sharing of your personal information from that browser.
How long we keep personal data
| Data | How long we keep it |
|---|---|
| Live video and audio | Not stored. It is processed as it passes through your server. |
| Chat messages | In memory only, up to the last 300 messages of a session, and dropped when the session ends |
| Incoming bitrate, and IP addresses used for rate limiting | In memory only, while they are needed |
| Session setup, OBS scene snapshots, uploaded overlays and media, destination names, stream keys and chat channel names | Until you end the session, when they are removed. Stream keys that appear in server logs are kept for the server log period below. |
| Login tokens | They expire 30 days after you sign in. Signing out removes the token from your device. |
| Account and moderation records, waitlist entries, support requests and emails, and the admin audit log | Until your account is deleted, or for as long as we need them for the purposes in this policy, and then deleted |
| Server logs | Logs rotate automatically, and older entries are deleted as new ones are written |
| Google Analytics data | Cookies last up to 2 years from your last visit. Google Analytics keeps the data it collects for no more than 14 months. |
| Payment, accounting and tax records, when billing launches | As long as tax and accounting law requires |
We may keep personal data longer when the law requires it, or when we need it to resolve disputes, enforce our agreements or establish, exercise or defend legal claims. When we no longer need personal data, we delete it.
Security
We use administrative and technical measures to protect personal data, including these:
- Passwords are stored only as salted scrypt hashes.
- Login tokens are stored on our servers only as hashes, and they expire after 30 days.
- Connections to our websites, the studio and our API are encrypted with HTTPS (TLS) through Cloudflare.
- Our servers connect to each other over a private, encrypted network.
- Requests from control sessions are rate limited to slow down abuse.
- Access to our production systems and personal data is limited to staff who need it, and admin actions are recorded in an audit log.
Stream keys. We store the stream keys you give us on our servers so your server can publish to your destinations, and stream keys can appear in our server logs. Treat your stream keys like passwords. Do not show them on stream or in screenshots, and if you think one has been exposed, reset it on the platform it belongs to and enter the new key in CueIRL.
Some streaming protocols, such as plain RTMP, do not encrypt what they carry, including the stream key. Where your encoder and destination offer an encrypted option, use it.
No system is perfectly secure, and we cannot guarantee the security of your data. If a breach affects your personal data, we will tell you and the relevant authorities as the law requires, and explain what happened and what you can do.
You can help too: use a strong password that you do not use anywhere else, do not share your account, and sign out of the studio on shared computers.
Your rights
Wherever you live, you can ask us to:
- Access the personal data we hold about you and get a copy of it.
- Move the data you gave us, in a structured, commonly used, machine-readable format, where that is technically feasible.
- Correct personal data that is wrong or incomplete.
- Delete your account and your personal data.
- Restrict how we use your personal data while a concern is looked into, or in other cases the law allows.
- Object to our use of your personal data based on our legitimate interests, and to any direct marketing at any time.
- Withdraw consent where we rely on it, such as for Google Analytics. This does not affect what we did before you withdrew it.
- Opt out of analytics on cueirl.com at cueirl.com/privacy-choices, or by turning on Global Privacy Control in your browser.
- Appeal if we turn down your request.
- Complain to a data protection authority.
How to make a request
Email [email protected]. If your account has an email address, send the request from that address. If it does not, tell us your username, and we will ask for information that lets us confirm the account is yours. We use what you give us to verify your identity for that purpose only. You can ask someone else to make a request for you if you give them signed, written permission; we may still ask you to confirm your identity with us directly.
We respond within 30 days. If a request is complex and the law gives us more time, we will tell you within those 30 days why we need longer and when to expect an answer. Requests are free. If a request is clearly unfounded or excessive, we may charge a reasonable fee or decline it, where the law allows.
Some data we have to keep even after you ask us to delete it, such as records we need to comply with the law, to finish dealing with a security or abuse investigation, or to establish, exercise or defend legal claims. We will tell you if that applies. We will not hold it against you when you use any of these rights.
Deleting your account
You cannot yet delete your account yourself in the app or the studio. To delete it, email [email protected] from the email address on your account, or with your username if the account has no email address. We will delete your account and the personal data tied to it within 30 days, except data we have to keep as described above. Copies in our server logs are deleted when those logs are, as described in How long we keep personal data. This works whether or not you have the app installed. You can ask us to delete a waitlist entry or a support request the same way.
Appeals
If we turn down your request, in whole or in part, we will explain why. You can appeal by emailing [email protected] with "Appeal" in the subject line. We will reply in writing within 45 days and explain what we decided and why. If we deny your appeal, you can contact the attorney general of your state.
Complaints to a data protection authority
If you are in the European Economic Area or the United Kingdom, you have the right to complain to a data protection authority, in particular in the country where you live, work or where you think the problem happened. Authorities in the EEA are listed on the European Data Protection Board website at edpb.europa.eu, and in the UK the authority is the Information Commissioner's Office at ico.org.uk. We would appreciate the chance to deal with your concern first, so please consider contacting us at [email protected].
US state privacy information
Some US state privacy laws, such as the California Consumer Privacy Act, apply only to businesses above certain size thresholds, and CueIRL does not currently meet them. We still give everyone the rights in Your rights, and we provide the information below so you know where you stand. In this section, "personal information" means the same as personal data.
Categories of personal information
| Category | Examples | Where it comes from | Who receives it |
|---|---|---|---|
| Identifiers | Username, email address, IP address, login tokens | You and your device | Cloudflare, our hosting and GPU providers, Resend for email, and Google for fonts and analytics |
| Internet or network activity | Server logs, request details, and website analytics if you allow it | Your device, automatically | Cloudflare, our hosting providers, and Google Analytics if you allow it |
| Audio and visual information | Your live video and audio while it passes through your server, and the overlay images and media you upload | You | Our hosting and GPU providers, and the destinations you choose |
| Account login credentials | Your username with your password, stored as a hash | You | Our hosting providers, as storage only |
| Information from public sources | Public follower counts for the channels you give us | Public channel pages on Twitch, Kick, YouTube and TikTok | Our hosting providers |
| Commercial information | Your plan and payment records, when billing launches | You | Stripe, when billing launches |
We collect and use these categories for the purposes in How we use personal data. We do not draw inferences about you to build a profile, and we use your login credentials only to let you sign in.
Sale and sharing
We do not sell personal information, and we do not share it for cross-context behavioral advertising. Some state laws define "sale" and "sharing" broadly enough that letting an analytics provider such as Google set cookies on a website could count. Google Analytics only runs on cueirl.com if you accept it, and you can switch it off at any time at cueirl.com/privacy-choices or by using Global Privacy Control, which we treat as an opt-out. We do not knowingly sell or share the personal information of anyone under 16.
We do not use personal information for profiling that leads to decisions with legal or similarly significant effects.
California
Under California Civil Code section 1798.83, California customers can ask whether we disclose personal information to third parties for their own direct marketing purposes. We do not. You can still ask by emailing [email protected].
If you are a California resident under 18 and a registered user, you can ask us to remove content you posted publicly on our Services. CueIRL does not publish your content on its own websites; your stream appears on the platforms you choose, where you can remove it. For anything else, email [email protected] with a description of what you want removed. Removal may not be complete, and the law may not require or allow removal in every case.
Nevada
We do not sell covered information, as defined in Chapter 603A of the Nevada Revised Statutes.
Children and teens
You must be at least 13 years old to use CueIRL. If you are under 18, you may use CueIRL only with the agreement of a parent or guardian.
CueIRL is not directed to children under 13, and we do not knowingly collect personal data from them. If we learn that a child under 13 has an account, we will delete the account and its personal data. If you believe a child under 13 has given us personal data, email [email protected].
If minors appear in your stream, you are responsible for getting any consent the law requires where you are filming.
Your viewers and people in your stream
If you turn on unified chat, public messages and usernames from the Twitch and Kick channels you name pass through your server so the studio, the app and your overlay can show them. Your server keeps the last 300 messages of a session in memory and drops them when the session ends.
You decide which chat to show and who appears or is heard in your stream. For that data, where data protection laws use these terms, you are the controller and we are your processor, handling it only to provide the Services to you. If you need a data processing agreement with us, email [email protected].
Viewers who want a chat message removed should ask the streamer or the platform where they posted it. We do not keep chat after a session ends.
Changes to this policy
We will update this policy when our practices change, and the "Last updated" date at the top always shows the current version. For a material change, we will post a notice on cueirl.com, and email you if we have your email address, at least 30 days before the change takes effect.
Before we launch a feature that collects new kinds of personal data, such as billing, cloud recording or push alerts, we will update this policy to describe it.
Previous versions are available on request at [email protected].
Contact us
Privacy questions, requests and complaints: [email protected]
Help with your account or streams: [email protected]
CueIRL Corporation
1151 Walker Rd, Ste 100, PMB 895
Dover, DE 19904
United States
