Privacy Policy
Last updated: 2026-09-30
Multichat and YouTube API Services
This section applies to Multichat, our private chat reader and browser-source service. The purchase, payment and licence provisions below apply to the storefront, not to connecting a YouTube channel in Multichat. Read the full Multichat privacy policy for all platforms and workspace controls.
Multichat uses YouTube API Services with your authorised read-only permission. It accesses and uses:
- OAuth access and refresh tokens, encrypted in storage, to authenticate API requests. We never receive your Google password.
- Your YouTube channel ID and title, saved to identify your connection and show the connected channel.
- Active broadcast IDs, titles, start times, status and live-chat IDs, used to discover streams and select their chats. Broadcast details are held in memory; selected identifiers are saved as workspace settings.
- Live-chat message IDs, text, timestamps, author channel IDs, display names, profile-image URLs, roles, membership events and available Super Chat/Super Sticker details and amounts. These are processed into attributed messages for your reader, selected browser sources and any messages you deliberately queue or feature. Supplied deletion/ban events remove affected content locally.
Cloudflare processes the data on our behalf to host Multichat and its database. TT Interactive's operator can access connection records and diagnostics where needed for maintenance and support; routine logs exclude complete chat payloads and credentials. Google receives authorised API requests, and its image servers receive ordinary image requests from readers. People given your reader, source or producer links can receive the data allowed by those links. When you broadcast a source, its displayed content is shared with your broadcasting software, streaming destination and audience. We do not sell YouTube data, use it for advertising, or pass it to other chat platforms, Euler Stream, third-party emote services, AI or remote text-to-speech services.
Chat polling follows YouTube's required interval or a longer service-budget interval. Active broadcasts refresh normally every 15 minutes, with idle checks backing off from two to 15 minutes. Ordinary YouTube chat/activity expires from the live buffer within 24 hours; deliberately queued selections expire within 24 hours of selection. Saved channel details and continuing authorisation are checked approximately daily, including idle workspaces. A connection that cannot be refreshed within 29 days of its last successful check is removed with its active credentials and queued selections. Pre-update records use a conservative expiry from 21 September 2026 until refreshed. We do not collect channel/video view, like or subscriber statistics or historical analytics. Message-rate indicators describe only messages received in the last 60 seconds.
Disconnect YouTube or Delete workspace to remove active stored data, or revoke access through Google security settings. Earlier encrypted database states can remain in Cloudflare point-in-time recovery for up to 30 days and are not served to users; deletions and revocations must be reapplied before recovery is reopened. Contact teamwgmojo@gmail.com for deletion requests or privacy questions. Multichat uses essential session cookies, saved reader preferences and browser storage for private-link access; it has no advertising or analytics scripts.
See the Google Privacy Policy, YouTube Terms of Service and Multichat Terms of Service. Multichat does not upload videos, send chat or moderate native YouTube content.
1) Who we are
Harry Blanchflower, trading as TT Interactive, is the operator of wgmojo.gg and the controller responsible for the personal data described in this policy (“we” / “us”). If you have questions or want to exercise your rights, contact teamwgmojo@gmail.com.
2) What personal data we collect
- Email address (for receipts, delivery, and support)
- Payment and order metadata (processed via Stripe): transaction IDs, purchased items, timestamps, the version and server-recorded time of any immediate digital-supply acknowledgement, and billing information needed for the purchase (we don’t receive your full card details)
- Download and delivery logs (via Cloudflare/R2 and the checkout worker): IP address, user agent, country, timestamps, filenames/request URLs, and download type to deliver files reliably, monitor downloads, and prevent abuse
- Software licence and activation data: product and entitlement, licence status, activation time, software/build version, and a keyed hash of the installation identifier used to enforce the disclosed device limit. We do not need to keep the raw installation identifier in the licence ledger
- Marketplace and membership fulfilment data (where you buy through Etsy or receive a Patreon benefit): provider account/member or receipt identifiers, email, purchased item or tier, payment/access state, fulfilment, refund/cancellation, and support history
- Creator referral data: an explicitly entered creator code, pseudonymous creator identifier, commission rate, attributed order and refund/dispute state, privacy-preserving self-referral screening values, eligible-net calculation, review state, and masked payout reference. Entering a code does not set a referral tracking cookie
- Creator enrolment and payout data (only after the programme opens): legal name, age/eligibility confirmation, country and tax residence, business/tax status and identifiers where legally required, sanctions/identity-check outcome, payout contact, and masked payout-account/provider references. Identity documents and full payout credentials must be collected by an approved authenticated provider, not by the public website, ordinary email, or the checkout Worker
- Email delivery events (via Resend): message and provider event identifiers, recipient, template/purpose, timestamps, and delivered, delayed, bounced, complained, opened, or clicked state where the configured event provides it
- Site usage and performance analytics (via Cloudflare Web Analytics): basic page-view, referrer, device/browser, country, and performance information used in aggregated reports
- Form submissions (via the checkout/support worker and Resend): the details you enter (e.g. name, email, stream URL, product, feedback type, and your request message)
- Form anti-spam metadata (via Cloudflare Turnstile and the checkout/support worker): Turnstile verification, timestamps, honeypot/timing signals, duplicate fingerprints, IP-derived rate-limit signals, and spam-review verdicts
- Support messages and bundles you choose to send us, including attachments and the redacted diagnostics, build, compatibility, connection health, recent event/result, and log data contained in a diagnostic support bundle
3) Why we use it
- To process orders and fulfil digital delivery (including sending download links)
- To issue, verify, recover, limit, revoke, and support software licences and entitlements
- To administer opted-in creator referrals, reconcile eligible-net commission, prevent self-referral, and record manual payouts
- To provide support and respond to questions
- To prevent fraud, abuse, and unauthorised sharing
- To filter spam and route feedback, support, and custom-request submissions
- To maintain basic operational security and improve reliability
- To understand basic site usage and performance without advertising or cross-site tracking
4) Legal bases (UK GDPR)
We process personal data under these legal bases (high level):
- Contract: to take payment, deliver your purchase, and provide essential service emails
- Legitimate interests: to operate and secure the site and digital delivery; prevent fraud, abuse, unauthorised sharing, and spam; diagnose faults and support issues; and understand basic site usage and performance. These are the interests we pursue. We use limited data and do not rely on this basis where your rights and interests override ours
- Legal obligation: to keep records where required for accounting, tax, or legal compliance
- Consent (where applicable): for anything optional you choose to sign up to or request
5) Who processes data (our service providers)
We use trusted providers to run payments, delivery, and messaging:
- Stripe (payments and order processing)
- Resend (sending delivery and support emails, and handling form submissions, such as custom requests and feedback)
- Cloudflare (site and file delivery, R2 file storage, security, Turnstile anti-spam checks, logs, KV counters, Workers Analytics Engine, and Web Analytics)
- Etsy (marketplace orders, cancellation/refund events, buyer messages, and digital fulfilment where that sales channel is offered)
- Patreon (membership identity, eligible tier/access state, and benefit fulfilment where that offer is enabled)
- Approved identity and payout provider (creator enrolment, sanctions/identity checks, tax forms, and payouts). No provider is selected and no enrolment data is collected during the private candidate; this notice and the programme terms must name the provider before enrolment opens
- Discord (internal feedback, download, and operational notifications, where configured)
These providers may process data outside the UK. Where that happens, we rely on appropriate safeguards used by those providers (such as standard contractual clauses) to protect data.
Cloudflare states that Cloudflare Web Analytics does not use cookies, localStorage, or fingerprinting to display analytics.
6) Data retention
We keep personal data only for as long as needed:
- Order and payment records: typically up to 6 years for accounting and tax obligations
- Licence and referral accounting records: typically up to 6 years after the relevant order, payout, or programme relationship, where needed for contract, fraud, accounting, tax, or legal records
- Creator enrolment: incomplete or rejected applications normally up to 90 days after review; accepted creator, tax, sanctions-check outcome, and payout records normally up to 6 years after the relationship or final payout. Any approved identity/payout provider has its own disclosed retention, which must be reviewed before enrolment opens
- Support emails: while the issue is active and for a reasonable period afterwards (typically up to 24 months)
- Raw diagnostic support bundles: unsolicited diagnostic bundles are not accepted. If support later requests a redacted bundle for a specific case, you will receive case-specific intake and handling instructions before sending it. This notice and the tested deletion workflow must be updated before automated bundle intake opens
- Detailed email delivery-event records: typically up to 180 days for delivery troubleshooting and complaint handling; minimal suppression state may remain while needed to prevent harmful repeat sends
- Custom request and feedback submissions: typically up to 12 months, unless ongoing work or support requires longer
- Feedback anti-spam counters: duplicate fingerprints are kept for up to 14 days, and hashed IP burst counters for up to 3 hours
- Download and delivery logs: typically up to 90 days, unless needed to investigate abuse or faults
- Cloudflare Web Analytics reports: currently available in Cloudflare for the previous 6 months
7) Your right to object
You have the right to object to processing based on our legitimate interests. Tell us what you object to by emailing teamwgmojo@gmail.com. We will stop unless we have compelling legitimate grounds to continue or need the processing for legal claims.
8) Your other rights
Under UK data protection law, you have rights including:
- Access to your data
- Correction of inaccurate data
- Deletion (where applicable)
- Restriction of processing (where applicable)
- Data portability (where applicable)
- Withdrawing consent (where consent is the legal basis)
To make a request, email teamwgmojo@gmail.com from the email address used for your order where possible. We may ask for information to verify your identity.
9) Data-protection complaints
To complain about how we use your personal data, email teamwgmojo@gmail.com. Tell us which use of your data or decision you are complaining about and what outcome you are seeking. Please do not send more personal data than we need to understand and investigate your complaint.
We will acknowledge receipt within 30 days. We will investigate your complaint, keep you informed where needed, respond, and tell you the outcome, all without undue delay.
You can also complain to the UK Information Commissioner’s Office (ICO) if you’re unhappy with how we handle your data.
10) Changes to this policy
We may update this policy from time to time. Updates will be posted on this page.
11) TikTok API integration (internal use only)
We also operate a private, internal TikTok integration used only by the account owner (Harry / TT Interactive). It is not offered as a public tool or service.
For this integration, we request TikTok Login Kit scope user.info.basic and TikTok Content Posting API scope video.upload.
Data obtained through these scopes is used only to authenticate the user and upload videos to that same user's TikTok account. We do not use this data for advertising, profiling, or resale, and we do not share this data with third parties other than using TikTok's own API to complete the requested authentication or upload.
Privacy questions
Does Multichat get my Google password?
No. Multichat uses read-only YouTube permission with OAuth tokens, encrypted in storage. We never receive your Google password.
Who hosts Multichat data?
Cloudflare processes the data on our behalf to host Multichat and its database.
Where is the full Multichat policy?
Read the full Multichat privacy policy, linked at the top of this page, for all platforms and workspace controls.