MADFLIXMADFLIX does not require a separate MADFLIX user account. This policy describes data processed by the application, Google services, the MADFLIX security backend, advertising providers, Cloudflare, and third-party channel sources.
1. Scope
This policy applies to the MADFLIX Android application and the official website at madflix-support.pages.dev. It does not replace the independent privacy terms of Google Play, advertising partners, Cloudflare, or third-party channel providers.
2. Data processed on your device
MADFLIX may store favorites, recently viewed channels, stream-resolution cache data, language and interface preferences, ad-frequency timing, consent status, a randomly generated installation identifier, and encrypted entitlement information. Local information remains until it expires, is replaced, app storage is cleared, or the app is removed.
3. Analytics, stability, and crash diagnostics
Production builds may use Google Analytics for Firebase and Firebase Crashlytics to understand app launches, sessions, device categories, feature use, stability, crashes, non-fatal errors, and application-not-responding events. Depending on Google configuration and user consent, these services may process app-instance identifiers, device and operating-system information, approximate location inferred from IP address, timestamps, screen or event names, diagnostic logs, and crash traces.
MADFLIX uses this information to improve television memory behavior, playback reliability, release quality, user retention, and monetization placement. Analytics is not intended to store channel credentials, payment-card information, passwords, or private signing material.
4. Advertising and consent
On supported phones and tablets, MADFLIX uses Google Mobile Ads and Google User Messaging Platform. Google and its advertising partners may process advertising identifiers, IP address, device information, approximate location inferred from IP address, consent choices, ad requests, impressions, interactions, fraud signals, and diagnostics. Where required, MADFLIX requests privacy choices before requesting personalized advertising.
Ads are not displayed over active live-channel playback. Android TV builds do not initialize the Google Mobile Ads SDK in this release.
5. Purchases, subscriptions, access keys, and integrity
Google Play handles payment-card and billing-account information. MADFLIX receives a Google Play purchase token and subscription status, not full card details. To verify ad-free access and prevent fake receipts or receipt reuse, MADFLIX sends purchase and product identifiers, installation information, application package and version details, and Play Integrity security data over HTTPS to the MADFLIX backend.
Purchase tokens are encrypted in the backend database. License keys and access tokens are stored as cryptographic hashes where feasible. A subscription or authorized access key may be limited to a controlled number of installation identifiers. Security records may include hashed IP and installation identifiers, request outcomes, and limited diagnostic information.
6. Cloudflare processing
The MADFLIX backend and this support website use Cloudflare services. Cloudflare may process network and security information such as IP address, request headers, timestamps, and abuse signals to deliver and protect the service. MADFLIX uses Cloudflare Workers and D1 for entitlement verification, rate limiting, and security-event handling.
7. Third-party channel sources
MADFLIX is a directory and player for third-party sources. When a channel is opened, the device may connect to that channel's source, content-delivery network, or embedded-player provider. Those parties may receive IP address, device or network information, user agent, and playback requests under their own policies. MADFLIX does not control independent third-party data practices.
8. Purposes
- Operate playback, favorites, recent channels, and interface preferences.
- Measure stability, sessions, retention, and feature use.
- Provide and measure advertising while respecting applicable consent choices.
- Verify subscriptions and authorized access.
- Prevent fake purchases, duplicate use, automated abuse, tampering, and unauthorized installations.
- Diagnose failures, maintain security, answer support requests, and process rights-holder requests.
9. Retention
On-device information remains until cleared, replaced, expired, or the app is uninstalled. Backend rate-limit records are designed for short retention, while limited security-event records may be retained for approximately 30 days. Purchase, entitlement, activation, and integrity records may be retained while needed to provide access, detect fraud, resolve disputes, satisfy legal obligations, or defend the service. Analytics and crash retention is controlled through the applicable Google service settings.
10. Sharing
MADFLIX does not sell personal information. Information may be disclosed to providers that operate advertising, analytics, crash diagnostics, billing, integrity verification, hosting, security, and channel delivery; to authorities where legally required; or as necessary to protect users, rights holders, MADFLIX, and the public.
11. Your choices and deletion requests
Clear app data or uninstall MADFLIX to remove locally stored information. Where required, the app provides Google's privacy-options entry point for advertising choices. To request deletion of eligible backend information associated with an installation, purchase, access key, support request, or channel-removal request, follow the data-deletion instructions.
12. Children
MADFLIX is not directed to children and should not be designated for children in Google Play. Live third-party programming may vary by source and region.
13. Security
Data in transit is protected with HTTPS. Sensitive entitlement information stored on supported devices uses Android Keystore-backed encryption, and purchase tokens stored by the backend are encrypted. No system can be guaranteed completely secure.
14. Contact and changes
Privacy, support, security, and verified channel-owner requests may be sent to madconnect.dev@gmail.com. Material policy changes will be posted here with an updated effective date.
Yosif Al-khazaali
United States
madconnect.dev@gmail.com