Privacy Policy

ZAVRO uses Google authentication services and YouTube API Services. A creator must sign in with Google, agree to this Privacy Policy, and expressly authorize the requested permissions before ZAVRO accesses Google User Data associated with that creator's account.

ZAVRO only accesses YouTube channels and live broadcasts selected or authorized by the creator and only requests permissions needed for features that are currently available in ZAVRO. Each live-stream session is initiated by the creator. ZAVRO retrieves data for the selected broadcast while that session is active; when the session ends, ZAVRO stops actively retrieving data for that broadcast. Ending an individual live-stream session does not by itself revoke the creator's Google OAuth authorization unless the creator separately disconnects or revokes that authorization.

In addition to OAuth-authorized connections, ZAVRO supports public read-only channel binding via public channel links or handles. In this mode, ZAVRO accesses only the user-specified public channel's public profile, public videos, and public comments. Public binding does not represent channel ownership, does not prove channel ownership, and grants no administrative or management permissions over the channel.

ZAVRO uses Google User Data only for the purposes disclosed in this Privacy Policy and only to provide or improve user-facing features that are visible to the creator. Specifically:

• Google account information is used to authenticate the creator and associate the authorized Google or YouTube account with the creator's ZAVRO account;
• YouTube channel information is used to identify the creator-authorized channel and display the correct channel connection in ZAVRO;
• Broadcast information is used to identify and connect to the live stream selected by the creator;
• Live-chat messages, message timestamps, and publicly displayed participant information are used to retrieve, display, organize, and process audience discussion for the authorizing creator. Raw live-chat messages may also be retained for a limited period, up to 30 calendar days, so the authorizing creator can review recent live-stream activity and use ZAVRO's creator-support features;
• Where permitted by YouTube API Services policies and any approval required for the applicable use case, live-chat data may be used to generate creator-facing summaries, topic groupings, recurring questions, viewpoints, sentiment or discussion signals, and suggested response priorities;
• OAuth tokens and authorization information are used only to maintain the connection authorized by the creator and to make the API requests necessary for the enabled features;
• Limited Google User Data may be used to secure the service, detect abuse or unauthorized access, troubleshoot failures, and respond to creator-initiated support requests; and
• Google User Data may be used to improve the reliability and usability of the user-facing ZAVRO features for which the data was obtained, subject to Google's Limited Use requirements.

ZAVRO's use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including the Limited Use requirements applicable to the Google OAuth scopes used by ZAVRO.

Accordingly, ZAVRO:

• Uses Google User Data only to provide or improve the user-facing features described in this Privacy Policy;
• Does not sell Google User Data or transfer it to advertising platforms, data brokers, information resellers, or similar parties;
• Does not use or transfer Google User Data for advertising, retargeting, personalized advertising, or interest-based advertising;
• Does not use Google User Data to determine creditworthiness or for lending purposes;
• Does not use Google User Data for surveillance or to infer sensitive protected attributes of creators or live-chat participants, such as race, ethnicity, religion, political affiliation, sexual orientation, health status, or similar sensitive traits;
• Does not use Google User Data to train, fine-tune, or improve generalized machine-learning or artificial-intelligence models; and
• Requires employees, contractors, service providers, and other agents handling Google User Data on ZAVRO's behalf to comply with applicable Google data-use restrictions and confidentiality obligations.

When a creator enables an applicable feature, ZAVRO may use automated language-processing systems, including artificial intelligence, to process selected live-chat messages and organize them into creator-facing summaries, topic groupings, frequently raised questions, viewpoints, or response suggestions.

Any automated processing of YouTube API Data is limited to the creator-authorized use case and is offered only to the extent permitted under the YouTube API Services Terms, Developer Policies, and any additional approval, amendment, or audit status required for that use case.

Where a feature constitutes a derived metric or analytics use case under YouTube policy, ZAVRO will enable that feature only where the applicable YouTube requirements have been satisfied and will clearly identify the resulting information as ZAVRO-generated rather than YouTube-provided data.

ZAVRO-generated outputs are not official YouTube metrics and are not provided, approved, verified, or endorsed by YouTube or Google. Automated outputs may be incomplete or inaccurate, and creators should review them before relying on them or responding publicly.

ZAVRO does not use live-chat messages or other Google User Data to train generalized AI models, does not use such data to profile protected characteristics, and does not combine Authorized Data from unrelated creators or content owners to create cross-user insights about YouTube's business or platform performance.

ZAVRO does not sell YouTube API Data, Google User Data, or personal information.

ZAVRO may provide the minimum information necessary to contracted service providers that perform services on ZAVRO's behalf, including providers of:

