Privacy policy

Last updated: 2 November 2026. The Dutch version of this policy is leading if the two differ.

Car sharing and sign-in

If you use car sharing, you sign in with Apple or Google. Your chosen provider processes your sign-in; Revly receives a unique account identity and stores it on the sharing server at Cloudflare. Your password is not sent to Revly. Google sign-in requests only a sign-in identity, without access to Gmail, Drive or contacts. Revly does not store a Google email address, profile name or Google access or refresh token for this purpose. See the Google privacy policy and Apple privacy policy.

Only after your explicit choice do you share a car and its existing history with invited members. The sharing server processes vehicle details, a compressed cover photo, tire and battery details, trip dates, duration and distance, odometer readings, refuelling and charging, recorded costs including fixed expenses, maintenance and reminders. The shared cover is resized and re-encoded without photo metadata; the original remains on your device. Routes, GPS points, addresses, personal notes, private or business classifications, extra gallery photos and invoices remain outside the shared records. Other cars are not automatically shared. This is separate from voluntary consumption contributions.

The app stores your Revly session in the iOS Keychain. Linking sign-in methods requires an explicit action and proof of both identities; matching email addresses never automatically merge accounts. You can sign out, revoke access or delete your sharing account through sharing account management. Owners must stop sharing their own cars first. Records in another owner's dossier may remain. A copy already received by an offline phone may remain after access is revoked.

Who is responsible?

Revly is made by Jelle, a car enthusiast from the Netherlands. You can ask privacy questions via support@getrevly.nl.

What is stored on your phone?

Everything you enter in Revly is stored locally on your iPhone. Think of your cars and registrations, maintenance and costs, reminders, garage appointments, odometer readings, fill-ups and charging sessions, passport entries, insurance details, road tax and lease details, your car's purchase price and value if you enter them, photos of your car, receipts and invoices (including PDFs), pages of your service book, the battery health of an electric or hybrid car (the percentage and who measured it), and trips.

If your iPhone's iCloud backup is on, Apple includes this data in your own backup. Revly has no access to it.

Trips and location

If you turn on Track trips, Revly uses your location, also in the background, to recognise car trips. If location is set to Always, Revly also keeps an eye on your location between trips, so a trip starts as soon as you drive off. When you stand still, iOS pauses this automatically. The distance, the times and (if you want) the route are stored only on your phone. You confirm yourself whether you were driving before a trip counts.

If you allow Motion & Fitness, Revly asks your iPhone's motion sensor whether you were in a car, cycling or walking. That way bike rides and walks don't count as trips. With the same sensor, Revly also spots car trips from the past 7 days that were missed, so you can add them (Missed a trip?). Trip detection processes location and motion on your phone. Features such as address lookup and the map share the data described below with external services.

In Profile > Settings > Data & privacy you choose whether routes are kept and for how long (30 days, 90 days, 1 year or always). The app deletes older routes automatically. You can turn trip tracking off at any time.

Trip addresses

When you open your trips, Revly can look up missing addresses using Apple Maps. Existing start and end coordinates from the saved route or trip are sent to Apple for this purpose. Revly does not retain additional GPS points for this lookup. The resulting addresses stay with the trip on your phone until you delete it. Without available coordinates, the app cannot fill in an address. Home and Work remain recognisable names in the overview.

Business trips (Revly Plus)

If you turn on Keep track of business trips, Revly also keeps the start and end point of every trip, even if you don't keep routes. The app uses them to look up the address through Apple Maps, so it appears in your trip log. For the address, those two points are sent to Apple. Start and end points, addresses, whether a trip is business or private and your description stay on your phone until you delete the trip. If you turn the setting off, Revly no longer keeps new start and end points.

Home and work

If you set a home or work address under Trips > Trip recording and settings > Saved places, Revly keeps that address and its point on the map on your phone. Your trips are then named, for example, Home → Work, trips between home and work are set to business in advance if you keep track of business trips, and the app picks up a trip that starts at home or work more reliably. For each trip, Revly only remembers whether it started or ended at home or work, not the address again. You look up the address through Apple Maps; for that, your search or current location is sent to Apple. You remove a saved place on the same screen, and Delete everything removes them too.

Trip log

So you can see why a trip was or wasn't measured, Revly keeps a trip log on your phone. It only contains times and what the app decided, such as "GPS on", "trip started" or "joined to the previous trip", without places or addresses. Entries older than 7 days disappear automatically. You find it in Profile > Settings > Data & privacy > Trip log. There you can clear it, or share it yourself if you report a problem to us. Revly never sends it on its own.

