The ScreenX Player app by Anantavya Tech Works is a digital signage app. It turns a TV, screen or media box into a display that shows the content a business has published from its ScreenX Signage account. The app has no sign-in, no advertising and no analytics or tracking SDKs. It collects only the technical data needed to pair a screen, deliver content to it and report whether it is working. We never sell personal information.
1Who we are
This policy is published by Anantavya Tech Works, India, the developer of the ScreenX Player app as listed on Google Play and the provider of the ScreenX Signage service (screenxsignage.com). In this policy "we", "us" and "our" mean Anantavya Tech Works. It covers:
- the ScreenX Player app for Android and Android TV, published on Google Play by Anantavya Tech Works under the package name
com.screenxsignage.player(the “app”), and - the ScreenX Signage web console and API at screenxsignage.com (including api.screenxsignage.com) that the app talks to (the “service”).
We handle personal information in line with India’s Digital Personal Data Protection Act, 2023 and the Information Technology Act, 2000 and, where they apply to our customers, other privacy laws such as the GDPR, the Australian Privacy Act 1988 and the New Zealand Privacy Act 2020.
2How the app works
The app is installed on a screen, not on a person’s phone. Someone with a ScreenX Signage account creates a “screen” in the web console and receives a short pairing code. Typing that code into the app links the device to that account. From then on the app downloads the account’s published playlists, designs and schedules and plays them. The app only ever connects outward to our servers; nothing connects into the device or the network it is on.
3Information the app collects
The app does not ask for a name, email address or any sign-in. The data it sends to our servers is technical and is tied to the paired screen, which belongs to a business account.
| Data | What it is | Why we collect it |
|---|---|---|
| Pairing code | The one-time code typed into the app. | To link the device to the correct account. The code expires and is single-use. |
| Device identifier | An identifier derived from the device’s Android ID, prefixed android-. | To tell one paired device from another in the console and to help with support. It is not used for advertising or cross-app tracking. |
| Device and app details | App version, screen resolution, the device’s time zone, free storage space, time since the app started, and short error messages. | To lay out content for the panel’s real size, run schedules at local time, warn the account when storage is low and show whether the screen is healthy. |
| Connection data | The IP address and time of each request, as every web server records. | Security, rate limiting and troubleshooting. Kept in server logs. |
| Playback events | Which content item played, when, for how long and whether it finished. | So the account can see proof of play. These describe content, not people. |
| Screenshots of the display | A picture of what the screen is currently showing, taken only when someone in the account requests it from the console. | Remote support: “what is this screen showing right now?” The picture is of the signage content. Only the newest 10 per screen are kept. |
| Device token | A random credential issued at pairing and stored on the device. | To authenticate the device on every request. Our servers store only a hash of it. |
What the app does not collect
- No location data, contacts, calendar, call logs, SMS, photos, files outside the app, camera or microphone.
- No Advertising ID, and no advertising, analytics, crash-reporting or tracking SDKs from third parties.
- No account credentials: the app never asks for a username or password.
4Information stored on the device
The app keeps on the device: the published content files (images, video, audio, designs) so playback continues offline, the device token, the address of the server it is paired with, its own settings (orientation, volume, menu password if one is set) and a short queue of playback events waiting to be sent. Content files are verified against a checksum before they are played. Unpairing the device from the app’s menu, or from the console, deletes the token; uninstalling the app removes everything it stored.
5How we use the information
- To pair devices, deliver published content to them and keep it up to date.
- To show account holders whether each screen is online, what it is playing and when it last checked in, and to send them alerts when a screen goes offline or runs low on storage.
- To provide playback reports.
- To keep the service secure, prevent abuse and diagnose faults.
- To offer and install app updates that the account chooses to apply from the console.
We do not use the data for advertising, profiling or to train machine-learning models, and we do not sell it.
7Android permissions the app uses
| Permission | Why the app needs it |
|---|---|
INTERNET | To reach the ScreenX Signage servers and download content. |
RECEIVE_BOOT_COMPLETED | To start the player automatically when the screen is switched on, if AutoStart is enabled in the app’s menu. |
WAKE_LOCK | To keep the display awake while content plays. |
SYSTEM_ALERT_WINDOW (display over other apps) | Only so that AutoStart can bring the player to the front on Android 10 and later. It is optional and requested through Android’s own settings page. |
REQUEST_INSTALL_PACKAGES, REQUEST_DELETE_PACKAGES | To install an update of the app itself when an account triggers one from the console. Nothing else is installed or removed. Installs from Google Play are updated by Play instead. |
None of these permissions give the app access to personal files, location, contacts, camera or microphone.
8Retention and deletion
- Screen records, device details and the latest status are kept while the screen exists in the account.
- Playback events are kept for a limited reporting period and then removed automatically.
- Only the 10 most recent screenshots per screen are kept; older ones are deleted as new ones arrive.
- Server access logs are kept for a limited period for security.
- Deleting a screen in the console revokes its device token immediately and removes its screenshots. Deleting an account removes its screens, content, members and integration tokens.
9Security
All traffic between the app and our servers uses HTTPS. Device tokens are random, stored only as hashes, rotated periodically and revoked at once on unpairing. Every content file is checked against its expected size and SHA-256 hash before it is shown. Each customer’s data is isolated from every other customer’s at the database level. Access to the console can be protected with two-factor authentication and IP allow-lists.
10Children
The app and service are for businesses and are not directed at children. We do not knowingly collect personal information from anyone under 16. If you believe a child has provided us with personal information, please contact us and we will delete it.
11Your rights
You may ask us for access to, correction of, or erasure of personal information we hold about you, and you may withdraw consent or raise a grievance with us; we will respond within a reasonable time. Because screen data belongs to the business account that paired the device, requests about a particular screen are usually handled through that business; we will help them respond. If you are in India and not satisfied with our response, you may approach the Data Protection Board of India. If you are in the EU, UK, Australia or New Zealand, you have the corresponding rights under your local law.
12Where data is stored
Our servers are hosted with reputable cloud providers. Where data is stored or processed outside India, we take reasonable steps to ensure it is protected to a standard comparable to Indian law.
13Changes to this policy
We may update this policy as the app and service change. The effective date at the top shows the latest revision. Material changes will be announced in the console or on our website.
14Contact
Questions or requests about this policy or your data:
© 2026 Anantavya Tech Works. ScreenX Player (com.screenxsignage.player) is developed and operated by Anantavya Tech Works, India.