Information MADFLIX may process
MADFLIX and service providers may process app or device identifiers, app interactions, diagnostics, advertising consent and delivery information, store purchase tokens, subscription status, installation identifiers, package/version information, device model information, and security or integrity results when needed for operation, advertising, fraud prevention and entitlement verification.
Discover recommendations
Discover uses a randomly generated app-installation identifier to remember recommendations. When personalization is enabled, MADFLIX may send content identifiers from existing Favorites and viewing history, preview interactions, watch-duration milestones, feedback and country-level connection information to its Cloudflare-hosted recommendation service. Interface language is not treated as a content-language preference. Discover does not use your IMEI or Android hardware identifier for personalization.
You can turn personalization off, reset recommendations or clear Discover history in Discover Settings. Turning personalization off stops behavioral event collection; explicit Hide and Not Interested choices still work. Resetting Discover does not erase ordinary Favorites or watch progress. Raw Discover events are retained for up to 90 days. Aggregate statistics without individual identifiers may be retained longer to measure quality and reliability. Recommendation state remains associated with the app installation until reset or deletion. Public sharing links contain the content identifier and optional campaign labels, not your private recommendation identifier.
Watching updates
Watching updates are enabled in app settings by default and can be disabled or customized there. Android notification permission and device notification settings also apply. The app uses locally saved viewing progress to check for new episodes and verified story connections, prepare a new-arrivals digest, and offer occasional continue-watching reminders. Individual title identifiers are requested from MADFLIX catalog services; the notification feature does not upload your full watch-history list or use a separate advertising identifier. Notification preferences, muted titles and recent updates are stored on your device. Background checks are periodic, may be delayed by Android, and do not guarantee playback-server availability.
Advertising and privacy choices
Free users may receive advertising through advertising service providers. Newer MADFLIX versions use Unity LevelPlay mediation with participating networks such as Unity Ads, ironSource and, when enabled, InMobi. Older versions may contain Google AdMob. TV video-ad inventory is configured separately from phone and tablet advertising.
Ad providers may process device and advertising identifiers, IP addresses, approximate location inferred from the connection, app/device information, ad requests, impressions and interactions to deliver, measure and protect advertising. MADFLIX does not request precise device location for these integrations.
Starting with version 4.1.15, the mobile mediation integration is configured to request non-personalized/contextual advertising, with behavioral-ad consent disabled and a do-not-sell/share restriction. Contextual advertising can still involve identifiers and technical data for delivery, measurement and fraud prevention. InMobi CMP collects and stores applicable regional privacy choices and shares TCF, Additional Consent and GPP signals with providers. Required regional consent is handled before eligible ad requests; optional controls are available in Settings. You can reopen Privacy choices in app Settings. Declining personalization does not make MADFLIX a paid app; available contextual advertising and regional consent requirements still apply. Ad availability is not guaranteed.
Analytics and crash diagnostics
MADFLIX uses Google Firebase Analytics and Crashlytics to understand app usage, ad delivery and SDK-confirmed ad revenue, and diagnose crashes and stability problems. Information may include app/device details, pseudonymous identifiers, app interactions, error reports and technical logs. Starting with version 4.1.15, Firebase advertising storage, advertising user data and ad personalization remain denied. Analytics storage defaults to denied and is enabled only when the user grants it through Privacy choices. Installing the app does not grant advertising or analytics consent. Crash diagnostics are used separately for reliability. MADFLIX does not need access to raw payment-card details for store purchases.
Provider information: Unity privacy policy, InMobi privacy policy, and Google privacy policy.
Purchases and access
Purchase tokens and installation identifiers may be transmitted over HTTPS to MADFLIX backend services to verify ad-free access and enforce installation limits.
External content and services
Availability of third-party channels, metadata and playback services can vary. External providers may process connection information according to their own terms and privacy practices.
Retention and deletion
Operational, entitlement, security and fraud-prevention records may be retained only as reasonably necessary. To request deletion, use the Data deletion page or contact support.
Security
Backend communication uses HTTPS and release builds use integrity and signing controls.
Contact
Privacy questions: madconnect.dev@gmail.com.
Changes
Effective date: September 23, 2026.