Legal

Privacy Policy - FlipZi: Cast & Mirror to TV

Effective October 8, 2026

This privacy policy applies to FlipZi: Cast & Mirror to TV (Android package app.flipzi.cast), published on Google Play by TwentyThree Labs.

TwentyThree Labs is the developer responsible for the app and the handling of information described in this policy. This policy explains how information is handled when you use the app and this website.

Information FlipZi handles

How media is transferred

FlipZi sends supported media and live output directly over your local network to the TV or receiver you select. FlipZi does not upload your personal media to a FlipZi cloud service. A website opened in Web Video remains subject to that website's own privacy practices.

Web Video analyzes the current page on your device to find public media candidates. This can include HTML video or audio elements, same-origin frames, media URLs exposed by supported page players, and media-shaped browser or ServiceWorker requests. FlipZi validates candidate addresses and media types before showing Cast. This analysis is bounded, does not continuously poll the page, and does not upload webpage contents, browser history, media candidate lists, or stream bytes to a FlipZi cloud service.

The standard release does not inspect or relay raw media requests from YouTube, Facebook, Instagram, TikTok, Vimeo, Dailymotion, Twitch, Reddit, X, VK, or OK pages. For those services, FlipZi keeps playback in an official player or app when available and otherwise offers screen mirroring. An internal restricted build can enable direct platform-stream research. In that build, FlipZi processes public player metadata and media requests on the device and may relay a selected unprotected stream to the selected receiver. It still does not forward account cookies, Authorization, passwords, or DRM material to the receiver.

When you choose Cast video or Cast audio, FlipZi checks the selected receiver's reported format support. It may send a validated public media address directly to that receiver, or temporarily relay progressive media, HLS resources, or a constrained non-DRM DASH manifest through your phone on local Wi-Fi. The relay uses opaque, short-lived addresses restricted to the selected receiver and stops when playback ends. Upstream website requests may include the Web Video user agent, byte ranges, and a scoped Referer or Origin needed for playback; page query strings and fragments are removed from Referer. FlipZi does not forward website cookies or Authorization headers to unauthenticated TVs. DRM, key-bearing HLS, and unsupported manifest features fail closed to mirroring or the official service.

Websites opened inside FlipZi may keep cookies and local site storage on your device so sign-ins completed in FlipZi can persist. Android and iOS do not allow FlipZi to read passwords, cookies, or account sessions from other apps, Chrome, or Safari. Web Video History and Most visited lists remain session-only.

Advertising

FlipZi may display advertising only in an ads-enabled build. Where ads are enabled, Google Mobile Ads may process device information, IP address, advertising identifiers, coarse location derived from IP, and ad interactions to deliver, secure, and measure ads. FlipZi requests Google UMP consent information worldwide and makes no ad request until UMP permits it. Google may show a configured IAB TCF vendor-and-purpose form in the EEA, United Kingdom, and Switzerland, a configured US-state privacy message where applicable, and no required form in other regions. Required choices can be reopened from Advertising privacy in Settings. Advertising consent never enables product analytics or crash diagnostics.

Optional product analytics

Product analytics is off unless you explicitly enable it in FlipZi. When enabled, FlipZi sends bounded events about feature use, discovery, connection, and playback outcomes to Google Firebase Analytics. Firebase also processes a random app-instance identifier, standard app and device details, and approximate region derived from network information. FlipZi does not add TV names, receiver identifiers, IP addresses, Wi-Fi names, filenames, media titles or content, browser URLs, pairing data, credentials, or free-form text to analytics events.

No activity from before your choice is sent later. You can turn product analytics off at any time under Analytics & crashes in Settings; collection then stops and the Firebase app-instance identifier is reset. Google handles previously received analytics data under its retention and privacy terms.

Optional crash and diagnostic reporting

Crash and diagnostic reporting is off unless you explicitly enable it. When enabled, FlipZi may send redacted crashes and ANRs to Firebase Crashlytics and bounded operation outcomes to Firebase Firestore so non-crashing failures can be diagnosed. These reports can include a random FlipZi install identifier, Firebase installation and session identifiers, app version and build, device brand and model, operating-system version and API level, locale, feature, operation stage, closed-set outcome and reason, coarse duration, and retry count. If product analytics is also enabled, bounded Firebase Analytics events may appear as Crashlytics breadcrumbs.

FlipZi removes raw exception messages from handled Dart errors it submits. Firebase-managed native fatal-crash and ANR reports may include provider-captured exception messages. FlipZi does not add screenshots, view hierarchy, media, filenames, browser URLs, cookies, credentials, TV names, local-network addresses, account identity, or other private free-form fields to these reports. Turning the option off clears the local diagnostic Firestore cache, removes the random FlipZi diagnostic identifier, and stops new reports; an already submitted network request may complete. A later opt-in starts a new FlipZi diagnostic cohort. Firebase provider identifiers and previously received records remain subject to Google's retention and privacy terms.

Operational configuration

FlipZi uses Google Firebase Remote Config to retrieve operational settings such as feature availability and the minimum supported app build. This request may process a random app-installation identifier, app version, platform, language, IP address, and standard device information. It does not include your media, TV details, local-network addresses, browser activity, pairing data, account credentials, or support text. Operational configuration is separate from optional product analytics and is used to keep the app compatible, safe, and recoverable.

Data sharing and sale

FlipZi does not sell personal information. Information is shared only with the TV or receiver you select, operating-system services needed to perform a feature, Google Firebase Remote Config for operational settings, Google Firebase Analytics when you enable product analytics, Firebase Crashlytics and Firestore when you enable crash and diagnostic reporting, and Google Mobile Ads when advertising is enabled and UMP permits an ad request.

Retention and control

Remembered TVs, preferences, saved page bookmarks, browser site data, local diagnostic history, and support drafts remain on your device until you clear them or uninstall the app. Detected candidate lists and relay mappings are session-only. Temporary media copies, session-only browsing history, and conversion files are removed when no longer needed. You can revoke permissions in system settings, change analytics and diagnostic choices in FlipZi Settings, reopen required UMP advertising choices where available, and reset or limit the advertising identifier through your device's privacy controls.

Children

FlipZi is not directed to children under 13 and is not intended to knowingly collect personal information from children.

Security

FlipZi uses platform permissions, encrypted receiver pairing where supported, bounded local servers, and transport checks. No networked product can guarantee absolute security.

Changes

Material changes will be posted here with a revised effective date.

Developer and privacy contact

Contact TwentyThree Labs about privacy requests at privacy@flipzi.app. For product help, use support@flipzi.app.