Privacy Policy

1. Data Controller Information

The entity responsible for processing personal and operational data under this Privacy Policy — the data controller — is:

Admixer EU GmbH
Graf-Luckner-Höhe 37, 45239 Essen, Nordrhein-Westfalen, Germany
Managing Director: Oleksii Boltivets
Commercial register: Amtsgericht Essen, HRB 32340 · VAT identification number: DE313546322
Website: https://admixer.net
Support: ask@screenroll.live
Privacy requests: privacy@admixer.net
Data Protection Officer: dpo@admixer.net

Where ScreenRoll processes personal data on a Publisher's behalf — the people a Publisher invites to its account, for instance — it does so as a processor under the Publisher's instructions, as clause 10 of the Terms of Service & Public Offer Agreement sets out. A data processing agreement under Article 28 GDPR is available on request.

2. Scope of Data Collection

We process data collected directly from Publishers and automated telemetry collected from connected ScreenRoll media players:

A. Publisher Account & Registration Information

• First and Last Name of authorized company representative;
• Work Email Address (used for authentication and notifications);
• Company / Organization Name, Business Category, and Country of Operation;
• Encrypted Account Credentials (passwords hashed using BCrypt);
• Billing and Payment Details (for active subscription invoices).

B. Display Screen & Telemetry Data

