1. Introduction

AdMatrix FZ-LLC (“ScreenLeads”, “we”, “us”, “our”) has designed the ScreenLeads Player App as a business‑to‑business (B2B) software product for managing and playing digital content on Android and Android TV screens.

The App integrates with the ScreenLeads platform and allows screens linked to a business account to play multimedia content and campaigns configured from the ScreenLeads web Dashboard.

This Privacy Policy explains how we collect, use, and protect information generated by devices running our App. The App is not intended for consumer‑facing (B2C) use, but for companies and administrators who use the ScreenLeads platform to manage their screens.

2. Scope

This Privacy Policy applies exclusively to the ScreenLeads Player App distributed through the Google Play Store and running on Android devices, Android TV, or other compatible systems configured as display screens.

It does not govern processing carried out by the ScreenLeads web Dashboard, other admin applications, the Customer’s external integrations (for example CRM, automation tools or messaging systems), or third‑party services linked from the ScreenLeads platform. Separate privacy policies may apply to those services and must be reviewed independently.

3. Definitions

For the purposes of this Policy:

• “Customer”: The company, organization, or professional that contracts ScreenLeads and manages the devices where the App is installed.
• “Administrator”: Person authorized by the Customer to configure screens, credentials, and content campaigns.
• “Device”: Screen, TV, tablet or other hardware where ScreenLeads Player is installed and executed.
• “Device data”: Technical information generated by the Device, such as IP address, hardware model, OS version, and error logs.
• “Authentication data”: Information required to log in with the Customer’s ScreenLeads account (username, password, session tokens).
• “ScreenLeads API”: Backend services accessible via api.pre.screenleads.com and related endpoints.

4. ScreenLeads’ role and legal bases

In most cases, ScreenLeads acts as a Data Processor for data managed by the Customer, who is the Data Controller for their own end users, to the extent data is processed in the context of campaigns and content configured by the Customer.

To the extent ScreenLeads determines how basic Device telemetry and App diagnostics are processed (for example logs and performance data), ScreenLeads may act as Data Controller for that technical data.

Where the GDPR or similar laws apply, relevant legal bases include, among others, the performance of a contract with the Customer and legitimate interests in maintaining platform security, availability, and performance.

5. Data we collect

Given the enterprise‑only nature of the App (Kiosk/Display mode), we limit data collection strictly to what is necessary for authentication, synchronization, and technical operation of the screens.

5.1. Authentication data

We collect and process the following data when an Administrator logs in to the App:

• Username or email associated with the Customer’s ScreenLeads account.
• Password or equivalent credentials entered on the screen.
• Access and refresh tokens (for example JWTs) generated by our servers to keep the Device session active.

5.2. Device identifiers

The App may collect:

• Public or private IP address assigned by the network.
• MAC address or other network interface identifiers.
• Android ID or other system identifiers generated by Android.
• Device hardware model and manufacturer.
• Operating system version and relevant firmware versions.

5.3. Diagnostic and telemetry data

To ensure service stability, the App may send to our servers:

• Error logs (crash logs) and failure traces.
• Connectivity status (online/offline).
• Confirmations that specific content has been downloaded or played successfully.
• Device health signals such as response times and success contacting the API.

5.4. Local screen configuration

The App may store and synchronize:

• Device time zone and regional settings.
• Auto‑start and reboot behavior.
• Volume, brightness and other playback preferences defined by the Customer.

6. How we use the information

We use the information collected exclusively to ensure continuous operation of the B2B service and to fulfil our contractual commitments to Customers.

6.1. Content synchronization

We use authentication and Device data to:

• Connect the screen to the ScreenLeads cloud infrastructure.
• Download and dynamically update videos, ads, and campaigns configured in the Dashboard.
• Ensure each screen displays only the content associated with the correct account.

6.2. Technical maintenance and support

Diagnostic and telemetry data allow us to:

• Monitor screen uptime.
• Detect and resolve failures remotely.
• Analyze recurring errors and improve future versions of the App.

6.3. Security and abuse prevention

Technical Device information and authentication data are used to:

• Validate the identity of the Device and the linked ScreenLeads account.
• Prevent unauthorized access to the Customer’s screen network.
• Verify that the App is used in accordance with our service terms and license.

7. Android device permissions

To operate autonomously as a digital sales agent, the App requires certain Android system permissions. These permissions are requested during installation or at first run and must be granted by the Administrator.

7.1. Internet and network status access

