NeuMaps privacy policy

Version 4 · 18 October 2026

1. Who is responsible

The data controller is MassiuSoft SL (tax ID B27694157), registered office at Fàbrica Maresma 2, 08460 Santa Maria de Palautordera (Barcelona, Spain), entered in the Barcelona Commercial Register (sheet B-656880, 1st entry).

For any privacy question, write to suport@massiusoft.com.

This policy applies to the NeuMaps apps for iPhone and Android, the apps for Apple Watch and Wear OS, and the neumaps.com website with its route planner.

2. In a few words

• You don't need an account to use NeuMaps.
• The map, routes, guidance and stats are worked out on your phone. Your position stays on your phone, unless you share it with a live group or map a resort for us.
• If the app records your ski day, it sends the queues you wait in (the lift, the time you board and the minutes you waited) without saying who you are, so everyone can see the queues right now. You can turn this off in your profile. On the server they are deleted after 2 hours.
• The live group shares your position, where you parked if you marked it and the messages you write in it, only with your group, while you are in it and for 24 hours at most.
• The photos you take in the app stay on your phone. They only leave it if you save them to your gallery or add them to the day image you share.
• There is no advertising and there are no third-party analytics or tracking tools, in the apps or on the website. We don't sell data. The only offers you can see are those of the resort where you ski, and only if you turn them on.

3. What data we process and why

3.1 Your location, for the map, routes and guidance

• What: your phone's GPS position, and the compass to point your dot on the map.
• Why: to show you where you are, start from where you are and guide you along the route, also with the screen off.
• Where: on your phone. Routes and guidance are worked out on the phone, also offline.
• Permission: the app asks for location "while using the app". While it guides you, records your day or shares your position with the group, it keeps using it with the screen off, and the system shows you so. We never ask for "always" location.
• On Android, your position comes from the system location service, which, depending on your settings, may use Google's location services.
• While you are being guided, the next instruction shows on the lock screen and on your watch: anyone who sees those screens can see where you are going.
• Legal basis: providing the service you ask for.

3.2 Your ski day

• What: if you agree to let the app record your ski day (it asks you the first time), your phone keeps the day's positions to work out your stats: runs, vertical, distance, speed and time.
• Where: only on your phone; if you map a resort, the days at that resort also go to the map editor (section 3.12). You can delete days in "My days". On an iPhone, they are included in the phone backups you make (for example, in iCloud).
• You can share an image of a day, with the stats and a drawing of your track, without coordinates, and, if you choose, up to three photos from the day (section 3.15). You choose who with.
• You can turn it off in your profile ("Record your ski day").
• Legal basis: your consent.

3.3 Outing tracks

• This is optional: "Save a track of each outing", in Settings.
• What: the GPS track of each guided outing (a GPX file) and a guidance log: the route, each instruction and when it was given, speed, distance from the route, GPS accuracy and battery.
• Where: on your phone. On an iPhone, in the Files app › NeuMaps › Traces; on Android, inside the app, where you can share or delete them. They are not sent anywhere.

3.4 Live queues

• On by default when the app records your ski day. You can turn them off in your profile ("Share queues"). The app works the same if you do.
• What is sent: each time your phone detects that you queued and boarded a lift, it sends the lift, the time you boarded and how long you queued, with a different random number for each queue. It does not send your position, your track or any identifier of you or your phone. Nothing is sent during guidance rehearsals or with the sample day.
• Why: so everyone can see the queues right now, in the app and on the website.
• How: the server does not store the IP address with the queues (it only uses it at that moment, in memory, to prevent abuse) and rounds the arrival time to the minute. For each lift it publishes the median of the last 20 minutes and how many queues it is based on.
• Retention: deleted after 2 hours, and not included in backups.
• Legal basis: our legitimate interest in showing queues to everyone. You can object by turning them off.

3.5 Live group

