Skip to content

Draft — pending legal review. This text has not yet been reviewed by a lawyer, is not indexed by search engines and may change. Items in [BRACKETS] are placeholders that will be completed once the operating company exists.

Privacy policy

Draft version of November 16, 2026

1. Who is responsible

The controller of the personal data described in this policy is [COMPANY LEGAL NAME], [REGISTERED ADDRESS], company ID [COMPANY ID], VAT ID [VAT ID] (“Tunelay”, “we”).

Tunelay is currently a pre-launch project running a free pilot, and the operating company has not been registered yet. Until it is, the person responsible for the processing is [INTERIM CONTROLLER — name and address of the individual operating the project]. [EU REPRESENTATIVE — only needed if the controller is established outside the EU.]

For every privacy question or request, write to [email protected]. We have not appointed a data protection officer [DPO ASSESSMENT — to be confirmed by counsel].

2. Who this policy covers

This policy covers visitors of tunelay.com (including people who send us a demo, contact or pilot request), users of the Tunelay dashboard at app.tunelay.com (owners, managers and staff of our business customers) and the Tunelay players installed in customer venues.

Tunelay is a service for businesses. When we process personal data on behalf of a business customer — for example data about its staff and the activity of its players — the customer is the controller and we act as its processor under a data processing agreement (see “Data processing (DPA)”). In that case, please contact the business first; we will help it answer you.

3. Website visitors

When you visit tunelay.com, the following data is processed:

  • Access data: our hosting provider Cloudflare processes your IP address, browser details and the requested page in order to deliver the website and protect it from attacks. We do not keep our own access logs for the website.
  • Browser storage: the site keeps your privacy choice, your colour theme and the volume of the sample player in your browser’s local storage. These values stay on your device and are not sent to us. The website sets no cookies (see the cookie notice).
  • Music samples: when sample previews are switched on, your browser loads the list of samples and — only after you press play — the audio file from our server at api.tunelay.com. Our server receives your IP address and browser details as part of these requests; no cookies or identifiers are used.
  • Analytics: no analytics or advertising tool is connected at the moment. If we add one, we will name it here and ask for your consent first.
  • Fonts, images and scripts are served from our own domain. We do not use social media plugins, embedded videos or tracking pixels.

4. Demo, contact and pilot requests

When you send a request through a form on the website, we store: the type of request, your name, email address, company (optional), type of business, number of locations, country, your message (optional), the language of the page, the time you confirmed this policy and its version, the time of your optional consent to product news, your browser’s user-agent string and how often the same request was sent again.

We do not store your IP address with the request. We keep only a pseudonymised fingerprint of it (a one-way hash combined with a secret key) to recognise abuse. To block spam, the form contains a hidden field and a minimum filling time, and short-lived counters limit requests to 5 per minute per IP address and 20 per day per email address; these counters expire within 24 hours.

A notification with your details is emailed to [email protected] so that we can answer you. You do not have to send a request, but without a name and email address we cannot reply.

5. Dashboard users

For people who use the dashboard on behalf of a business customer, we process:

  • Account data: name, email address, password (stored only as a one-way hash), preferred language, role (owner, brand manager, location manager or staff), assigned locations, the dates of invitation and acceptance, and the time of the last sign-in.
  • Invitations: email address, name, role, locations and language of the invited person; an invitation link is valid for 7 days. Password reset links are valid for 60 minutes. Links and sign-in tokens are stored only as hashes.
  • Sign-in: a sign-in token valid for 30 days is kept in your browser’s local storage on app.tunelay.com and removed when you sign out.
  • Audit log: who changed what and when in the dashboard (including the values before and after the change), together with the IP address and browser user-agent of the request.
  • Emails we send: invitations, password resets and, to account owners, alerts about players that need attention (at most one email per player per hour).
  • Business data entered by the customer: company and billing details, locations with address, timezone and opening hours, zones, schedules, playlists and announcements. Announcements are audio files uploaded by the customer and may contain a person’s voice or name.

6. Players and devices

A Tunelay player is an app on an Android tablet or a Windows PC in a customer venue. It has no individual staff log-ins. To pair, operate and support players remotely, we process:

  • Pairing: platform, app version, operating system version, an optional device nickname and the IP address from which the pairing was requested. The pairing code is valid for 10 minutes and stored only as a hash.
  • Device record: device name, location and zone, app and operating system version, last contact time, the name and type of the current audio output (for example the name of a Bluetooth device) and the latest technical status: manufacturer and model, free and used storage, network type, cache and update status, app permissions and kiosk settings, uptime and volume.
  • Status reports (heartbeats), sent regularly: playback state, audio output, app version and the technical status above.
  • Event log: which track or announcement played and when, errors, remote commands (for example volume, test sound or resync, with the dashboard user who sent them) and actions taken on the player screen — pause, resume, volume, mood switch, skip, “Play anyway” and manager PIN unlocks — with the time and the device.
  • Players do not collect location (GPS), microphone or camera data, contacts or advertising identifiers.

7. A note for employers

Player actions are recorded per device, not per person. Combined with a shift roster they could still relate to an identifiable employee. Customers decide whether and how they use play reports and must inform their staff that player actions are logged; we do not use this data to evaluate employees.

8. Purposes and legal bases

