Privacy policy

Last updated 23 September 2026

This policy explains what Maze collects, why, where it is kept and how to get it deleted. It covers the iPhone and Android apps, the web app at https://app.ridemaze.com and this website. It is written to match what the app actually does. If you find a place where it doesn't, please tell us.

The short version

1. Who we are

Maze is run by Klavs Buss, Barona iela 76, Rīga, Latvia, who is responsible for your data (the "controller" under the EU General Data Protection Regulation, GDPR). Write to [contact email] about anything in this policy.

2. What we collect, when and why

WhatWhenWhy
Device ID: a random code the app creates the first time it starts. Sent with every request that reads or saves your data on our server. Keeps your rides, routes and vehicles yours when you have no account.
Road-usage dots: position, speed, direction, GPS accuracy, altitude, time and the vehicle you picked. While the app is open (on screen) and you are moving: at most one dot every five seconds, and one when you save a point. Short trips (under about ten dots) are never sent. Off with Ghost Rider. To count how often each road is ridden, which with riders' likes tells us which roads are worth riding.
Recorded rides: the same fields, about one per 10 metres ridden, and whether the app was in the background. Only while a recording runs: you started it, or Auto-record did (off by default). With "Always" location permission, it continues when the screen is off. A recording stops by itself after a long stop, and after 12 hours at most. So you can see where you rode, your speed and climbs, and ride it again or in reverse.
Steepness dots: the same fields, about one per 10 metres. Only on steep stretches (8% or more over at least 20 metres), while the app is open or a recording runs. Off with the Altitude meter switch or Ghost Rider. To mark steep roads from real measurements.
Route requests: start, finish, stops and the ride style you chose. When you ask for a route while online. The iPhone app can plan routes on the phone with a downloaded map; then nothing is sent. To compute routes. Not stored unless you save, favourite or start a route.
Saved routes: the line, its distance and stats, and the name of an imported GPX file. When you save, favourite or start a route, or import a GPX file. So your routes are there next time, on every device you sign in on.
Points: category (a road mark such as gravel or a pothole, a view, a like), place, time, the road and direction it applies to, and an optional note of up to 500 characters. When you save a point or like a road. To work out your direction, the app also sends your last 90 seconds of movement with it. We use that once and do not store it. To show riders what is on a road, and to learn which roads riders love. Points are public, except the ones you keep for yourself (see section 6).
Vehicles: type (motorcycle, car, bicycle), top speed, and brand and model if you add them. Asked the first time you open the app; editable in the app. To tell your rides apart by vehicle.
Account (optional): email address and password, your account ID, when the account was created and when you signed in. When you create an account or sign in. Your password goes to Google Firebase Authentication. We never see or store it. To back up and sync your routes and rides across devices. When you sign in, what you saved on that phone before is moved into your account.
Map requests: which map tiles you load. When you look at an area you haven't downloaded (always on the web app). To draw the map.
Server logs: IP address, time, the address requested (which can include your device ID) and your app or browser version. With every request to our server. To keep the service running and secure, and to find faults.
Messages to us: whatever you write. When you email us. To answer you.

We don't collect your name, phone number, contacts, photos or camera, microphone, motion sensors or advertising ID. We don't track you across other apps or websites.

3. Location in detail

Your phone asks your permission before Maze can use your location, and you can change it at any time in the phone's settings.

4. What stays on your phone

So that Maze works without a signal, it keeps things on your phone: your settings and device ID, copies of your routes, rides, vehicles and the points on the map, downloaded maps, and the last five places you picked in search. It also keeps anything not yet sent. It keeps a diagnostics log of errors and app events, which never contains your route lines. The log stays on the phone unless you copy it yourself. The web app keeps the same things in your browser's storage. We don't use cookies, on this site or in the app.

Offline mode pauses sending, not collecting: what is collected meanwhile is sent when you go back online.

6. Who else sees your data

We don't sell your data, show ads or share your data with anyone for marketing.

7. How long we keep it

8. Your controls in the app

9. Your rights and how to use them

Under the GDPR you have the right to:

Write to [contact email]. If you have an account, write from the address on the account. If you don't, include the device ID from Settings → Device ID, because it is the only way to find your data. We answer within one month.

You can also complain to a data protection authority: ours is the Data State Inspectorate of Latvia (Datu valsts inspekcija), or you can go to the one in the country where you live.

10. Children, security, changes

Children. Maze is not meant for children under 16, and we don't knowingly collect their data. If you believe a child has given us data, write to us and we will delete it.

Security. Data travels encrypted (HTTPS). Access to the server and the backups is limited to the people who run Maze. No system is perfectly secure. If a breach puts your data at risk, we will tell you and the authority as the law requires.

Changes. When what Maze collects changes, this policy changes first. The date at the top shows the last change. For a change that matters, we will give notice before it takes effect.