Privacy policy

01 Summary

• Your drives are always visible to you. They are private by default, and you can share a drive with one crew.
• Drives are recorded in the mobile app, which stores your location only while you are recording. Background recording is optional. The website does not use your location.
• Standings are opt-in. Distance standings and top-speed standings are separate choices.
• Usage analytics in the app are off until you turn them on. On the website they are on by default.
• The current mobile app shows no ads, and it does not show an ad consent form or Apple's tracking prompt. The website shows no ads.
• We do not sell your data, and we do not send your location or drives to advertisers.
• You can delete your account at any time from Settings in the mobile app. On the website, email privacy@revada.app to delete your account or to request a copy of your data.

02 What we collect

Account details. Email, display name, handle, country, profile photo and how you sign in (email and password, Google or Apple). Every part of Revada needs an account.

Drives. GPS coordinates, timestamps, speed, heading and figures we work out from them, such as distance, moving time, top speed and elevation. Also the drive title, notes, the vehicle you picked and the visibility you chose.

Photos. Your profile photo, vehicle photos and any photos you add to a drive in the app. The app shrinks and re-saves each photo before upload, which removes hidden details such as the GPS position your camera stored. It also saves a small map image of each drive's route for your own drive pages.

Garage. Vehicles you add, with the details you enter.

Crew data. Crews you create (name, description, country if you pick one, and whether it is private), crews you join, and the posts and events you add to them.

Notifications. If you turn on Crew post notifications in the app, we store your Expo push token so we can send those alerts.

Usage analytics. See section 06.

Crash reports. If the mobile app crashes or hits a fatal error, it sends a crash report so we can fix it. This is separate from the analytics choice and happens regardless of your choice in Settings. We do not add your name, email or route to crash reports. The website does not send crash reports.

Support messages. If you use the contact form, we store your topic, message, reply email, platform and app version.

Early access list. If you join the early access list on our website, we store your email address and the time you signed up. If you pick a phone type, we store that too. To stop spam sign-ups we also keep a scrambled form of your network address and your browser type. We use your email only to tell you when the app is ready. Email privacy@revada.app and we will delete it.

We do not collect payment card details, contacts, or bank information.

03 Location

The mobile app asks for location access so it can record a drive. It reads your location while you record a drive, and on the Drive and setup screens to show GPS signal strength before you start. It does not store your location unless a drive is recording. The website does not ask for your location.

Background recording is off by default. If you turn it on in the app's Settings, the app also asks for background (Always) location so a run keeps recording while your screen is off or you switch apps. Recording stops if you force-close the app.

Signal gaps. GPS can drop out, for example in tunnels. When the signal comes back, we check the gap. If it is short and the jump is realistic for a car (up to 30 minutes, 10 km, and an average under 200 km/h), we count the straight line between the two points as distance and draw it as a dashed line. If not, that stretch is left out of your distance and not joined up on the map.

You can turn off location access in your phone settings at any time. Recording stops and the rest of the app keeps working.

04 Why we use it

• To record a drive and draw its route and log.
• To show your archive, garage, profile and stats.
• To share a drive with the crew you picked.
• To run crews, crew posts and crew events.
• To send Crew post notifications, if you turn them on.
• To rank you in distance or top-speed standings, if you opt in.
• To understand how Revada is used, through analytics.
• To find and fix crashes.
• To answer support messages.

Our legal bases are your consent (location recording, analytics in the app, sharing), contract performance (the features you asked for) and legitimate interest (security, abuse prevention, crash fixing, website analytics).

05 Who can see your data

• You: all of your own drives, always, whatever visibility you set. This includes archived drives.
• Private (default): only you.
• Crew: only active members of the crew you tag the drive with.

Drives you share with your crew show distance, average speed, your exact max speed, when the drive started, and a simple route shape, with no real coordinates, map, title or vehicle. Your best top speed among drives shared with a crew, and when you set it, also appears on that crew's top-speed board for its members. External drive cards show distance, average speed and max speed only.

