Early access. ArrivePad is live and working, and you're welcome to sign up and use it for real. It's an early release, so expect the odd rough edge. The iPad and Android apps aren't available yet: please use the web browser version instead, which runs on any tablet. Questions: [email protected].
Skip to content
ArrivePad
Features Privacy Tour Pricing Contact
Menu
Features Privacy Tour Pricing Contact Log in
Log in Start free
Terms of Service Privacy Policy Data Processing Agreement Fair Usage Policy Cookies Sub-processors Security

Data Processing Agreement

Version 2026-09-30 · Zac Simmonds, trading as ArrivePad

Early access: we may update this document before general launch, and we'll email account owners about any material change.

This Data Processing Agreement ("DPA") forms part of the ArrivePad Terms of Service between the customer organisation (the controller) and Zac Simmonds, trading as ArrivePad (the processor). It meets the requirements of Article 28 of the UK GDPR. Acceptance is recorded, with its version and time, when the organisation signs up.

1. Details of the processing

Subject matterProviding visitor sign-in software
DurationFor as long as the customer's account exists, then deletion as in §9
Nature and purposeRecording visitor sign-in and sign-out; showing who is on site; producing evacuation lists; recording deliveries and notifying recipients; exports and archives the controller asks for
Data subjectsVisitors to the controller's sites; meeting and delivery recipients; staff users
Personal dataName; optionally company, person visited, email, phone, vehicle registration and a photo; sign-in and sign-out times; site and kiosk used; answers to any questions the controller adds to its sign-in form; which documents and checklists a visitor accepted. Invited visitors: name, email, expected time, the host's message and any note the visitor leaves about assistance they need. People's names, emails, mobile numbers and meeting/delivery preferences. Delivery recipient, site and recorded time.
Special category dataNone intended. Photos are not processed as biometric data — no face recognition or matching. A visitor's free-text note about assistance they need, or an answer to a question the controller chooses to ask, may reveal health or other special category information; the controller decides whether to ask such questions and is responsible for its lawful basis for doing so.

2. Instructions

We process personal data only on the controller's documented instructions: these terms, this DPA, and the controller's settings and actions in the app (such as its retention period and exports). We tell the controller if we believe an instruction breaks data protection law.

3. Confidentiality

Everyone we authorise to process the data is bound by confidentiality. Our staff do not access customer visitor records except where necessary to provide support the controller asks for, or where required by law.

4. Security

We apply appropriate technical and organisational measures (Article 32), described on our Security page, including encryption in transit, strict separation between organisations, access controls, two-factor sign-in for admins, audit logging and encrypted storage of secrets.

5. Sub-processors

The controller gives general authorisation for the sub-processors on our sub-processors page. We give at least 30 days' notice of changes, during which the controller may object; if we can't resolve an objection, the controller may close its account. We impose equivalent data protection terms on each sub-processor and remain responsible for them.

6. International transfers

Data is stored in the European Economic Area. We do not transfer it outside the UK and EEA unless a lawful transfer mechanism applies (UK adequacy regulations, the UK–US Data Bridge for certified recipients, or the UK IDTA / Addendum).

7. Helping the controller

We provide tools for the controller to answer data subject requests (search, export with photos, correction and deletion), and will reasonably help with requests, DPIAs and consultations with the ICO. Requests we receive directly are passed to the controller without undue delay.

8. Personal data breaches

We notify the controller without undue delay after becoming aware of a personal data breach affecting its data, with the information it needs to meet its own reporting duties.

9. Deletion and return

The controller can export all its data at any time. When it deletes its organisation, we delete the data immediately from the live system; backups are overwritten within 30 days. Records the controller deletes, or that pass its retention period, are deleted in the same way. An organisation nobody has used for six months is warned by email and, if still unused 30 days later, deleted the same way (Terms, section 3). The only thing we keep afterwards is a closure record about the account itself (Privacy policy, "How long we keep it") — never visitor data.

10. Audits

We make available the information needed to demonstrate compliance with this DPA and allow for reasonable audits, on reasonable notice and no more than once a year unless required by a regulator or after a breach.

ArrivePad: visitor sign-in for UK organisations.
UK-only service · UK GDPR & Data Protection Act 2018 · Data stored in the EEA.
ArrivePad is run by Zac Simmonds, trading as ArrivePad. ICO registration 00016212501.
Pricing Contact Privacy Terms Fair use DPA Sub-processors Security Cookies