• Only if you create or join a group, after agreeing on the screen that explains it.
• What is sent: the name you choose (it doesn't have to be yours); your position, with its accuracy and time, every 15 seconds to 1 minute while you are in the group, also with your phone in your pocket; if you add them, the meeting point and the route you share with the group; if you marked it, where you parked (section 3.13); and the messages in the group chat (section 3.14).
• Who sees it: only the members of the group.
• Retention: the server keeps only each member's latest position, with no history. When you leave the group, yours is deleted at once. The group is deleted when the last member leaves, when its creator ends it or, at the latest, after 24 hours. It is not included in backups.
• The invitation link and QR code are made on your phone, and you choose who to share them with.
• Legal basis: your consent. You can withdraw it by leaving the group.

3.6 Resort data

• The app downloads each resort's package (the map and the data to work out routes) and, when online, checks the resort status (closures and queues) every minute and the weather now and then.
• These requests carry neither your position nor any identifier of you. Like any web server, ours receives the IP address and technical data of each request (for example, the app version).
• The weather is requested by our server from Open-Meteo for a few fixed points in each resort: none of your data goes with it.
• Why: to serve you the data and protect the service (for example, by limiting requests per IP address).
• Retention: server technical logs, 14 days.
• Legal basis: providing the service and our legitimate interest in keeping it secure.

3.7 Your watch and Health

• Apple Watch: if you allow it, the watch saves a downhill skiing workout to the Health app for each guided outing (not for rehearsals). This keeps the app open on the watch while it guides you. NeuMaps does not read any Health data. The watch also uses its compass to point the group arrows.
• Wear OS: no health data is used. The phone and the watch communicate through Google Play services.
• The watch does not connect to our servers: it shows what the phone sends it.

3.8 Emergency card

• It shows 112, the ski patrol phone number and where you are, in words and coordinates. It works offline.
• Calls are made by your phone. If you share where you are, you do it with the system share sheet and with whoever you choose: NeuMaps does not receive it.

3.9 The neumaps.com website

• It uses no cookies and loads nothing from elsewhere: no third-party fonts, scripts or maps.
• The planner remembers in your browser the resort, view and filters you choose. This does not leave your browser.
• The planner does not ask for your location. The points you choose on the map are sent to our server to work out the route and stay in the technical logs for 14 days, like visitors' IP addresses.
• "Listen to the route" uses your browser's voices, which may depend on your browser or system provider.

3.10 If you write to us

• We process what you send us (address, name and message) to reply to you.
• Retention: as long as needed to handle your request and any claims.
• Legal basis: our legitimate interest in replying to you.

3.11 Map editor contributors

Only for people we invite to review the map:

• you sign in with a link we send by email; we keep your address, username, permissions, a session cookie (needed to sign in) and an access log with the IP address;
• each change is signed with the username and time. This history is not deleted: it is what proves where each piece of map data comes from;
• the account and access log are kept while you contribute; the change history, always.
• Legal basis: the contribution agreement.

3.12 Mapping mode

Only for people we invite to map a resort with the app:

• it is turned on with an invitation link (by email or with a QR code) and after accepting it on the app screen that explains it; to invite you we keep your address and name, as for map editor contributors (section 3.11);
• what is sent: when each ski day at that resort ends (and when you ask for it with the day's button), the positions the phone recorded that day (time, coordinates, altitude, accuracy and speed), the phone model (for example, "iPhone") and the app version. We only keep the positions from that day inside the resort, from the first to the last moment near the slopes or lifts; the rest is discarded on arrival;
• what for: correcting and completing the resort's map (slopes, links, lift ride times);
• who sees it: the people in the editor allowed to correct that resort;
• retention: each day is kept until someone has used it and marks it as reviewed, and for 90 days at most; then its positions are deleted and only its date is kept, for a year, so it is not received again. If you delete a day in the app, it is also deleted from the editor. Corrections made from it stay in the map history with a reference to the day, without the positions;
• the phone identifies itself with a token that we only store as a one-way hash, and which expires if it is not used for 120 days. You can stop mapping whenever you want, in the app profile, and the person who invited you can also remove it;
• Legal basis: your consent. You can withdraw it by stopping mapping.

3.13 Where you parked ("Where's my car")

• What: where you parked, if you mark it ("I'm at my car", with your current position, or with a long press on the map), and when you marked it. If you don't mark it and the app is recording your day, it suggests a spot: the base of the first lift you ride.
• Why: to show your car on the map and plan the route back to it.
• Where: on your phone, with the app's preferences. It is deleted at midnight (resort time) or when you remove it. On iPhone, it is included in the phone backups you make (for example, in iCloud).
• In a live group: if you are in a group, the car you have marked or confirmed (not a suggested one) is sent to the group so the other members can see it on the map and go there. On the server, it is deleted when you remove it, when you leave the group or when the group ends (24 hours at most), and it is not included in backups.
• Legal basis: your consent. In the group, the one in section 3.5.

3.14 Group chat

• Only inside a live group (section 3.5).
• What is sent: the messages you write (200 characters at most) and the canned phrases you send, also from the Apple Watch, with the name and colour you have in the group and the time.
• Who sees it: only the members of the group, including those who join later (the last 200 messages at most).
• Retention: on the server, until the group ends (24 hours at most), also if you leave earlier, so the others can read your last message. They are not included in backups or in the server logs. On your phone, only while the app is open.
• Alerts: with the app closed, the app itself checks for new messages and shows the alert on your phone. We don't use Apple's or Google's notification services: we send them nothing. You can turn alerts off in the chat.
• We don't read the messages or use them for anything else. The chat is not an emergency service: for that there is the emergency card (section 3.8).
• Legal basis: your consent, the one in section 3.5.

3.15 Photos of your day

• What: the photos you take in the app while your ski day is being recorded, with your phone's camera. They are kept with the time you took them; where, the app works out from the day's positions (section 3.2). The photos are saved again without metadata (neither the location nor the phone model).
• What for: to show them in the timeline and on the day map and, if you choose, in the image you share.
• Where: only on your phone, inside the app. They are deleted when you delete the photo or the day. On an iPhone, they are included in the phone backups you make (for example, in iCloud). They are not sent anywhere.
• To Photos or your gallery: if you tap "Save to Photos" (iPhone) or "Save to gallery" (Android), a copy is saved to your phone's gallery, with the time and, on an iPhone, where you took it. From then on, it's yours to manage.
• Permissions: on an iPhone, the camera and adding photos to Photos (not reading them). On Android, the app uses your phone's camera app and does not ask for the camera permission.
• Legal basis: providing the service you ask for.

3.16 Resort offers

• Only if you turn them on. The first time the resort where you are has an offer, the app asks whether you want to see them. You can change it whenever you like in your profile ("Resort offers"). Without your "Yes", none are shown and nothing is sent.
• What is read: the resort's list of offers, which is public, like the state of the slopes. The request carries nothing of yours.
• The arrival time: your phone works out whether you'll make it in time with your position, your profile, the queues and the lift opening hours. Your position never leaves your phone.
• What is sent: - when an offer card appears on screen, the offer and a random number that is different each time (to count how many times it has been shown), with no identifier of you or your phone; - with "I'm going", a ticket: a random code made by your phone, with no link to you or your phone. The server only keeps a one-way hash of it. If the offer has limited places, one is booked for you at that moment; - when the venue scans the ticket's QR code with its reader, the server records the venue and the time, so the ticket can't be used twice.
• Who sees it: the resort sees the figures for each offer and each venue (how many times they were shown, if 10 or more, and how many were accepted and redeemed). Never anything about a person.
• How long: on your phone, the day of the offer. On the server, the numbers for each time an offer is shown, 2 days; tickets, 30 days after the offer ends. After that, only the count remains.
• Who is responsible: MassiuSoft, for showing you the offers and for the ticket; the resort, for the content of the offer and what is provided at the venue.
• Legal basis: your consent. You can withdraw it in your profile.

4. What we don't do

• There is no advertising: only the offers of the resort where you ski, if you turn them on (section 3.16).
• There are no third-party analytics or tracking tools, in the apps or on the website.
• We don't sell or hand over personal data.
• We don't give individual data to resorts.
• If accounts are added later, we will update this policy first.

5. Who it is shared with

• EUginy, the group company that runs our servers, on our behalf.
• Postmark (United States), which sends sign-in emails to map editor contributors and mapping invitations.
• MXroute (United States), the email provider for suport@massiusoft.com.
• Apple and Google, when you download the app from their stores, when the system gives you your location (Android) or when the phone talks to the watch (Wear OS). These are their own processing activities, governed by their policies. In the 2026-27 season NeuMaps is free and has no in-app purchases.
• Authorities, if the law requires it.

6. Where it is stored

• On your phone: your position, your ski day, your day's photos, your tracks, where you parked and your preferences.
• On our own servers, in the province of Barcelona (Spain): what is described in sections 3.4, 3.5, 3.6, 3.9, 3.11, 3.12, 3.13, 3.14 and 3.16. Backups are also in Spain.
• Outside the European Economic Area: map editor sign-in emails, at Postmark, which participates in the EU-U.S. Data Privacy Framework; and emails you send to suport@massiusoft.com, on MXroute's server in the United States.

7. How long

• Your position for the map and guidance: it doesn't leave your phone.
• Your ski day and tracks: on your phone, until you delete them.
• Your day's photos: on your phone, until you delete them or the day.
• Preferences: on your phone, until you uninstall the app.
• Live queues: 2 hours.
• Your position in a live group: until you leave; 24 hours at most.
• Where you parked: on your phone, until midnight or until you remove it; in a live group, until you leave or remove it, 24 hours at most.
• Group chat messages: until the group ends; 24 hours at most.
• Offers: on your phone, the day of the offer; on the server, the count of each time they are shown, 2 days, and tickets, 30 days after the offer ends.
• Server technical logs (IP address, requests): 14 days.
• Server backups: 7 days, and up to a month on the replica.
• Emails: as long as needed to handle your request.
• Map editor contributors: while they contribute; the change history, always.
• Mappers' days: until they are reviewed, 90 days at most; the day's date, a year.

8. Your rights

You can ask to access your data, correct it, delete it, restrict its processing, object to it and to take it with you (portability). You can also withdraw your consent at any time; what was done before remains valid.

Write to suport@massiusoft.com. We will reply within the time set by law. If we need to check who you are, we will ask for the minimum.

As you have no account and almost everything stays on your phone, we will often hold no data that identifies you. You can delete the data on your phone yourself: days and their photos in "My days"; a single photo from the viewer; tracks from Files (iPhone) or Settings (Android); everything else by uninstalling the app.

If you disagree with our reply, you can complain to the Spanish Data Protection Agency (www.aepd.es) or to the authority of the country where you live; in Andorra, the Andorran Data Protection Agency (www.apda.ad).

9. Children

NeuMaps does not ask for your age and has no accounts. If you are under 14, ask a parent or guardian for permission before using the live group.

10. Security

• Communication with our servers is encrypted (https).
• Only authorised people and systems can write to them. Live group keys, the tokens of phones that map and offer tickets are stored as one-way hashes.
• We make backups every night, with an encrypted replica at another site.

11. Changes to this policy

If we change it, we will say so in the app and on the website, with the date and version number. If a change affects processing based on your consent, we will ask for it again.