Distance standings (opt-in) show your display name, country and total distance. Top-speed standings (opt-in) show your display name, country and top speed. Neither shows routes, drive IDs or exact times. Other drivers can open your public profile from the standings. It shows your display name, profile photo, country, drive count, and your total distance or top speed only for the standings you joined.

Your profile photo and vehicle photos can be seen by other signed-in drivers. Run photos and run map images are only visible to you. Crews that are not private can appear in crew discovery with their name, description and country.

Change any of this in the Revada app, under Settings.

06 Analytics

In the mobile app, analytics are off until you turn them on in Settings, and you can turn them off again at any time. On this website, analytics are on by default, and there is no website setting to turn them off yet.

We record events such as starting or saving a drive, opening a screen, or joining a crew. Events are linked to your account ID but do not include your email, name or GPS coordinates. They go to our own event store on Firebase, where we delete them after 90 days. Separately, PostHog (EU cloud) records, linked to your account ID, the screens you open and the buttons you tap in the app, and the pages you visit (with their full address) and what you click on the website. We use it for feature flags and funnels. The mobile app does not record your screen. On the website, PostHog can also record how you move through pages (session replay) when that is switched on in our PostHog project.

07 Ads

The current mobile app shows no ads. It does not request ads, show Google's ad consent form or ask for Apple's tracking permission. Our source code keeps Google AdMob support so ads can be added later, but this version is built without Google's ad software. The website shows no ads.

If we add ads later, we will update this policy first. Where the law requires it, for example in the EEA and UK, Google's consent form asks whether you agree to personalised ads before any ads load. On iPhone, personalised ads would also need your permission through Apple's tracking prompt.

08 Services we rely on

• Firebase (Google LLC): sign-in, database, file storage and server functions.
• PostHog: product analytics.
• Sentry (Functional Software, Inc.): crash reports from the mobile app.
• Expo: delivering push notifications, if you turn them on.
• OpenFreeMap (tiles.openfreemap.org): map tiles in the mobile app. Each map you view requests tiles from it, which shows it the map area you are looking at and your IP address.

We use Sentry to receive crash reports. Data may be stored and processed in a country other than your own, with safeguards suited to your jurisdiction. For example, standard contractual clauses where EU or UK law requires them, or the safeguards required under the Philippines' Data Privacy Act of 2012 (RA 10173) for Philippine residents. We do not sell your data.

09 Retention and deletion

Drives, photos and garage entries stay until you delete them or delete your account. Our own analytics events are deleted after 90 days.

When you delete your account in the mobile app's Settings, we delete it straight away: your profile, drives, drive photos, garage, vehicle and profile photos, standings entries, public profile, crew memberships, crew posts, analytics events and support messages, and then your sign-in. Crews you own pass to another active member. A crew with no other active members is deleted. If a step fails, it is retried automatically until it finishes. We keep a small record that the account was deleted, so late updates cannot bring data back.

If you can no longer open the app, the data deletion page explains how to ask us to delete your account and data.

Deleting your account does not remove data already held by PostHog or Sentry. If an earlier test version of the app showed you ads, Google AdMob may also hold data from it. Email privacy@revada.app if you want us to ask them to delete it.

10 Your rights

Under applicable data protection law you may access, correct, object to processing, request erasure or blocking, port your data, and be informed of breaches. To delete your account, use Settings in the mobile app. The website has no delete option, so if you only use the website, email privacy@revada.app and we will delete it for you. You can also email us to request a copy of your data. We respond within 15 working days. You may also complain to your local data protection authority.

11 Children

Revada is not intended for children under 13. If a child's data has been provided to us, contact privacy@revada.app and we will remove it.

12 Security and changes

Data is encrypted in transit, access is restricted to the people who need it, and accounts are protected by authenticated sessions. No system is perfectly secure. If a breach affects you, we will notify you and the regulator as required.

We will post material changes to this policy in-app before they take effect. Questions: privacy@revada.app.