Privacy policy

Last updated: October 13, 2026

This policy explains what personal data we process when you use Mappifier, and what your rights are. It covers the apps for Android, iOS and desktop, the web app at app.mappifier.com, and this website.

Who is responsible

We are the controller under the Swiss Federal Act on Data Protection (FADP) and, where it applies, the EU General Data Protection Regulation (GDPR). For any privacy question or request, write to support@mappifier.com.

In short

• To search, you need an account. We store your email address with it.
• The locations you search are sent to our server and, without your identity, to our routing provider. We keep no readable history of your searches: for 30 days we only remember, as a hash, which areas you have paid for, so that searching them again is free.
• The app reads your device’s position only when you tap the location button, to show it on the map. It stays on your device unless you add it as a location.
• There is no advertising, we don’t track what you do, and we don’t sell personal data. We only count, without knowing who, how often some steps happen.
• You can delete your account in the app at any time.

What we process and why

Your account

To create and secure your account we process your email address, an account ID, how you sign in (email and password, Google or Apple), and whether your email address is confirmed. If you sign in with Google or Apple, we also receive the name they share with us.

Sign-in is run by Firebase Authentication, a Google service. It stores your password in hashed form; we never see it. It also sends the emails that confirm your address or reset your password.

Our own database stores your account ID, your email address, your plan and the date your account was created.

Your searches

A search sends each location’s coordinates, the name you gave it, the travel mode and the maximum travel time to our server. To compute the area each location can reach, our server passes the coordinates, the mode and the time to our routing provider, HERE. The coordinates are first rounded to a grid of about 100 metres to 1 kilometre. HERE receives neither your identity nor your IP address.

We keep the computed areas for up to 30 days in a cache that all users share. Its entries aren’t linked to any account.

For each account we store two things. One is a number per month: how many locations it has used. The other is a record of each area the account has paid for, kept for 30 days so that searching it again is free. That record is a keyed hash of the place, the mode and the travel time. It doesn’t contain the place and can’t be turned back into one; it only lets us recognise the same search when you make it again. We don’t store what you named your locations.

Address search

What you type into the address search, the centre of the map and the app’s language go through our server to HERE, which returns matching places. We don’t store them, and HERE doesn’t receive your identity.

Purchases

Location packs are sold by the Apple App Store and Google Play. They process the payment; we never receive your card or bank details. RevenueCat checks each purchase with the store and reports it to us. For that it receives your account ID and the details of the purchase.

For each purchase or refund we store the product, the store, the store’s transaction ID, the price and currency, and the time. We also store how many bought locations you have left.

Error and crash reports

When the app crashes or hits an unexpected error, it sends us a report so that we can fix the fault. On Android, iOS and macOS the report goes to Firebase Crashlytics; on the web, Windows and Linux it goes to Sentry.

A report contains the error and where in the code it happened, the app version, your device model and operating system or browser, and a pseudonymous ID derived from your account ID. It never contains your email address, your locations, addresses or search terms.

Sharing a search

When you share a search, the app makes a link that contains its locations, the names you gave them, and their modes and travel times. Anyone who has the link can see them, so share it only with people who may. We don’t store the link. Its content sits in the part of a web address that browsers don’t send to servers, so opening it doesn’t tell us the locations either. They reach our server only when the person who opened the link runs the search.

A link opened before signing in is kept on that device until the person has signed in and decided whether to open the search.

Your device’s position

When you tap the location button, the app asks your device where it is; the first time, your device asks you for permission. The app marks the position on the map and moves the map there. It doesn’t follow you, and it doesn’t send the position to us. If you then add a location at that place, it is sent to our server like any other location you search.

The map first opens on the country your device is set to. That comes from your device’s region and time zone settings, not from its position.

The map

The map is drawn from OpenStreetMap data served by OpenFreeMap. To load it, your device connects directly to OpenFreeMap, which thereby learns your IP address and which part of the map you are looking at. In the web app, the map software (MapLibre GL JS) is loaded from the unpkg content delivery network, which also receives your IP address.

Data stored on your device

The app stores your language choice, your sign-in session and your last search on your device, so that the search is still there when you come back; in a browser, this uses the browser’s local storage. The last search never leaves your device, and its result is removed after 30 days at most. It stays when you sign out and is removed when you delete your account on that device. We don’t use advertising or tracking cookies.

Counts of how the app is used

To see whether the app works for people, we count how often certain steps happen: the app being opened, the sign-in page being shown, a search being made, the purchase page being opened, a pack being bought, a search being shared. We keep these as totals per day and per platform, such as Android or web. A count isn’t linked to you, your account or your device, and can’t be traced back to them.

Server logs

Our servers and hosting providers process technical data such as your IP address, the time and the address requested, in order to deliver the service and keep it secure. Logs are kept only as long as that requires.

This website

This website sets no cookies, runs no analytics and loads nothing from other sites. The hosting provider processes your IP address as described under Server logs.

When you write to us

If you contact us, we process your email address and what you write in order to answer.

Legal bases under the GDPR

Where the GDPR applies, we process your data:

• to perform our contract with you (Art. 6(1)(b)): your account, your searches and your purchases;
• for our legitimate interests (Art. 6(1)(f)): keeping the service secure, preventing abuse, and finding and fixing errors;
• to comply with legal obligations (Art. 6(1)(c)), for example bookkeeping rules.

Who receives your data

We use the following providers. Each receives only what its task needs.

We don’t sell personal data and don’t share it for advertising. We disclose data to authorities only where the law obliges us to.

Transfers abroad

Some of these providers process data outside Switzerland and the European Economic Area, in particular in the United States. Where a recipient is certified under the Swiss-U.S. or EU-U.S. Data Privacy Framework, we rely on that. Otherwise we rely on the standard contractual clauses approved by the European Commission and recognised by the Swiss Federal Data Protection and Information Commissioner.

How long we keep data

• Account, monthly usage, purchases and bought locations: until you delete your account.
• Cached reachable areas: up to 30 days. They aren’t linked to you.
• Crash and error reports: up to 90 days.
• Records of the areas you paid for: 30 days.
• After you delete your account: a hash of your email address and the number of free locations you had used, until the end of the month.
• Emails you send us: as long as handling your request requires.

Apple, Google and RevenueCat keep their own records of purchases for as long as their policies and the law provide.

Deleting your account

You can delete your account in the app: open the account menu and choose Delete account. This immediately deletes your sign-in, your account record, your usage, our records of your purchases and any bought locations you haven’t used. See Delete your account for the steps and for what to do if you can’t open the app.

One thing stays until the end of the month: a hash of your email address, together with the number of free locations you had used. If you sign up again with the same address in that month, the new account continues from that number instead of starting with all its free locations. We keep the hash, not the address itself.

Your rights

You can ask us to tell you what data we hold about you, to correct it, to delete it, to restrict its processing or to hand it over in a common format. You can also object to processing that we base on our legitimate interests. Write to support@mappifier.com; we answer within 30 days.

You can complain to a data protection authority: in Switzerland the Federal Data Protection and Information Commissioner (FDPIC), in the EU or EEA the authority of the country where you live.

Children

Mappifier isn’t meant for children under 16, and we don’t knowingly collect their data.

Security

Connections to our services are encrypted. Access to our database is limited to the people who run the service, and the keys for our providers stay on our server.

Changes to this policy

When we change this policy, we change the date at the top. If a change is significant, we announce it in the app or by email before it takes effect.