We use personal data only for the following purposes and on the following legal bases under Article 6(1) GDPR:

  • Answering requests and arranging a demo or pilot: steps taken at your request before a contract (b), or our legitimate interest in communicating with businesses and their representatives (f).
  • Occasional product news by email: your consent (a), which you can withdraw at any time. No such emails have been sent so far.
  • Providing the service to customers — accounts, players, schedules, announcements, alerts, reports and remote support: performance of the contract with the customer (b) and our legitimate interest in providing it to the customer’s users (f); where we act as processor, the customer’s instructions.
  • Security, abuse prevention, rate limits and the audit log: our legitimate interest in keeping the service and its users safe (f).
  • Legal obligations, for example accounting once paid services exist (c), and establishing or defending legal claims (f).
  • Storing your choices in the browser: strictly necessary for a feature you use; no consent is needed for this [LEGAL BASIS FOR LOCAL STORAGE — counsel to confirm under the Czech Electronic Communications Act].

9. No automated decisions

We do not make decisions based solely on automated processing that have legal or similarly significant effects on you, and we do not create marketing profiles. We do not sell personal data or use it for advertising.

10. Recipients and processors

We use the following service providers, who process data on our behalf under data processing terms:

  • Cloudflare, Inc. (USA) — hosting and delivery of tunelay.com and app.tunelay.com (Cloudflare Pages); processes IP addresses and request data.
  • DigitalOcean, LLC (USA), data centre in Frankfurt, Germany — servers for the API and background jobs, the MySQL database, file storage (Spaces) for audio files and backups.
  • [EMAIL DELIVERY PROVIDER — SMTP service not chosen yet] — sends invitation, password-reset, alert and request-notification emails.
  • [MAILBOX PROVIDER for [email protected]] — receives emails you send us and request notifications.
  • [REMOTE SUPPORT TOOL — for example AnyDesk, only with the customer’s permission for a support session] — screen content may be visible during a session.

11. Other recipients

Users of a customer account with the right role see the data of that account’s users, locations and players. We may share data with professional advisers bound by confidentiality, and with authorities or courts when the law requires it.

12. Transfers outside the EU

Service data is stored in the EU (DigitalOcean, Frankfurt). Cloudflare delivers the websites through a global network, so requests can be processed at locations outside the European Economic Area, including the USA. Both providers are US companies, and their support staff may access data from outside the EEA.

These transfers rely on [TRANSFER SAFEGUARD — the provider’s certification under the EU-US Data Privacy Framework and/or the Standard Contractual Clauses in its data processing terms; to be verified before launch]. You can ask us for a copy of the safeguards.

13. How long we keep data

Retention periods marked “automatic” are enforced by our systems today. For the others, automatic deletion is not yet in place; the proposed periods will be confirmed before launch.

  • Values in your browser: until you clear them; a new privacy-choice version asks you again.
  • Demo, contact and pilot requests: while we handle your enquiry, then at most [LEAD RETENTION PERIOD — proposed 24 months after the last contact]; earlier on request. Records of a consent are kept while the consent is valid and for [CONSENT RECORD PERIOD] afterwards as evidence.
  • Rate-limit counters: automatic, at most 24 hours.
  • Pairing requests, including the requesting IP address: automatic deletion one day after the request expires.
  • Player status reports (heartbeats): automatic deletion after 90 days. The latest technical status of a player is replaced by each new report and deleted with the player.
  • Player event log, alerts and remote commands: kept during the customer relationship for play reports and support, at most [EVENT RETENTION PERIOD — proposed 13 months].
  • Audit log: [AUDIT LOG RETENTION PERIOD — proposed 12 months].
  • Dashboard sign-in tokens: automatic deletion 24 hours after they expire (they are valid for 30 days). Failed background jobs, which can contain email contents: automatic deletion after 30 days. Temporary audio processing files: automatic deletion after 6 hours.
  • Accounts and customer data: for the duration of the customer relationship, then deleted within [DELETION PERIOD AFTER THE END OF THE CONTRACT — proposed 30 days], unless we must keep something for legal obligations or claims.
  • Backups: [BACKUP RETENTION PERIOD — DigitalOcean database backups; to be confirmed]. Emails in the [email protected] mailbox: [MAILBOX RETENTION PERIOD].

14. Security

Connections are encrypted (HTTPS). Passwords, sign-in tokens, device tokens, pairing codes and invitation and reset links are stored only as hashes. Access to customer data is limited by account, role and location, and changes are recorded in the audit log. No system is perfectly secure; if a breach affects you, we will inform you as the law requires.

15. Your rights

Under the GDPR you have the right to access your data, to have it corrected or erased, to restrict its processing, to data portability, and to object to processing based on our legitimate interests — including, at any time, to direct marketing. Where processing is based on consent, you can withdraw it at any time; this does not affect processing before the withdrawal.

To exercise your rights, write to [email protected]. We answer within one month; in complex cases this can be extended by two further months, and we will tell you why. We may ask you to confirm your identity.

16. Complaints

You can lodge a complaint with the Czech data protection authority, the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, www.uoou.gov.cz), or with the supervisory authority in the EU country where you live or work. We would appreciate the chance to resolve your concern first at [email protected].

17. Changes to this policy

The version date is shown at the top of this page. We will inform customers by email about material changes before they take effect. The version you confirmed when sending a request is stored with it.

Questions about this page? Email [email protected].