NexaIPTV PLAYER

YOUR ACCOUNT AND DATA

Privacy policy

Nexa IPTV Player · Android package com.nexasystems.iptvplayer
Last updated:

This policy covers the Nexa IPTV Player application, the Fire TV edition Nexa Media Player, and the account services at nexasysteme.com. Nexa is a media player for playlists you choose to add.

Delete your account and data · Privacy contact

1. Who is responsible and how to contact us

The data controller is Salvador Carrasco Olmedo, operating Nexa IPTV Player (Nexa-Systems). For privacy questions or requests concerning your personal data, email nexasystems5@gmail.com.

2. Information used by the service

3. Why information is processed

Account and playlist data are processed to provide sign-in, synchronize your lists, connect your devices and deliver the license you request. Purchase and billing data are used to manage payments, renewals, refunds and invoices. Necessary service processing is based on performance of the contract; required billing records are processed to meet legal obligations. Proportionate abuse prevention and account security are based on legitimate interests. Where consent is required for optional processing, it must be obtained separately; reading this policy does not itself provide consent.

4. Google advertising SDK in the Android app

The current Android application includes and initializes the Google Mobile Ads SDK (AdMob). Whether an advertisement is displayed depends on the app configuration. The SDK can process IP addresses, device and advertising identifiers, app interactions and diagnostic information for advertising, measurement and fraud prevention, including when a banner is not visible. An IP address may be used to estimate a general location; this is different from requesting GPS location.

You can manage or delete your advertising ID through Android settings. See Google’s privacy policy and Google Mobile Ads data information. The public Nexa website does not include advertising or an analytics tracker.

5. Providers and data sharing

IONOS hosts the website and account backend. Google/Firebase and Amazon provide sign-in, and Google provides the app advertising SDK described above. Stripe processes website payments and subscriptions. If personalized invoice delivery is enabled, the configured email provider processes the recipient address, message and attached invoice. Information is also processed when necessary to handle support requests or comply with a binding legal obligation.

When you load or play a playlist, your device connects to that playlist’s provider and may request program information, artwork and streams. That provider receives the connection information and credentials required for those requests. Its privacy practices are separate from Nexa’s. The app may retrieve artwork and metadata from the sources associated with your catalog.

Providers may process information outside your country, including outside the European Economic Area. Their applicable transfer safeguards and processing terms depend on the service and region. You can ask the controller for information about the providers and safeguards used for your data. Provider information: Firebase privacy, Stripe privacy.

6. Storage, retention and security

Account data remains in the backend while your account is active, unless you remove individual playlists or devices earlier. The account service uses HTTPS and encrypts stored playlist contents. The transport used for streams depends on the playlist provider and the URLs you choose; an HTTP stream is not encrypted in transit.

Deleting your account removes its linked playlists, devices, sessions and license/purchase references from the active account database. A keyed, pseudonymous identifier and the original trial dates are retained to prevent repeated free trials. That trial record contains no name, email address or playlist, but it can recognize the same identity if you register again.

Payment-provider records, issued invoices and invoice-delivery records are managed separately and may be retained for billing obligations, dispute handling and applicable retention periods. Hosting logs and backups are subject to the hosting service’s retention and rotation; account deletion is not an immediate erasure of every backup copy. Contact us for the retention details applicable to your request.

7. Delete your account and data

For the Fire TV edition using Amazon, open the library menu in Nexa, select Delete account and confirm. This deletes your Nexa data, not your Amazon account. You can also request deletion by email without installing the app, using the contact below and identifying that you use Amazon sign-in.

You can request deletion of your Nexa account, including linked Google and Amazon identities, on the website:

  1. Open My account on this website and sign in with the Google or Amazon account used in Nexa.
  2. If an annual subscription is still set to renew, open Manage billing and invoices and cancel its renewal first.
  3. Select Delete account and confirm. This removes the associated data from the active Nexa account database as described above.

If you cannot sign in, or want the associated Firebase identity record removed as well, email nexasystems5@gmail.com with the subject Nexa account deletion. Send the request from the email used for your Nexa account when possible. We may need to verify ownership before acting. Do not send your password, card details or playlist credentials. The Firebase identity is not automatically deleted by the website’s account-deletion button.

Removing the app alone does not delete your server account or cancel a subscription. Local player data can be removed using Android’s app storage controls. You can also request deletion of particular data without deleting the entire account by contacting us.

8. Your privacy rights

Depending on the applicable law, you may request access, correction, erasure, restriction, objection or portability of your personal data, and withdraw consent for processing based on consent. Contact the controller at the email above. Withdrawal does not affect the lawfulness of earlier processing. You may complain to the Spanish Data Protection Agency (AEPD) or your competent data-protection authority.

9. Website sessions and policy changes

The account website uses the necessary __Host-nexa session cookie for sign-in and request protection. Google and Amazon sign-in and Stripe checkout operate under their respective privacy and cookie information. This policy may be updated when the service or its data practices change. The date at the top identifies this version; changes requiring additional notice or consent must be handled separately.