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.
Data processing agreement — outline
Draft version of November 16, 2026
1. Status of this outline
This page outlines the data processing agreement (DPA) that Tunelay will conclude with each business customer under Article 28 GDPR. It is not a signed agreement. The final DPA will be part of the contract with the customer [DPA SIGNATURE MECHANISM].
2. Roles
The customer is the controller, and Tunelay its processor, for personal data processed in the customer’s account on the customer’s behalf: the accounts of its owners, managers and staff, the activity of its players (events, staff actions and play reports), device data, announcements it uploads and data about its locations.
Tunelay is an independent controller for: its website and the requests sent through it, the contractual relationship with the customer’s contact persons, account security and abuse prevention (audit log, rate limits, sign-in security), billing once paid services exist, legal obligations and claims, and aggregated statistics that do not identify anyone. [ROLE SPLIT — proposed; to be confirmed by counsel.]
3. Subject matter and duration
Processing is limited to providing the Tunelay service under the customer’s terms: background music playback, schedules, announcements, player management, alerts, reports and remote support. It lasts for the duration of the contract and ends with deletion of the data as described below.
4. Data subjects and categories of data
- Data subjects: the customer’s owners, managers and staff who use the dashboard; staff who operate the players in the venues; people whose voice or name appears in announcements.
- Identity and contact data: name, email address, language.
- Account data: role, assigned locations, invitation and sign-in times.
- Security data: audit log with changes, IP address and browser user-agent.
- Device and event data: player status and technical details, audio output names, plays, errors, remote commands and actions on the player screen with timestamps.
- Content: announcement audio files and texts entered by the customer.
- No special categories of personal data are expected; the customer must not upload them.
5. Tunelay’s obligations as processor
Tunelay will:
- process personal data only on the customer’s documented instructions — the contract and the customer’s settings in the dashboard — and inform the customer if an instruction appears to infringe data protection law;
- ensure that everyone with access is bound by confidentiality;
- apply the security measures described below and keep them appropriate to the risk;
- use sub-processors only under the general authorisation below, inform the customer [SUB-PROCESSOR NOTICE PERIOD] in advance of any change and let it object;
- help the customer respond to data subject requests and meet its obligations on security, breach notification and data protection impact assessments;
- notify the customer of a personal data breach without undue delay [BREACH NOTICE DEADLINE — for example within 48 hours of becoming aware];
- delete or return the personal data at the end of the contract, at the customer’s choice, within [DELETION PERIOD — proposed 30 days], unless the law requires storage;
- make available the information needed to demonstrate compliance and allow audits [AUDIT TERMS — frequency, notice and costs].
6. Sub-processors
- Cloudflare, Inc. (USA) — hosting and delivery of the dashboard (app.tunelay.com).
- DigitalOcean, LLC (USA), data centre in Frankfurt, Germany — application servers, database, file storage and backups.
- [EMAIL DELIVERY PROVIDER — not chosen yet] — invitation, password-reset and alert emails.
- [REMOTE SUPPORT TOOL — for example AnyDesk, only for support sessions the customer starts or permits].
7. Security measures in place today
- Encrypted connections (HTTPS) between players, dashboard and API.
- Passwords hashed with bcrypt; sign-in tokens, device tokens, pairing codes and invitation and reset links stored only as hashes; device access can be revoked at any time.
- Separation of customer accounts and access limited by role and location.
- Audit log of changes in the dashboard; rate limits on sign-in, pairing and public forms.
- Automatic deletion of player status reports after 90 days and of pairing requests one day after expiry.
- Hosting in an EU data centre (Frankfurt).
- [TO BE DOCUMENTED — encryption at rest, backup and restore, staff access management, logging and incident response.]
8. Transfers, liability and open points
International transfers are handled as described in the privacy policy [TRANSFER SAFEGUARD]. Liability, audit costs, governing law [GOVERNING LAW] and the order of precedence between the DPA and the terms will be settled in the final agreement.
Questions about this page? Email [email protected].