Privacy policy — Rydi driver app
Last updated 19 August 2026 · applies to the Android and iOS app “Rydi” (com.avilo.rydi)
Rydi is a delivery app used by drivers at work. It is provided by their employer or by the laundry whose deliveries they drive, and this policy describes what the app on the phone collects, why, and where it goes.
Who is responsible
The app is published by Avilo AS (Norway). For the delivery data inside it, the operator — the laundry or transport company the driver works for — is the data controller; Avilo AS processes it on their behalf as a data processor under a data processing agreement. Questions about your own data are answered fastest by your employer; Avilo can be reached at post@avilo.no.
What the app collects
| Data | Why | Leaves the phone? |
|---|---|---|
| Location while the app is open | Shows the driver on the map, answers “I’m here” at a stop, and lets dispatch see where the round has got to. | Yes — only the coordinates of where you are, sent to the operator’s own Rydi server. Nothing else travels with them: no speed, no route, no history. |
| Location in the background | Arrival alerts: the phone notices when the driver reaches a stop and reminds them to come back to Rydi for the signature. | No. See below. |
| Photos taken in the app | Proof of delivery — what was handed over and where it was left. | Yes, attached to that delivery. |
| Signature drawn on screen | Confirms the recipient accepted the delivery. | Yes, attached to that delivery. |
| Name and email of the driver’s account | Signing in, and showing who did what on a delivery. | Yes. |
| Crash and error reports | Finding faults in the app. | Yes, to Avilo’s own error tracker. Personal details are deliberately not attached. |
Background location, precisely
The driver turns arrival alerts on themselves, in the app’s settings — they are off until they do. When they are on, the phone’s operating system watches a circle around each stop on today’s round and wakes the app when the driver arrives.
That location is not sent anywhere. The only thing the app does with it is show a notification on the same phone. No coordinate, and not even the fact that an alert fired, reaches the employer, Avilo, or anybody else. Turning the setting off stops it entirely.
The reason the feature exists at all is that drivers navigate in Google Maps or Waze, outside Rydi. Without the alert, nothing brings them back to the app to take the signature.
Speed is never reported
The app can show the driver their own speed and a warning when it is above the limit. That stays on the phone: it is not stored, not sent, and not visible to the employer. It exists for the person driving, and it is deliberately not a way to judge them.
What the location data may and may not be used for
Location collected for planning and following a round is used for exactly that. Under Norwegian law GPS monitoring at work is a control measure (arbeidsmiljøloven ch. 9): the employer must have a legitimate reason for it, must discuss it with employee representatives before introducing it, and must tell the affected employees what it is for. Data gathered for route planning must not be repurposed to assess an employee’s performance, and Rydi is built not to offer that: it aggregates time spent to the place, never to the person.
Why we are allowed to process it
Each purpose has its own basis under the GDPR:
- Deliveries, photos, signatures, account: necessary to perform the contract between the operator and their customer, and to prove a delivery happened.
- Position while the app is open: the operator’s legitimate interest in knowing where a round has got to, so dispatch can answer a customer asking where their linen is and can re-plan a route that has fallen behind. Nothing more specific than the current position is kept, which is what keeps that interest proportionate.
- Arrival alerts: your consent, given by turning the setting on. Turn it off and it stops — no explanation needed, and nothing about the choice is reported to anyone.
- Crash reports: our legitimate interest in an app that works.
No automated decisions about you
Nothing in Rydi scores, ranks or judges a driver, and no decision about anyone is made automatically. Time spent at a stop is counted towards the place — a goods reception that is always slow is a fact about that address — never towards the person who was standing there.
How long it is kept
- Live position: the latest one, overwritten by the next. It is not a trail.
- Deliveries, photos and signatures: kept by the operator for as long as they need them as proof of delivery and to meet their own bookkeeping obligations.
- Crash reports: 90 days.
The operator decides the retention of their own delivery data; ask them for their period if you need the exact figure.
Deleting it
Ask your employer and they can have your account closed and its personal details removed; the deliveries themselves stay as long as the operator needs them as proof, since a delivery record is also the customer’s receipt. When an account is closed, the last known position is deleted with it — it is one row, overwritten in life and gone at the end.
How it is kept safe
- Everything between the app and the server travels over HTTPS; nothing is sent in the clear.
- The sign-in token is held in the phone’s own secure storage (Keychain on iOS, Keystore on Android), not in ordinary app files, and the app can be locked behind a fingerprint or face.
- An operator sees only their own data — the separation is enforced by the server on every request, not by what the app chooses to show.
- Servers and backups are in the EU/EEA, access is limited to the people at Avilo who maintain them, and that access is logged.
Who else sees it
Nothing is sold, and nothing is used for advertising. The app talks to the operator’s own Rydi server. Beyond that, two services are involved:
- Mapbox — draws the map and turns an address into a coordinate. It is a US company, so those requests leave the EEA; they are covered by the EU Commission’s standard contractual clauses. What it receives is a map tile request or an address to look up — not your name, and not who is driving.
- Avilo’s own error tracker — crash reports, hosted by us in Europe.
Delivery data, photos and signatures are stored in the EU/EEA.
Permissions the app asks for, and why
- Location — the map, “I’m here”, and (optionally) arrival alerts.
- Camera — proof-of-delivery photos.
- Notifications — new work, and arrival alerts.
- Biometrics — unlocking the app without retyping a password. The fingerprint or face never leaves the phone’s own secure hardware; the app only learns whether it matched.
Each of these can be refused, and the app keeps working with less: without location there is no map, without the camera there is no photo proof.
Your rights
Under the GDPR you may ask for a copy of your data, ask for it to be corrected or deleted, and object to processing. Because your employer is the controller, address the request to them first; they can reach Avilo through their agreement. Complaints can be made to the Norwegian Data Protection Authority, Datatilsynet.
What you have to give, and what you do not
Signing in and recording a delivery are part of the job: without them the app cannot do what it is for. Everything else is a choice — arrival alerts, and each OS permission — and the app keeps working with less. There is no penalty in Rydi for saying no, and nobody is told that you did.
Children
The app is a work tool for employed drivers and is not directed at children.
Changes
If this policy changes in a way that affects what is collected or where it goes, the date at the top changes and the app tells you at next sign-in.