ONDOOR Data Processing Agreement
Last updated: 11 November 2026
This Data Processing Agreement ("DPA") forms part of the ONDOOR Terms of Service between the Customer (the controller) and mrbooz AB, Roslagsgatan 22, 113 55 Stockholm, Sweden (the processor). It meets the requirements of Article 28 of the GDPR (EU 2016/679). It takes effect when the Customer accepts it in the app, or on first use of the Service, whichever is earlier.
1. Subject and duration
The processor processes personal data on the controller's behalf to provide ONDOOR, for as long as the controller uses the Service and the retrieval period afterwards.
2. Description of processing
| Data subjects | Guests, ticket buyers, pass holders, invitees; the controller's staff, promoters and other users |
|---|---|
| Categories of data | Identity and contact details; party size, guest list, notes and custom fields; check-in times and devices; tickets, passes and orders; invitation responses; approximate location from IP at signup; optionally, a gender estimate from first names |
| Special categories | None intended. The controller must not add them unless lawful and necessary |
| Nature and purpose | Hosting, storage, search, sync to devices, check-in, invitations and confirmations, messaging, ticket sales administration, analytics, AI-assisted import when used, support |
| Retention | As configured by the controller; deleted 30 days after deletion by the controller or after the agreement ends |
3. Processor obligations
The processor shall:
- process personal data only on the controller's documented instructions, including these terms and settings in the Service, unless EU or Member State law requires otherwise, in which case it will tell the controller first unless the law forbids it
- tell the controller if it thinks an instruction breaks data-protection law
- ensure that everyone authorised to process the data is bound by confidentiality
- take the security measures in Annex 1
- assist the controller, as far as possible, with data subjects' requests, including through the export, correction and deletion tools in the Service
- assist with security, breach notification, impact assessments and prior consultation, taking into account the nature of processing and the information available to it
- at the end of the agreement, delete or return personal data at the controller's choice, after the retrieval period, unless law requires storage
- make available the information needed to show compliance, and allow and contribute to audits, as set out in section 6
4. Sub-processors
- The controller gives general authorisation for the sub-processors on the published sub-processor list.
- The processor will give at least 30 days' notice of new or replaced sub-processors by email or in the app. The controller may object on reasonable data-protection grounds; if it can't be resolved, the controller may end the affected service with a prorated refund of prepaid fees.
- The processor imposes data-protection obligations on each sub-processor equivalent to this DPA, and stays responsible for them.
5. International transfers
Personal data is hosted in the EU. Transfers outside the EU/EEA happen only to sub-processors covered by an adequacy decision or the Commission's Standard Contractual Clauses, with supplementary measures where required.
6. Audits
The processor will answer reasonable written security questionnaires and provide its security documentation. On-site audits may be requested once a year with 30 days' notice, during business hours, at the controller's cost, by an auditor bound by confidentiality, and without access to other customers' data. Further audits are allowed after a personal data breach or if a supervisory authority requires them.
7. Personal data breaches
The processor will notify the controller without undue delay, and aim to do so within 48 hours of becoming aware of a breach affecting the controller's data. The notice will say what's known about the nature, likely consequences and measures taken, and will be followed by updates.
8. Liability and precedence
Liability follows the Terms of Service. If this DPA and the Terms conflict on data protection, this DPA prevails.
Annex 1: Technical and organisational measures
- Encryption in transit (TLS) and at rest; hashed passwords; two-factor login available
- Role-based permissions and per-person visibility, enforced on the server. Devices receive only data their user may see
- Door devices: local data limited by role; check-ins shared between nearby devices are encrypted with a per-event key, contain no names or contact details, and the key can be rotated to shut out lost devices
- Least-privilege access for processor staff, with audit logs
- Separate production environment, monitoring and alerting, dependency scanning
- Backups with point-in-time recovery, tested restores, and an expiry of at most 35 days
- Soft delete with 30-day restore, then permanent deletion
- Rate limiting and abuse protection on login and public pages
- Incident response process and breach notification as in section 7