Permissions: INTERNET, ACCESS_NETWORK_STATE

Purpose:

• Receive commands from the ScreenLeads API and Dashboard.
• Download updated multimedia content and synchronize configurations.
• Verify screen connectivity for support and monitoring.

7.2. Local storage

Permissions: READ_EXTERNAL_STORAGE, WRITE_EXTERNAL_STORAGE (or modern equivalents).

Purpose:

• Cache videos and creatives to avoid playback interruptions during temporary connectivity loss.
• Optimize playback performance on devices with limited resources.

7.3. Auto‑start and power management

Permissions: RECEIVE_BOOT_COMPLETED, WAKE_LOCK

Purpose:

• Allow the App to start automatically when the Device is powered on.
• Keep the screen awake during business hours.

The App does not request permissions such as camera, microphone, precise location, or contacts, unless future versions require them. In that case, we will update this Policy and show prominent in‑App notices in accordance with Google Play policies.

8. Cookies and similar technologies

The ScreenLeads Player App does not use traditional browser cookies, because it runs as a native application. However, local identifiers and internal storage may be used to store configuration, manage content caches, and maintain minimal state information between restarts.

These mechanisms are used solely to ensure proper operation of the App and not for advertising tracking of end users.

9. Sharing data with third parties

ScreenLeads acts as Data Processor for most of the data generated by the App and does not sell or rent Device information or credentials to third parties for advertising purposes.

Data may only be shared in the following cases:

• Cloud infrastructure providers: Hosting and processing required to run the API, store logs, and serve content.
• Monitoring and logging services: Performance and error‑logging tools limited to technical data.
• Legal requirements: Disclosure to competent authorities when required by law, court order, or valid request.

10. International data transfers

AdMatrix FZ-LLC is headquartered in the United Arab Emirates and may use providers located in different jurisdictions. In case of international data transfers, we take reasonable measures to ensure an adequate level of protection, in line with applicable data protection laws.

Where GDPR or similar laws apply, mechanisms such as standard contractual clauses and other safeguards may be implemented.

11. Data retention

We retain information associated with the ScreenLeads Player App only for as long as necessary to maintain the service, resolve technical issues, and comply with legal obligations.

• Error logs and telemetry data are kept for limited periods and then anonymized or deleted.
• Technical Device identifiers are retained while the screen is registered and active in the Customer’s account.
• Authentication credentials are processed transiently and replaced by short‑lived encrypted session tokens.

12. Security

We apply enterprise‑grade security standards to protect our infrastructure and the information processed. All communication between the App and our servers is encrypted via secure protocols, and access tokens are generated with limited validity.

Internal access to data is restricted to personnel and systems that need it, and we use access control, auditing, and monitoring to prevent unauthorized access and detect security incidents.

13. Rights of customers and administrators

Depending on applicable law, Customers and, where relevant, Administrators acting as individuals may exercise rights over personal data relating to them, such as access, rectification, erasure, restriction, objection, and portability.

Most of these rights are exercised vis‑à‑vis the Customer as Data Controller. ScreenLeads will cooperate with the Customer to help fulfil rights requests that involve data processed through the App.

14. Children

The ScreenLeads Player App is not directed at children and is not used for end consumers to create personal accounts. It is designed to run on screens controlled by businesses and Administrators.

15. Third‑party links and services

The App may contact ScreenLeads backend services to download content and, indirectly, integrate with other Customer systems (for example CRM or automation tools) configured from the Dashboard.

This Policy does not cover processing by those external services. Customers should review the privacy policies of each provider integrated into their ecosystem.

16. Changes to this Privacy Policy

We may update this Privacy Policy when we add new functionalities, change our processing practices, or need to adapt to new regulations or Google Play requirements.

We will update the “Last updated” date and, where reasonable, notify Customers and Administrators via appropriate channels. Continued use of the App after publication of an updated version constitutes acceptance of those changes.

17. Contact

For legal, technical, or privacy‑related questions about data processed through ScreenLeads Player, you can contact us at:

• Legal entity: AdMatrix FZ-LLC
• Physical address: Compass Building, Al Hulaila Industrial Zone‑FZ, Ras Al Khaimah, 10000, United Arab Emirates.
• Privacy email: privacy@screenleads.com
• General email: david@screenleads.com

Please specify in the subject line that your inquiry refers to the ScreenLeads Player App on Google Play so we can route it quickly to the appropriate team.