Trip in progress (Live Activity)

If Show trip in progress is on (Trips > Trip recording and settings), you see distance, time and speed during a trip on your Lock Screen, in the Dynamic Island and in CarPlay. While Revly runs in the background, the app isn't allowed to start that itself. So at the start of a trip Revly sends a short request to Revly's server (at Cloudflare), which sends a start signal to your iPhone via Apple. Only a code from iOS (the push token), a random trip number and the start time are sent, plus ordinary technical data such as your IP address. No location, registration or trip data. The server does not store push tokens or trip content in a database. Cloudflare Workers Logs does store technical request metadata and errors. The app then updates distance, time and speed itself on your phone. If you turn the switch off, this no longer happens.

Scanning receipts and invoices (Revly Plus)

When you scan a fuel receipt or garage invoice, or pick a photo, screenshot or PDF, Revly reads the text on your iPhone itself, using Apple's text recognition. Nothing is sent to a server. The camera only asks for permission the first time you scan. You pick photos yourself with the iOS photo picker, so Revly doesn't see the rest of your photo library.

Scanning your service book

When you photograph the pages of your service book, Revly reads the dates, odometer readings and garages on your iPhone itself, also using Apple's text recognition. Nothing is sent to a server. You check what was found before it is saved. The app keeps the photo of a page with the service entry, on your phone. The first service book is free, after that it is part of Revly Plus.

Map with fuel stations, charging points and garages

The map itself is Apple's (Apple Maps). Revly looks up fuel stations, charging points and garages through Google Places. For this, the area you are looking at on the map is sent to Google, and for brand garages your car's brand as a search term (for example "Volvo garage"). When you tap a place, Revly fetches its name, address, rating and opening hours from Google using the ID of that place. Google also receives ordinary technical data, such as your IP address. These map searches do not send your registration number, trip records, notes or receipts from your vehicle records to Google. Revly may reuse map search results from temporary working memory for up to fifteen minutes. This cache is not written to a file. A saved garage link stores the Google Place ID; Google names and addresses are not permanently copied for that link.

If you search for a town or postcode, Apple looks it up. If you choose Google Maps for a route, that app (or the website) opens with the destination. Google's privacy policy applies to that. If Google is briefly unavailable, Revly uses Apple's search instead.

Garage appointments and your calendar

A garage appointment stays in your local vehicle records: date, time, duration, note and your manually entered garage name or a Google Place ID. Revly does not book anything with the garage. Searching for a garage sends your search text to Google Places; suggestions are only displayed temporarily. For a linked garage, the app requests current business information using its Place ID.

Add to my calendar is optional. Revly opens the system editor with the appointment details so you can review them before saving. A manually entered garage includes its name; a Google link includes a URL with the Place ID. Revly does not request permission to read your existing calendar events for this. Once saved, your chosen calendar service manages the event, including any synchronisation enabled in your calendar settings. Changing or removing an appointment in Revly does not automatically update an earlier calendar event.

Searching for tyres in your browser

Choosing search in Tyres opens a Google search in your browser with the selected tyre type and entered tyre size. No registration number is included. Google receives the search query and ordinary browser information, such as your IP address. You decide whether to continue to a shop.

Exporting

When you export your costs or trip log to Excel, Revly creates the file on your phone. You choose in the share sheet where it goes, for example to your email or your employer. Revly doesn't send it anywhere itself.

Services Revly connects to

For some features, Revly fetches information from other parties. Only what is needed is sent.

For Dutch cars, Revly sends the registration number to RDW Open Data to look up vehicle information and perform checks, such as checking the inspection (APK) date, recalls and whether a previous car is still on the road. This is part of those features, not a usage statistic. The registration number is not included in usage statistics sent to Firebase.

Official fuel consumption comparison

In an app version that supports this feature, tapping fetch requests the available official NEDC and WLTP figures for your registration number from the public vehicle data service. Your registration number is sent for this request. Your fuel entries, costs, odometer readings and trips are not sent. The comparison is calculated on your iPhone.

The figure and retrieval date are stored locally so you can view them offline. After 30 days, the app asks you to refresh before showing a difference again. Delete everything also removes these saved figures. The service receives ordinary technical information, such as your IP address, with a network request. Processing for this lookup is performed to provide the feature you request.

