Privacy notice
Last updated 25 October 2026. See also our Terms of Use.
Who we are
Arrival ID is operated by Arrival ID Ltd, company number 17458900, registered at Bartle House, 9 Oxford Court, Manchester, M2 3WQ. Arrival ID Ltd is the data controller for the information described here. For any privacy question, or to exercise your rights, email support@arrivalid.app.
What we collect and why
Account details (your email address and name) so you can sign in and own the Arrival IDs you create. Location and access information you enter, and the photographs you publish, so recipients can find the entrance. Recipient activity — that a link was opened, navigation was started, and whether an arrival worked — so publishers can see whether their instructions are correct. Optional contact details you add to a journey. Basic technical records such as the count of failed code attempts, kept to prevent abuse.
Our lawful bases
We rely on contract to provide the service to account holders; legitimate interests to keep the service secure, prevent code guessing and improve the reliability of arrival information; and consent where you choose to attach your phone's location to a photograph. Where you publish someone else's contact details you are responsible for having a lawful basis to do so.
Optional delivery proof
After finding an entrance, a driver may save photographs of the goods, an optional damage photograph and note, capture time and an optional one-time GPS reading. Home proof is always optional; a Business owner may require a goods photo per entrance before delivery completion. With the recipient’s agreement, drivers may add a drawn signature and printed name. Dictation is converted to text for read-back and confirmation; no audio recordings are stored. Photograph the goods, not people. Hidden image metadata is removed; GPS is stored separately with device accuracy and distance from STOP. If location permission is refused, the proof says “Location not shared”. This is not live tracking or independent verification. The guide owner sees the proof and may share an unlisted proof link or download a PDF; anyone holding that link can see its photographs, note, recipient name, signature and GPS. Server receipt time and a SHA-256 evidence fingerprint are stored separately; phone time and GPS can be inaccurate or spoofed and are not guaranteed dispute evidence. Saved originals cannot be edited; corrections are dated additions. Proof links expire 90 days after capture. Automatic permanent deletion of records and photographs is awaiting secure scheduling and is not yet active. Offline proofs stay in this browser until uploaded on reconnection while Arrival ID is open, keeping the original time and GPS. A prepared upload receipt lasts seven days; an expired receipt leaves the unsent copy on the phone with an explanation. Clearing browser data can remove unsent proofs. Downloaded PDFs and copies shared outside Arrival ID are not remotely deleted.
Who else is involved
We use a small number of service providers acting on our instructions: cloud hosting and database/storage infrastructure, transactional email delivery for sign-in and account messages, and HERE for map display. HERE receives map-view requests, including the viewed area and ordinary connection information. Navigate links open your chosen Google Maps, Apple Maps or Waze app with the stored coordinates. We do not sell your information and we do not use it for advertising.
How long we keep it
Published Arrival IDs, photographs and access information are kept while your account is active, and deleted within 30 days of you deleting the Arrival ID or your account. Unpublished draft photographs are deleted after 30 days. Arrival outcomes and reports are kept for up to 24 months as evidence that a location's instructions work. Failed-code security records are kept for 30 days.
Your rights
You can ask for a copy of your information, correct it, delete it, restrict or object to how we use it, and ask for it in a portable form. Email support and we will respond within one month. You can also ask us to delete your account entirely. If you are unhappy with our response you can complain to the Information Commissioner's Office at ico.org.uk or on 0303 123 1113.
What a recipient sees
Anyone holding the link sees the entrance name, instructions, warnings, the entrance pin and the pictures you published. They never see your account, your customer names, your job references or any internal journey name.
Photographs
Pictures are re-encoded on your phone before upload: hidden camera data is stripped and any blurring you apply is permanently baked into the picture. Only that published version is stored. The untouched original never leaves your phone, so a blur can never be undone by us or anyone else.
Who owns the pictures
You keep ownership of every photograph you publish. By publishing one you give us permission to store it and show it to the people holding your link, and to keep it as evidence of what that entrance looked like. We do not use your pictures for anything else, and we do not sell or license them.
Private and shared Arrival IDs
Nothing you create is listed publicly or indexed by search engines. An Arrival ID is reachable only by its code or the secure, unlisted link you share, and anyone holding that link can see it. You can expire or revoke a link at any time, after which it shows nothing but a "not available" message.
Taking something down
If an Arrival ID shows a face, a number plate, a gate code or anything that should not be shared, email support and we will take it down while it is reviewed. Recipients can also report a problem from the bottom of any Arrival ID page.
Keeping instructions safe and current
The publisher is responsible for making sure their instructions are accurate, lawful and safe to follow, and for updating them when a site changes. We do not write, generate or verify instructions, and reports from recipients are only shown to the publisher for review.
What you must not publish
Do not photograph people unnecessarily. Blur faces and number plates before publishing. Never publish gate codes, alarm codes or key-safe details. Only share access information you are authorised to share.
Location
Standard latitude and longitude are stored, so the pin works with any map or navigation app. New entrance positions start from your phone’s GPS and can be adjusted by you; addresses and site details are entered by you, not copied from a map provider’s search or geocoding results. Existing stored records are preserved; this does not audit their historical origin. Your phone's location is only recorded when you request or permit it.
Translations
If a publisher asks for a guide to be translated, the step instructions are sent server-to-server to our translation provider, Verilingo, only at that moment. Verilingo keeps a masked record of each request for up to 30 days. The original instruction is always shown next to any translation. A recipient's chosen reading language is remembered only on their own device. Arrival ID does not send guide information automatically to delivery platforms.
Offline copies
Saving a guide for offline use is optional and only happens when the recipient chooses it. The saved copy stays on that device and may contain the guide's photographs and instructions. It is removed automatically when it expires, where the browser supports this, and can be removed at any time from Offline arrivals. If a link is revoked, the change reaches an offline device only after it reconnects.
Fictional demonstrations
Public demonstrations use fictional places and purpose-made images. They do not expose a real location or personal information. Demonstration responses stay only in the open page, are not stored, and do not affect operational Arrival ID evidence. Unlisted partner walkthroughs do not collect additional information.
Your control
You can edit instructions at any time without changing the link, and you can archive an Arrival ID so the link stops working. Reports from recipients never change your instructions automatically.
Not for emergencies
Arrival ID is not an emergency service and must not be relied on by emergency responders.