Privacy Policy

Last updated: September 9, 2026

This policy covers the WAIVR mobile app (iOS and Android) and the waivr.ai website, operated by waivr.ai. Contact: support@tm.waivr.ai.

The short version

• We do not know where you are. WAIVR never sends your location to us. There is no live tracking in this app: no position feed, no "where is this rider now" lookup, and nothing we or anyone else could query to find you.
• WAIVR is built offline-first. Maps, routing, search and voice run on your phone. Your GPS trace is processed on the device, not streamed to us.
• We store what your account needs: your email, username, rider name, vehicles, crews, and the rides you record.
• Voice features process audio on the device. We never receive recordings.
• No ads, no ad trackers, no sale of your data. The app carries two open-source SDKs, for crash reports and for product analytics, and both send only to our own servers: neither vendor receives anything about you.

What the app collects

Account data (stored on our servers)

• Email address — used to sign in with one-time codes and for account-related messages.
• Username — your public handle, visible to other riders.
• Rider name (callsign) — the name the app speaks and shows.
• Garage — the vehicles you add (make, model, year).
• Crews — the groups you create or join, and your membership in them.
• Rides — rides you record sync to your account: the track, distance, duration and riding statistics. They are private to your account.

Data that stays on your phone

• Location — the app uses GPS to navigate, including in the background during a ride. Position data is processed on the device. It is not streamed to our servers; only the rides you record are synced, as described above.
• Motion sensors — used to compute riding statistics such as lean angle. Processed on the device.
• Voice — speech recognition and the app's spoken voice run on the device. Audio never leaves your phone.
• Maps and search data — downloaded to your phone so the app works offline.

Real-time location

Your position is read by the app, on your phone, and used there: to draw your bike on the map, to snap you to the road, to speak your next turn, and to warn you about what is ahead. It is not transmitted to us while you ride. We operate no live-location service and no rider tracking, and we have no way of knowing where you are at any moment, including while you are navigating. Which countries' maps you have downloaded says nothing about it either: you can install as many as you like and keep them.

Rides you choose to record are the one exception, and they are a choice: when you save a ride it syncs to your account with its track, so it is there on any device you sign in on. That is a ride you decided to keep, after it happened. It is private to your account, and you can delete it.

Requests our servers see

• Place search — when you search online, your query is sent to our servers, which use Amazon Location Service (AWS) to return results.
• Weather — the app requests the forecast for your area directly from MET Norway (api.met.no), a free public weather service. Only coordinates are sent, no account information.
• Downloads — when the app downloads maps and other offline data, our servers see the standard technical details of the request (such as IP address), used only to serve and secure the download.

Music control

If you connect Spotify or Apple Music, WAIVR only sends playback commands (play, pause, skip) to the music app on your phone. Your music account, listening history and audio never pass through WAIVR or our servers.

Crash and error reports

When the app crashes, hangs or is terminated by the system, it sends a report so we can fix the fault. The report contains the technical detail of the failure: where in the code it happened, the app version and build, your device model, and the operating system version. If you are signed in, the account identifier is attached so we can tell one rider's repeated crash from many riders' single one.

Reports are collected by the open-source Sentry SDK inside the app, but they are sent to our own servers and nowhere else: the app's reporting address is api.waivr.ai. We hold no account with Sentry and Sentry receives nothing. Reports are stored in our own storage and read on an error-tracking server we run ourselves.

A crash report never includes a screenshot, a picture of the screen's contents, your location, your ride data, your email, your username or your rider name. We have switched all of those off.

Product analytics

The app records how it is used, so we can see which features riders reach and where they get stuck. Examples of what is recorded: the app was opened, an onboarding step was completed, a permission was asked for and what you answered, a country's maps were installed, a ride started and ended, a route was planned, a search was used, a setting was changed, a ride card was shared.

Alongside these events we keep a small, deliberately coarse description of the app: your platform, app version, the language the app is set to, whether you see kilometres or miles, which country's map data is active, the make and model of your primary bike, and the status of each permission (not asked, granted, denied). On Android we also keep the Play Store install referrer, which tells us which link brought you to the app. Events are keyed to your account identifier or your device identifier. They never carry your email, your username or your rider name.

Your ride itself is not in this. Where you rode, your speed, your lean angle and your GPS trace are yours. They are shown back to you in the app and they never enter our analytics.

These events are collected by the open-source RudderStack SDK inside the app, configured to send only to our own servers (api.waivr.ai) for both its data and its configuration. We hold no account with RudderStack and RudderStack receives nothing.

What the website collects

• Waitlist and newsletter — if you sign up, we store your email with a double opt-in confirmation. Every email includes an unsubscribe link.
• Visit statistics — the site records anonymous visit events (a random visitor identifier, the page viewed, approximate location at country/city level, and the campaign link that brought you here). This is not linked to an app account.
• Local preferences — your language and theme choices are kept in your browser's local storage. The site sets no advertising cookies.

Where data is stored

Our servers run on Amazon Web Services in the European Union (Ireland, eu-west-1). Data is encrypted in transit. Sign-in codes and account emails are delivered through AWS services. The error-tracking server that displays crash reports is one we operate on rented hardware in Finland, also inside the European Union.

Retention and deletion

Account data is kept while your account exists. You can delete your account from inside the app, or by emailing support@tm.waivr.ai from your account's email address — see how to delete your account. Deletion removes your account data and synced rides from our servers. Data on your phone is removed by uninstalling the app.

Your rights

If you are in the EU/EEA or the UK, you have the right to access, correct, export and delete your personal data, to object to or restrict its processing, and to lodge a complaint with your data protection authority. To exercise any of these rights, email support@tm.waivr.ai.

Legal bases

We process account data to provide the service you signed up for (performance of contract), visit statistics, crash reports, product analytics and service security out of legitimate interest, and waitlist/newsletter emails on your consent, which you can withdraw at any time.

Children

WAIVR is not directed at children and is intended for users of legal riding age. We do not knowingly collect data from children.

What we never do

• No selling or renting of personal data.
• No advertising networks or cross-app tracking.
• No uploading of your voice audio.
• No real-time location. We never receive a live position, we never track where you are, and we cannot locate you or your bike.
• No sharing of your data with any third-party AI service. The app makes no request to any AI provider. The voice that speaks your directions is generated on your phone.
• No sending of your rides, your location or your riding statistics to our analytics or crash reporting.
• No collection beyond what this policy describes.

Changes

If this policy changes, the new version is published on this page with an updated date. Material changes are announced in the app.

Contact

waivr.ai — support@tm.waivr.ai