If no figure is available for your car, Revly may request a reference for its technical vehicle group from our Cloudflare service. This sends only a code derived from public technical characteristics, without a registration number, VIN, account or device ID. Cloudflare also receives your IP address with the request. The public reference catalogue uses a D1 database with EU jurisdiction; API requests may be processed through the global network. Under the current Cloudflare settings, technical Worker logs remain available for at most 7 days. Your personal vehicle file is not stored in this catalogue. A group reference is clearly labelled and does not produce an exact difference percentage for your car.

An official test figure is not a real-world average. Using the official comparison does not grant permission to share your own consumption.

For electric cars, we show available WLTP figures in kWh/100 km. For hybrids, NEDC, WLTP, fuel and electricity stay separate. Missing figures are not estimated. Hybrids do not receive a single difference percentage based solely on fuel; this also depends on the split between electric driving and fuel use.

Voluntary consumption contributions

App versions supporting this feature offer a separate Consumption contribution choice. It is off by default and requires explicit consent. In versions supporting automatic sharing, after explicit consent to automatic sharing Revly sends your contribution while the app is open: technical vehicle group, month, measured distance and litres from completed full-tank measurements. This covers up to the previous 24 months plus the current month, only eligible Dutch petrol and diesel cars without hybrid powertrains. The month is the measurement’s closing month. Costs are not shared during this test phase.

Supported app versions can show group averages for petrol and diesel cars with the same sufficiently known technical vehicle group. Viewing is separate from contributing: opening the comparison sends your registration only to RDW and only the technical group code to Cloudflare. Your own refuelling history and participant credential are not sent for this lookup. At least 10 participant codes, 20 participant-months and 10,000 measured kilometres are required; one participant code may supply no more than a quarter of the distance. The average is distance-weighted over at most 24 months plus the current month. Counts are rounded down; small groups and incomplete vehicle matches receive no figures. A participant code is not the same as one person or one car. Withdrawal excludes contributions immediately from the next request; figures already displayed on an open screen can remain until refreshed. Cloudflare receives monthly totals, a technical group code and a random participant code. New app versions also send available technical vehicle details for grouping: make, model, fuel, type approval, type, variant and execution. Missing fields remain unknown and these contributions are grouped separately. A missing official reference value does not prevent a contribution. These details come from RDW and do not prove an exact execution. We receive no registration number, VIN, routes, locations, precise refuelling dates, notes or receipts. Your registration number is sent only to RDW to identify the technical group. Contributions are pseudonymised, not anonymous. Cloudflare also processes your IP address for the request. The D1 database has EU jurisdiction; requests may use the global network. The secure participant credential stays bound to your iPhone.

Each update replaces previous contributions for eligible cars. Versions supporting automatic sharing do this after consent, when the app opens, and after changes or deletions in your local fuel history. If connectivity fails, Revly retries while the app is open or the next time you open it. Older app versions only share through Update contribution. Existing consent to manual sharing only becomes automatic after a new explicit choice to allow automatic sharing. Stop sharing and delete contributions withdraws consent. New uploads stop immediately; contributions are removed once the server confirms deletion. Offline deletion remains pending and is retried when Revly opens or returns to the foreground. Delete everything also requests server deletion. Open Revly online and wait for confirmation before deleting the app. Withdrawal alone preserves your local records.

Monthly totals are deleted daily once older than 24 months plus the current month. After withdrawal, separate consent proof is retained for up to 730 days to demonstrate your choice. Historical platform backups may temporarily contain earlier data; restored data must not be used again for processing. If your phone or participant credential is lost, self-service for that old contribution is unavailable. For access or deletion questions, contact support@getrevly.nl. Consent is the basis for voluntary contributions; refusing or withdrawing does not affect other app features.

EV and plug-in hybrid: a separate choice

App versions supporting EV/PHEV contributions request new, separate consent under Consumption contribution. This is off by default. Earlier petrol/diesel consent does not authorise this data. Only BEVs and RDW-confirmed plug-in hybrids (OVC-HEV) with a complete technical match are eligible; ordinary hybrids (NOVC-HEV) are never shared as plug-in hybrids.

After consent, Cloudflare receives separate monthly fuel and charger-energy totals: technical vehicle group (make, model, type approval, type, variant, execution, powertrain and fuel), source, measurement method, opening and closing months, measured distance and litres or kWh, linked to a random participant code. Fuel uses completed full-tank measurements. Charger consumption requires read odometers and two explicitly confirmed 100% charge boundaries with all intermediate energy. Charger energy includes losses and is not battery consumption. PHEV uses total measured distance without estimating electric kilometres.