• Cloud hosting and data storage;
• Authentication and security;
• Database and application infrastructure;
• Automated language or artificial-intelligence processing for creator-enabled features;
• Error monitoring;
• Customer support; and
• Email delivery.

ZAVRO retains information only for as long as necessary for the purposes described in this Privacy Policy and subject to applicable Google and YouTube API data-retention rules.

Unless a different period is expressly permitted by YouTube for the applicable data type and use case:

• Raw live-chat messages from creator-authorized streams may be retained for up to 30 calendar days from the date they are accessed so the authorizing creator can review recent live-stream activity and use ZAVRO's creator-support features. Raw live-chat message text is deleted no later than the end of that period, unless an earlier deletion requirement applies because the creator requests deletion or revokes authorization;
• Other YouTube Authorized Data that is subject to YouTube's 30-day storage rule is retained only as long as necessary for the creator-authorized purpose and for no longer than 30 calendar days, after which ZAVRO deletes or refreshes that data as required by YouTube API Services policies;
• OAuth access and refresh tokens may be retained for as long as necessary while the creator's Google authorization remains active, provided the tokens are used only for the purposes covered by that authorization. Ending an individual live-stream session stops that session's active access to the selected broadcast but does not, by itself, revoke Google OAuth authorization;
• ZAVRO account information is retained while the ZAVRO account remains active, unless earlier deletion is requested or required; security and operational logs may be retained for a limited period necessary for fraud prevention, security, troubleshooting, and legal compliance; and
• Derived analytics or metrics are retained only for the period permitted under applicable YouTube policies and any approval or amendment applicable to ZAVRO. If ZAVRO is permitted to retain eligible derived metrics for an extended period, that extended period does not apply to raw live-chat or comment text, video titles, creator names, descriptions, or other API Data that remains subject to YouTube's refresh or deletion requirements.

Creators may disconnect their YouTube account through ZAVRO's account or connection settings. When a creator revokes Google or YouTube authorization through ZAVRO's revocation mechanism, ZAVRO will promptly programmatically revoke the applicable Google token and delete Authorized Data accessed or stored pursuant to that consent as soon as possible and no later than seven calendar days after the revocation.

Creators may also revoke ZAVRO's Google authorization through the Google Security Permissions page. ZAVRO periodically reconfirms that stored authorization tokens remain valid. When ZAVRO detects that authorization has been revoked through Google's security settings, ZAVRO will stop accessing the account and delete API Data associated with that authorization as soon as possible and no later than 30 calendar days after the revocation, in accordance with YouTube API Services policies.

Ending an individual live-stream session is different from revoking Google OAuth authorization: the end of a session stops active retrieval for the selected broadcast, while revocation terminates the underlying authorization and triggers the applicable deletion process described above.

Revoking ZAVRO's access or deleting data from ZAVRO does not delete content or information stored by YouTube. To delete data from YouTube, users must use YouTube or another authorized application that provides the relevant deletion function.

Users may request deletion through ZAVRO's account-deletion function or by contacting privacy@zavro.net.

After receiving a valid deletion request, ZAVRO will delete the user's ZAVRO account information, related stored YouTube API Data, and associated creator-specific outputs as soon as possible and no later than seven calendar days, except where limited retention is required by applicable law.

Subject to applicable law, users may request to:

• Access personal information associated with their ZAVRO account;
• Correct inaccurate information;
• Disconnect their Google or YouTube account;
• Delete stored data;
• Delete their ZAVRO account; or
• Ask questions or submit complaints regarding our privacy practices.

ZAVRO uses reasonable administrative, technical, and organizational safeguards designed to protect Google User Data and other information against unauthorized access, use, disclosure, alteration, loss, and misuse. ZAVRO uses industry-standard transport encryption for data transmitted between systems and applies access controls and other security measures to stored data and credentials.

Access to production systems and Google authorization credentials is restricted to personnel and service providers with a legitimate operational need and is subject to appropriate confidentiality and security obligations.

However, no internet transmission or storage system can be guaranteed to be completely secure.

ZAVRO is operated by a company based in Singapore. Information may be processed in Singapore and in other countries where ZAVRO's contracted service providers operate.

Where required, we use appropriate safeguards for international transfers of personal information.

ZAVRO is intended for creators who are legally able to enter into a binding agreement. ZAVRO is not directed to young children, and we do not knowingly invite children below the applicable minimum age to create ZAVRO accounts.

We may update this Privacy Policy to reflect changes to ZAVRO, applicable law, Google API Services requirements, or YouTube API Services requirements.

If ZAVRO changes how it accesses, uses, stores, or shares Google User Data in a way that was not previously disclosed, we will update this Privacy Policy and, where required by Google policies or applicable law, provide notice and obtain consent before using Google User Data for the new purpose.

The updated version will be published on this page with a revised "Last Updated" date.