Privacy Policy
Effective date: 28 October 2026 · Last updated: 29 October 2026
LIVEXIO MEDIA TECH LTD operates Livexio and is the controller of personal data processed to provide and operate Livexio, as described in this policy. It is a private company limited by shares, registered in England and Wales under company number 17547937.
Registered office: Fryatt Lodge, 64 Brooklands Road, Romford, RM7 7EB, United Kingdom.
For privacy questions, rights requests, data deletion or complaints, contact contact@livexio.com.
This policy covers signing in, connecting destinations, studios, broadcasts, recordings, and live chat.
1. Information and use
We handle account names, email addresses, profile images, channel identifiers, permissions, encrypted connection credentials, broadcast settings, audio/video, requested recordings, and available chat and viewer information. Essential cookies, browser storage, and technical logs support sign-in, connections, security, and troubleshooting.
We use this information to provide the features you request, publish to destinations you select, and operate and secure Livexio. Where UK/EU law applies, our bases include providing your requested service, legitimate interests in security and operation, and legal obligations.
2. YouTube and Google
Google sign-in: when you choose Continue with Google, we use the Google account identifier, name, email address and profile image that Google makes available to create or identify your Livexio account, authenticate you and show your account identity. Google sign-in does not by itself connect a YouTube channel. YouTube channel permissions are requested separately when you choose to connect a channel.
Your permission choices: Google displays the requested permissions before you authorize them. You can cancel that request, use Livexio's email sign-in instead of Google sign-in, or withdraw Google authorization through your Google account permissions. Without YouTube authorization, Livexio cannot perform the corresponding YouTube channel, broadcast or chat actions.
Livexio uses YouTube API Services. When you connect a channel through Google, Google handles your sign-in and permission choices. We do not receive or store your Google password.
- Account and channel information: Google sign-in may provide an account identifier, name, email address and profile image for your Livexio account. The YouTube connection provides the authorized channel identifier, channel name and thumbnail, permission scopes and connection status.
- Authorization credentials: we store encrypted OAuth access and refresh tokens and their expiry information to perform the authorized connection and broadcast actions. Tokens are used by the server, not exposed in the studio interface.
- Broadcast and stream information: we process your chosen title, description, tags, category, schedule and privacy setting, together with YouTube broadcast/stream identifiers, watch URLs, ingestion addresses/stream keys, broadcast status, health and available concurrent viewer information.
- Live chat: we retrieve available message identifiers, content, message/event type, author display names, available handles, author identifiers and profile images, publication times, platform-provided reaction counts, author role flags, and available membership, Super Chat, sticker and gift details or gift artwork for the selected broadcast, including text supplied for supported membership or paid-message events. We retain chat events temporarily to show them in the studio and support available actions.
- Your source media: camera, microphone, guests, screen shares, uploads and requested recordings are processed as your Livexio programme. We do not download your videos from YouTube to create Livexio recordings.
We use channel information to identify your selected destination, credentials to maintain your authorized connection, broadcast data to prepare, publish, monitor and end your broadcasts, and chat data to provide the studio chat and host-selected comment overlays. API data is not sold or used to target advertising, build user profiles or train general-purpose AI models.
Use of these services is subject to the YouTube Terms of Service. Google handles information under the Google Privacy Policy.
Google user data and Limited Use
Livexio's use and transfer of Google user data must comply with the Google API Services User Data Policy, including its Limited Use requirements. We limit Google user data to providing or improving the user-facing sign-in, channel connection, broadcast and chat features described in this policy.
We do not sell Google user data, transfer it to data brokers or information resellers, use it for advertising or retargeting, determine creditworthiness or lending eligibility, or use it to train, develop or improve generalized or non-personalized artificial-intelligence or machine-learning models. Our service providers are not permitted to use that data for these purposes either.
Transfers of Google user data are limited to delivering or improving the visible features you authorize, necessary security purposes, compliance with applicable law, or a merger, acquisition or asset transfer after obtaining your explicit prior consent. These restrictions also apply to information derived from Google user data.
Human reading of Google user data is permitted only with your affirmative agreement to view the specific information, where necessary for security or compliance with applicable law, or for internal operations using aggregated data as permitted by Google's policy and applicable law. General operational or support access does not create an unrestricted right to read identifiable Google user data.
You can revoke Livexio's access through your Google account permissions. Our deletion controls and contact process are described below.
3. Facebook, Instagram, Twitch, and X
When you send a host chat message, it is published only to the destinations you select, using your connected accounts. A reply targets its original destination. Uploaded chat images, GIFs and PDFs are shared as links; anyone with a link can open it for 24 hours. The file is removed at the next scheduled maintenance run after expiry. Stream thumbnails are host-provided files sent to eligible destinations; unused uploads are removed after one day.
For connected platforms, we access only information and features permitted by your authorization and made available by the platform. This may include account or Page details, broadcast management, live comments, and viewer information. Features depend on platform support and account eligibility.
- Facebook and Instagram: account/Page connections and supported publishing or engagement features; Meta Privacy Policy.
- Twitch: channel connections and supported streaming and chat features; Twitch Privacy Notice.
- X: account connections and supported broadcast and engagement features; X Privacy Policy.
You can revoke access using each platform's connected-app settings.
5. Storage and retention
How we protect Google user data
Our public website and requests to Google API endpoints use HTTPS to protect data in transit. OAuth access and refresh tokens are encrypted before storage and are used on the server; they are not displayed in the studio interface. Authenticated server routes and account-level access checks restrict access to connected-channel records and requested actions. Google handles your Google password, which Livexio does not receive or store.
Basic Google sign-in profile information is retained as part of your Livexio account while it is needed to provide that account. You can request account-data deletion at the contact address below. Google sign-in profile data, YouTube connection/API records and original programme media have distinct purposes and retention lifecycles; disconnecting a YouTube channel does not by itself delete your Livexio account.
Connection credentials are encrypted with restricted server access. A scheduled YouTube maintenance process runs every 15 minutes. It normally rechecks authorization and refreshes connected-channel details daily. Invalid or revoked authorization disables the affected connection and removes the associated stored API data.
YouTube chat history is removed after 24 hours, with cleanup at the next maintenance run. Selected YouTube comment overlays expire within 24 hours. Other stored YouTube broadcast API fields and settings are refreshed or removed on a 27–28 day schedule, before the applicable 30-day limit. Old completed shutdown-job copies are removed after one day. This does not erase the original show title or other information you supplied directly to Livexio.
OAuth tokens remain only while needed for the authorized connection. Remove channel deletes that selected connection's local credentials and associated API records without revoking the Google authorization grant. Revoke all YouTube access removes all your YouTube connection data from Livexio and submits token revocation to Google immediately. If Google is temporarily unavailable during revocation, an encrypted token is held solely for revocation retries, for at most seven days; failures are flagged for operator follow-up. Reconnection is blocked while revocation remains unresolved.
Original Livexio programme recordings and user-uploaded media have a separate lifecycle; deleting YouTube API records does not delete that original media or copies you published to destinations. You can include original media in an account-deletion request. Service providers may process information outside your country; contact us for the relevant storage arrangements and safeguards.
6. Disconnect and request data deletion
Use Remove channel beside a channel on your Destinations page to remove only that connection and its stored YouTube API data from Livexio. Other channel connections are retained. This local removal does not revoke your Google authorization grant; an explicit new connection can authorize the channel again. End broadcasts using that channel first. To withdraw Google authorization and remove all your YouTube connection data from Livexio, choose the separate Revoke all YouTube access control and confirm the account-wide action. Google revocation may also affect connections sharing those grants. After local credentials have already been removed, revoke any remaining Google authorization directly through Google account permissions.
To request deletion by email, including deletion of your account or original Livexio media, contact contact@livexio.com with the subject Livexio data deletion request and identify your account or channel. We verify the requester's authority and process YouTube API-data deletion as soon as possible and within seven calendar days. Account deletion includes the associated YouTube API data.
You can also revoke access in Google account permissions. Daily authorization checks normally detect that change; associated API data is removed upon detection, with a maximum 30-day requirement. Contact us if you need immediate assistance. Deletion controls are documented separately from backup retention; backup copies are restricted and must not be restored into active use without reapplying outstanding deletions.
Deleting information held by Livexio does not delete videos or comments held by YouTube or other destinations. Manage those directly on the relevant platform. Requests about Facebook, Instagram, Twitch and X data can be sent to the same contact address.
7. Rights and contact
Depending on applicable law, you may request access, correction, deletion, portability, restriction, or object to processing. Contact contact@livexio.com. You may complain to your data protection regulator, including the UK ICO.
We publish policy updates here with a revised last-updated date. If we materially change how we use Google user data, we will notify affected users in the app or at their account email address. Before accessing a new category of Google user data or using it for a new purpose not previously disclosed, we will explain the change and obtain the required consent.