No registration, VIN, routes, locations, trips, odometer readings, exact measurement dates, notes, receipts or costs go to Cloudflare in this contribution. Registration goes only to RDW for technical matching. Contributions are pseudonymised; Cloudflare also processes your IP address. The database is in the EU. Consent and the device-bound credential are separate from earlier petrol/diesel contributions. The same retention periods apply: 24 months plus the current month for measurements and up to 730 days after withdrawal for separate consent proof.

After edits, deleted charging/refuelling entries or deleted vehicles, Revly replaces eligible EV/PHEV contributions while the app is open. Without connectivity, replacement waits for a retry. Stop EV/PHEV sharing and delete contributions blocks uploads immediately and removes both fuel and electricity once the server is reachable. Delete everything requests this too. Open Revly online and wait for confirmation before deleting the app. Contributing again requires a new deliberate choice.

Public EV/PHEV comparisons require no contribution. Only the technical group code goes to Cloudflare for lookup, without local measurements or a participant credential. Fuel and charger energy are evaluated separately by powertrain, fuel, source and method: at least 10 participants, 20 participant-months and 10,000 measured km; one participant supplies at most 25% of the distance. Only sufficiently large complete groups receive distance-weighted averages and rounded lower bounds. Insufficient data produces no figure. Personal and group measurements may cover different periods and uses; a technical match does not guarantee equal conditions.

Usage statistics and crash reports

Revly uses Google Firebase (Analytics, Crashlytics and Performance Monitoring) to see which features are used and to fix bugs. This is off by default. It only turns on if you give permission in the welcome flow or in Profile > Settings > Data & privacy.

With permission, the app sends things like: which screens and features you use (for example "maintenance logged" or "trip confirmed"), general device information such as the iPhone model and iOS version, a random app ID and, in case of a crash, technical details about the error. For these statistics and crash reports, we never send your registration number, routes, notes, receipts, garage names or other content of your file to Firebase. This is separate from the data needed to use a feature described above, such as the registration number in an RDW request. From the map we only measure how many places were found and a short error code if a search fails, never which places, where you searched or what you searched for.

Advertising measurement is always off. Firebase is a service of Google Ireland Limited. Google may also process data outside the EU, with the safeguards Google applies for this. Statistics are kept for up to 14 months. If you withdraw your permission, the app stops measuring immediately and the statistics on your phone are deleted.

The legal basis for this is your consent. You can withdraw it at any time, without the app working any less well.

Screen recordings in older app versions

Clarity and the screen-recording switch are being removed from Revly. App versions without this feature do not send screen recordings to Microsoft. Older versions may still offer this optional feature; the following explanation applies to those versions.

In older app versions, you can turn on Screen recordings yourself in Profile > Settings > Data & privacy. This is off by default, even if you have already turned on usage statistics. When it is on, Microsoft Clarity records how you tap and scroll through the app, so we can see where something is unclear or gets stuck.

In these recordings, text, registration numbers, amounts and photos are hidden. Your file itself, your routes and your receipts are not sent. General information is included, such as the iPhone model, the iOS version, the country and a random ID.

Clarity is a service of Microsoft Corporation. Microsoft may process data outside the EU, with the safeguards Microsoft applies for this. Recordings are kept for 30 days, other data for up to 9 months. The legal basis is your consent. If you turn it off, the app stops recording immediately.

Revly Plus

A Revly Plus subscription runs through Apple's App Store. Apple processes the payment. Revly only learns from Apple whether your subscription is active, so the Plus features work. You cancel in your Apple ID settings. The standard Apple terms of use (EULA) apply.

Notifications

Reminders for maintenance, trips, seasonal tips, milestones (such as a round odometer reading or your car's birthday), the fuel use alert and invitations to contribute consumption data are local notifications. They are scheduled on your phone, and nothing goes through a server. In Profile > Settings > Notifications you turn each type on or off.

Your rights

• Access and take with you: via Profile > Settings > Data & privacy > Export my data you get all your data in one file.
• Delete: use Delete everything on the same screen to erase your local vehicle records and request deletion of any consumption contributions. Server deletion may remain pending while offline. If you shared contributions, stop sharing and wait online for confirmation before deleting the app. Deleting the app alone does not request server deletion. Delete previous exports and calendar events yourself; contributions, consent proof and backups follow the retention periods described above.
• Withdraw consent: turn off the switches for statistics and crash reports.
• Questions or a complaint: e-mail us at the address above. If we can't work it out together, you can file a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens, or with the supervisory authority in your own country.

Children

Revly is intended for people aged 16 and over.

Changes

If anything changes in how Revly handles your data, we update this page and the date at the top. For big changes, we will also let you know in the app.