Astro Player
Português

Privacy Policy

Version of October 14, 2026.

1. Who we are

Astro Player is a personal media player for TVs, TV boxes, phones and other devices. It plays the content that users access themselves with the access code they received from a provider. Astro Player does not sell, host or provide that content; the only videos it hosts are the app's own: those of the interface and those of the demo account (section 7).

Contact for any privacy matter: [email protected].

2. Summary

3. What the app stores on your device

The app stores in its own storage on your device: the access code, the username and password for the content server, favorites, recently viewed items, playback positions, a temporary copy of the content list and the device identifier. The password, favorites, recently viewed items and playback positions are not sent to our system (except the demo account password, section 7); the access code, the identifier and the username are also sent to it, as described in section 4. Uninstalling the app or clearing its data deletes all of it from the device.

In version 1.2.2 for phones, tablets and TVs (from Google Play or the file from the website), the app asks Android not to include this data in automatic backup or in a transfer to a new device. In older versions, if Android automatic backup is turned on for the device, Android itself may include this data, including the content server username and password, in the backup stored in your Google account or in a transfer to a new device. That copy is an Android feature, does not go through Astro Player and is not deleted when you uninstall the app; it is managed in the device's backup settings.

4. What the app sends to the Astro Player system

When you sign in, the app sends to our system:

After that, while the app is open, even in the background, it runs a short check every 90 seconds and a query every time the app opens and every 15 minutes. These send the access code, the identifier, the device type, the app version and the installation source and, in the 90-second check, also the access expiry date; if the data sent at sign-in did not arrive, it is sent again in the query. Using the access code, the app also fetches the content server addresses from our system. To look for the app's internal updates, the access code and the app version are also sent to our update server. On Roku, the app sends only the access code, the identifier and the device type (and, for the demo account, also the username and password, section 7).

Approximate location: the network that protects our system (Cloudflare) tells us the state or region the connection came from, derived from the IP address. We keep only the state or region. The Astro Player system does not store your IP address.

5. Who sees this data

The provider that issued your access code, and the accounts that manage that provider in the Astro Player dashboard, can see for each device: the identifier, username, type, model, operating system and app versions, access expiry date, whether it is connected, last connection, activation date, state or region, notes written by the provider and, if applicable, a block. They also see daily usage counts by state and device type, which do not identify anyone.

6. Services from other companies inside the app

Some components from other companies are built into the app. Below is what each one does and in which versions.

6.1 Google Analytics (older versions only)

Versions 1.0.0, 1.0.1 and 1.1.0 of the Android app include Google Analytics, a Google service, to measure usage statistically (for example, how many times the app was opened and on which types of device), and so do the internal app updates delivered to them before October 7, 2026. Google receives its own random Analytics identifier, technical device information (such as language and screen size), a record of each time the app opens and the approximate location derived from the IP address, and processes this data under the Google Privacy Policy, which explains it in how Google uses information from sites or apps that use its services.

Version 1.2.1 (published on October 10, 2026) and later versions do not use Google Analytics. The internal update sent to older versions since October 7, 2026 does not use it either; it reaches the device when the app is opened with an active access code. An older version keeps sending data to Google Analytics until it receives that update or is replaced by version 1.2.1 or later.

6.2 Capgo update component (sending turned off in version 1.2.2)

Versions 1.0.0 to 1.2.1 of the Android app include a component, made by the company Capgo (open source), that installs the app's internal updates and by default sends technical operation logs to Capgo's servers: a random identifier created by the component itself; the app's name; the versions of the app, the Android system and the internal update; the device model and the version of the app's built-in browser; the store the app was installed from; whether the device is an emulator; when the app opens, loads its screen, goes to the background and comes back; the steps of each update; and the app's errors and unexpected shutdowns, with memory usage data and the error messages from the system and the app screen. As with any internet connection, Capgo also receives the device's IP address. This happens even though we do not use any Capgo service: Astro Player has its own update server. Anyone still using one of these versions keeps sending this data until they update the app.

The component was not designed to send your username or password. However, on devices that cannot use the preview's video engine, a failure to load the preview may cause the error report to include the video's address, which the app builds with your content server username and password.