• Screen Identifiers, Name, Resolution, Location Coordinates, and IP Addresses;
• Operating System Runtime data (Samsung Tizen, Windows, macOS, Android, Linux, or the television's browser at cms.screenroll.live/tv);
• Real-time Screen Status (Online/Offline heartbeats, error logs, player software version);
• Media Play Logs and Proof of Play audit records.

C. Programmatic VAST & Audience Metrics

• Aggregated Opportunity to See (OTS) audience estimation parameters per display venue;
• Real-Time Bidding (RTB) auction transaction logs and VAST ad request timestamps;
• Device telemetry necessary for programmatic impression reconciliation with Demand-Side Platforms (DSPs).

D. Website & Dashboard Analytics

This marketing website uses Google Analytics 4 (property G-6TH4GV96XH), provided by Google Ireland Limited, to understand which pages visitors read and which sources they arrive from. Google Analytics sets first-party cookies and processes a truncated IP address; we do not use it to identify individual visitors, and we do not combine it with your ScreenRoll account data. Google may transfer this data outside the EEA under its Standard Contractual Clauses.

Once you press "Accept" in the cookie banner, the website also uses Microsoft Clarity, provided by Microsoft Corporation, which records how pages are used — clicks, scrolling and pointer movement — as session replays and heatmaps, so we can see where the site is unclear. Clarity sets first-party cookies (_clck, _clsk) and Microsoft's own cookies on its domains (such as MUID), and it masks anything typed into a form. It is not loaded at all before you choose, nor after you press "Decline".

Once you press "Accept", every page of the website also loads the Admixer visit counter (Admixer Tag Manager). Admixer is the advertising platform of Admixer EU GmbH, the operator of ScreenRoll. On each page you open, the counter tells Admixer that the page was visited and identifies your browser with a cookie Admixer sets on its own domain, admixer.net (am-uid, 90 days), so repeat visits from the same browser can be told apart from new ones. Because the cookie belongs to admixer.net, Admixer can recognise the same browser on other websites that use Admixer. We do not combine it with your ScreenRoll account data. Like Clarity, it is not loaded at all before you choose, nor after you press "Decline".

Every page of this website also carries the CreativeRoll site tag. CreativeRoll is Admixer EU GmbH's own ad-measurement service (IAB Europe TCF vendor 511), and we use it only to confirm that a click on one of ScreenRoll's own ads reached this site. When a page is opened from such an ad, its address carries a short click id (crc); the tag sends that id, the site's address without its path, and the campaign's UTM tags to CreativeRoll. It sends nothing on a page you did not reach from our ad, sets no cookie and does not tell one visitor from another.

You can prevent this collection by pressing "Decline" in the banner, by installing the Google Analytics opt-out browser add-on, or by using your browser's tracking-protection settings.

The ScreenRoll dashboard at cms.screenroll.live uses a separate Google Analytics 4 property (G-ER3ZWKQBS4) and Microsoft Clarity to measure how the application is used and where it is hard to use. They are part of the service: using the dashboard means accepting the Public Offer Agreement, which includes this policy (clause 12.4), and nobody is asked a second time. Clarity starts only once you are signed in to an account that has accepted the agreement. Its recordings show the dashboard as it appears on screen, so they can include the names, figures and settings shown there; anything typed into a form field, passwords included, is always masked, and only ScreenRoll staff can view the recordings. Neither is loaded on player routes — the pages that run on your displays — so your screens are never counted as visitors and screen access links are never transmitted to Google or Microsoft. We tell Clarity not to share anything it records with Microsoft Advertising, on the website or in the dashboard.

3. Legal Basis for Processing

We process data under the following GDPR legal bases:

• Contractual Performance (Art. 6(1)(b) GDPR): To provision your CMS account, deploy schedules, and execute programmatic ad auctions.
• Legitimate Interests (Art. 6(1)(f) GDPR): To monitor network security, prevent fraudulent ad impressions, and measure aggregate website usage.
• Legal Obligations (Art. 6(1)(c) GDPR): For financial record-keeping, tax invoices, and accounting audits.

4. Third-Party Sharing & Programmatic Partners

ScreenRoll integrates with Admixer's global ad exchange and trusted DSP partners for programmatic ad monetization. In programmatic auctions, non-personal, aggregated screen venue parameters (such as screen location, size, and OTS multipliers) are transmitted to demand partners to fulfill real-time bids. Personal account data is never exposed to DSP buyers.

5. Data Retention & Security

We enforce enterprise TLS 1.3 encryption in transit and AES-256 encryption at rest. Proof of Play logs and transaction statements are retained for 7 years to satisfy audit requirements. Active Publisher account telemetry is maintained for the duration of the subscription.

6. Publisher & User Rights

Under GDPR and applicable privacy regulations, users have the right to access, rectify, export, or request deletion of their personal data. To exercise these rights, submit a written request to privacy@admixer.net.

7. Cookies, Local Storage & Analytics

The marketing site (screenroll.live) sets no analytics cookies without your consent. Google Analytics 4 runs in Consent Mode: until you press "Accept" in the banner, it stores nothing on your device and receives only cookieless, aggregated pings. Microsoft Clarity is not loaded at all until you press "Accept", and never after "Decline". Neither is the Admixer visit counter (see §2D), so its cookie (am-uid) is not set before you accept. The CreativeRoll site tag (see §2D) sets no cookie: it only confirms that a click on our own ad reached the site, from the click id in the page's address. Your choice itself is kept in your browser's local storage (sr-consent) — that is strictly necessary and carries no personal data. You can change your mind by clearing site data in your browser.

The CMS (cms.screenroll.live) uses no advertising trackers. It measures its own use with Google Analytics 4 and Microsoft Clarity as part of the service (see §2D): their cookies are set for everyone who uses the dashboard, Clarity's only once the account has accepted the Public Offer Agreement, and Clarity's recordings mask anything typed into a form field. Neither runs on the pages your displays play. Beyond those cookies, the CMS keeps only what a signed-in session strictly requires, in local storage: your session token, a device-trust token for two-step verification (48-hour lifetime), and a cached copy of your own profile. None of it is readable by third parties.

8. Account Security Data

To protect accounts that control physical screens in public places, we process, on the basis of our legitimate interest in security and fraud prevention (Art. 6(1)(f) GDPR):

• Sign-in verification: one-time codes sent to your email, stored only as cryptographic hashes and expired within minutes to hours; device-trust tokens (hashed, 48-hour lifetime); the time, IP address, browser and platform of sign-in attempts — shown back to you in the code email so you can recognise a sign-in that is not yours.
• Registration integrity: when an account is created through the public form we record the request's IP address, browser identification, language preference, referring page and reported timezone. This exists solely to distinguish genuine registrations from automated abuse, is visible only to platform administrators, and is never used for marketing or profiling.
• Activity log: administrative actions inside the CMS (who changed what, when, from which IP) — the audit trail your own organisation is entitled to.

9. Processors & Sub-processors

We share personal data only with processors needed to run the service, under GDPR Art. 28 terms:

• Microsoft Azure (European Union regions) — hosting, databases and media storage.
• Resend — transactional email delivery: sign-in codes, password resets, invitations, invoices.
• Google Analytics 4 — statistics, with IP truncation: on this marketing website only with your consent, and in the dashboard as part of the service (§2D).
• Microsoft Clarity (Microsoft Corporation) — session replays and heatmaps: on this marketing website only with your consent, and in the dashboard as part of the service, recording the dashboard as it appears with form fields masked (§2D). Nothing it records is shared with Microsoft Advertising. Microsoft may process this data outside the EEA under the EU–US Data Privacy Framework. See the Microsoft Privacy Statement.
• OpenStreetMap Foundation (map tiles and Nominatim geocoding) — when a publisher opens the map view or searches an address inside the dashboard, their browser requests map tiles and geocoding directly from OpenStreetMap's servers, which therefore see the browser's IP address and the searched text. Our own servers also use Nominatim to complete the addresses of locations; that request carries the address, not a person. See the OSMF privacy policy.
• Open-Meteo — weather widgets. Our servers request the forecast for the place a publisher chose, or for the coordinates of the location a screen stands in, and pass it to the screen with its schedule. The screen itself contacts nobody; no account, key, identifier or device address of yours is sent. See the Open-Meteo terms.
• News sites — news widgets. Our servers read the feed a publisher chose and pass the stories to the screen. The pictures in those stories stay on the news site's own servers: a screen showing a picture fetches it from there, so that site sees the screen's IP address, as any website does. A publisher can switch pictures off.

Payments. Invoices are paid by bank transfer, and we hold the invoicing details a Publisher gives us for that purpose. No card payments are taken at present and no card details pass through ScreenRoll. Should card payment be introduced, it would be handled by a payment provider in that provider's own interface, and this policy updated first.

Programmatic advertising partners receive what an auction needs — the screen's venue type, audience estimate, size and location — and never the personal data of a Publisher's users; section 4 describes this.

10. Retention

Sign-in codes: minutes to 24 hours; device-trust tokens: 48 hours; both hashed. Password-reset links: 1 hour, single use. Registration-integrity metadata and activity logs: for the life of the account, then deleted with it. Billing records and invoices: as long as tax law requires. Proof-of-play and payout statements: 7 years, for audit.

When an agreement ends, the Publisher may export its media and reporting data for 30 days, as clause 8.4 of the Terms provides; after that the account and its content may be deleted or anonymised, subject to the statutory periods above.

11. Policy Updates

Admixer reserves the right to update this Privacy Policy. Substantial changes will be communicated via email or dashboard notification 14 days prior to taking effect.