🛡️ XUPER TV MAX
Privacy Policy
The developer’s retention settings are not yet confirmed. SDK configuration, permissions, and security practices also need verification. Review these items before removing this notice or treating this document as the final app policy.
1. App, developer, and scope
This policy concerns Xuper TV Max, the Android short drama app with package name com.xupertvmax.world. Its Google Play developer account is XUPER TV MAX. Website: xupertvmax.world. Privacy contact: support@xupertvmax.world.
The developer has confirmed AdMob, Firebase Analytics, Google Play Services, and the Facebook (Meta) SDK. This draft interprets the reported features as no app accounts, Facebook Login, in-app payments, personalized advertising, or child-directed use. These details must match the released app.
2. Information you provide
If you contact support, your email address, message, and attachments are processed to answer your enquiry and handle privacy requests. Avoid sending passwords, payment credentials, government identifiers, or unnecessary sensitive information. The reported app does not require an app account or provide a payment feature.
3. Device and usage information
SDKs can collect data without an app account. Depending on version, configuration, and user choices, this can include:
- IP address and approximate location inferred from it;
- Android advertising ID where enabled, app-instance identifiers, and SDK identifiers;
- Device model, operating system, language, app version, and technical environment;
- App launches, sessions, event interactions, and ad impressions or clicks;
- Diagnostics and SDK performance information.
The final policy must identify the events and identifiers actually collected. This draft does not establish access to GPS location, contacts, SMS, call logs, microphone, camera, files, or installed-app inventory. Any such access must be documented if present. An IP-derived location is different from precise GPS location.
4. Purposes
The described services support non-personalized ad delivery and measurement, usage analytics, evaluation of app reliability, fraud prevention, and support. Only purposes actually enabled in the app should appear in the finalized policy. Identifiers can remain personal data even when they do not contain a person’s name.
5. AdMob
The developer reports non-personalized ads. AdMob can still process IP addresses, identifiers, ad interactions, and diagnostics for delivery, measurement, frequency controls, and fraud prevention. Non-personalized advertising does not mean no information is collected.
See Google’s Privacy Policy and Mobile Ads data disclosures. Verify identifier collection, mediation partners, ad personalization, and consent settings against the actual integration. This policy does not replace an in-app consent interface.
6. Firebase Analytics
Firebase Analytics measures app use through events and identifiers. It may record automatic activity and developer-configured events. Verify the event list, advertising-ID collection, consent controls, advertising integrations, and retention setting. Firebase Authentication and Crashlytics are not assumed simply because Firebase Analytics is present.
See Firebase privacy information and Analytics collection controls.
7. Google Play Services
Google Play Services is integrated in the app. Google’s handling depends on the components used and their configuration. This does not mean the developer receives every category of information Google holds. Refer to Google’s Privacy Policy.
8. Facebook (Meta) SDK
The Facebook SDK can send app events, technical information, and identifiers to Meta when corresponding collection features are enabled. Automatic event logging and advertising-ID collection have configurable settings that need verification. Facebook Login is reported as unused, so collection of a Facebook profile through login is not assumed.
Meta’s processing may include measurement and other business-tool purposes depending on the integration. See Meta’s Privacy Policy and Meta Business Tools Terms. Confirm actual events and data-use settings before claiming that Meta processing is limited to non-personalized uses.
9. Sharing and other recipients
SDK information is sent to relevant providers, including Google and Meta. It can include identifiable or pseudonymous information, and must not be described as exclusively anonymous. Support correspondence is processed through the email provider. Any additional backend, video, hosting, or mediation provider receiving data must be identified in the final policy.
Any legal disclosures, business transfers, and legally defined sale or sharing practices must be described according to actual operations; the SDK list alone does not establish them.
10. Permissions, consent, and choices
Android settings allow management of app permissions and available advertising-identifier controls. Options vary by device. Provider privacy settings may offer additional choices. Permission to use a device feature, an advertising preference, and analytics consent are different controls.
The app must provide any required prominent disclosure and consent before the corresponding collection starts. Opening the app, scrolling past a policy, or dismissing a disclosure does not establish affirmative consent. No in-app opt-out or privacy-settings feature is claimed without verification. The final policy must explain the controls actually implemented.
11. Data retention
Pending developer confirmation: Firebase Analytics retention is not yet known. The final policy must state the actual setting and retention period or specific retention criteria for support emails, server records, and any other developer-controlled data, including backup deletion and legitimate exceptions.
Google and Meta retain information they control under their own policies and settings. Their retention is separate from information directly controlled by XUPER TV MAX. This draft does not invent fixed retention periods.
12. Deletion requests
You can request deletion of personal information controlled by XUPER TV MAX by emailing support@xupertvmax.world with the subject “Xuper TV Max data deletion request.” Describe the information or support correspondence concerned. Do not send passwords or financial credentials.
The developer has confirmed that deletion requests will be handled through this email. The final policy must specify verification, processing times, and any justified retained information. Some SDK data is controlled by providers or cannot be associated with a particular person by the developer; provider privacy tools and request processes may apply separately.
Uninstalling stops this installation from collecting new data, but does not automatically erase previously transmitted data. No app account is reported. If account creation is introduced, the app must offer in-app deletion initiation and an external deletion resource, and describe deletion of associated data.
13. Regional privacy rights
Depending on applicable law, you may have rights to access, correct, delete, or receive a copy of your information; restrict or object to processing; withdraw consent; or appeal a decision. Other rights may concern targeted advertising or legally defined sale or sharing. Email the privacy contact with your enquiry. Any relevant legal bases, response process, operator details, representatives, and complaint routes must be verified for the markets served.
14. Children
The developer reports that the app is not directed to children. The target-age range and Play Console audience declarations still need verification; this draft does not invent an age threshold. Parents or guardians can contact support with privacy concerns. The final policy, consent arrangements, and SDK settings must reflect the actual audience.
15. Security
No method of transmission or storage is completely secure. Pending verification: describe the actual safeguards for app traffic, developer-controlled information, and support records. Check encrypted transport for every endpoint and access controls before making specific security claims. Third-party SDKs alone do not establish security across the app.
16. International processing
Google and Meta operate services internationally, so SDK data may be processed outside your country. Their policies explain their arrangements. Locations and transfer safeguards for developer-controlled information must be verified before making specific claims.
17. Website and external links
The promotional website has a separate website privacy policy. Google Play and other external services have their own policies. Links to providers do not mean the app integrates all their products.
18. Changes and contact
Update this policy when features, SDKs, collection, sharing, retention, or deletion practices change. The final policy must state its effective date and actual notification method. For privacy enquiries, contact XUPER TV MAX at support@xupertvmax.world.