In version 1.2.2, sending to Capgo is turned off: the component still installs the internal updates but sends nothing to Capgo's servers. The Amazon Appstore version (Fire TV) does not include this component.

6.3 Google Cast (older versions only)

Versions 1.0.0 to 1.2.1 of the Android app include Google Cast, from Google, to cast video to a TV or a Chromecast. In those versions, Cast starts working when the player is opened and, while the app stays open, may look for compatible devices on your local network, for example when the app returns to the foreground or when you tap the cast button. According to Google, Cast logs technical information about this use (device discovery, the start and end of casting sessions, and technical data about the device and the app) to measure Cast usage and improve how it works, and sends part of it to Google's servers, encrypted and without identifiers that lead to you; Google says it does not share this data with other companies, and neither you nor we can turn this logging off. Google describes this data on the page Cast SDK Google Play Data Safety Section.

Version 1.2.2 does not include Google Cast, and neither does the Amazon Appstore version (Fire TV). Anyone still using an older version keeps it until they update the app.

In older versions, when you cast, the app hands the video's title and address to the TV device, through Google's default receiver. That address is built by the app and always contains your content server username and password; the TV uses the address to fetch the video directly from the server.

7. The content server you use

Your username, password and playback requests go directly from your device to the content server chosen by your provider. That server does not belong to Astro Player and follows the rules of whoever operates it. The exception is the Astro Player demo account, made to show the app (for example, during store review): it uses a username and password created by us and our own server, which only delivers the app's demo material (videos, covers and the list); in that case, that username, that password and the playback requests are sent to our system.

Some content servers use an unencrypted connection (http). In that case, your username, password and playback requests travel unencrypted between your device and that server; this depends on whoever operates the server. Covers and images in the list are also loaded directly from the addresses the content server provides, which may be other websites.

8. What we do not collect

Through the app, we do not collect names, email addresses, phone numbers, ID numbers, payment data, GPS location, contacts, photos, personal files, microphone or camera. The username in section 4 is the one your provider created for you on the content server.

On Android, the app requests the permissions to access the internet and check the network state, used to play videos, talk to our system and know whether there is a connection. The phone, tablet and TV versions (from Google Play or the file from the website) also request the permissions to run a foreground service, keep the device awake and start when the device boots. The app does not use these directly: they are declared by Android's task scheduler (WorkManager), which the update component uses to download the internal updates and resume them after the device restarts; in older versions, Google Cast also declares the foreground service permission. The Amazon Appstore version (Fire TV) requests only the first two. All of them are granted by Android at installation, without asking, and none of them gives access to contacts, photos, files, microphone, camera or location.

9. How we use the data

The legal bases are the performance of the service you request and our legitimate interest in keeping the service running securely, under the Brazilian General Data Protection Law (Law No. 13,709/2018).

10. Who we share data with

We do not sell or rent data. It only reaches:

Because the server is outside Brazil, the data in section 4 is transferred abroad, with the protections described in section 12.

11. How long we keep data

Each device record is kept while the device is linked to the access code. Daily counts are aggregated and do not identify devices. To delete your device record from our system, write to [email protected] with your access code and username. We reply within 15 days.

12. Security

All communication between the app and our system is encrypted (HTTPS). The dashboard requires a username and password, and each provider sees only the devices in their own network.

13. Your rights

You can ask us to confirm whether we process data about your device, and to access, correct or delete it, or to tell you who it was shared with, by writing to [email protected].

14. Children

Astro Player is not directed at children and does not knowingly collect data from children.

15. Changes to this policy

When this policy changes, the new version will be published on this page with an updated date. If the Portuguese and English versions differ, the Portuguese version prevails.

What changed in the version of October 14, 2026: section 2 explains where your password goes; section 3 makes clear what the app stores on the device and what is also sent to our system and covers Android automatic backup; section 4 now mentions the installation source, the update server and that sending continues while the app is in the background; section 6 now describes, version by version, the services from other companies built into the app (Google Analytics and Google Cast, which are not in version 1.2.2, and the Capgo update component, whose sending was turned off in version 1.2.2); section 7 explains the demo account and the unencrypted connection used by some content servers; section 8 lists the app's permissions on Android and explains the username; and section 10 includes the content server, the cover websites, Google Cast and Capgo; section 1 explains the only videos the app hosts.