Privacy.

Data controller

NomadMapper AS is the controller for personal data processed in the service. Privacy questions go to privacy@nomadmapper.com.

01Information we collect

1.1 Account and profile

Name, email address and password (stored as a cryptographic hash – we cannot read your password). Plus whatever you choose to add: profile picture, home city, date of birth, countries visited, preferred activities, language, currency and theme.

If you sign in with Google or Facebook, we receive your name, email address and a user ID from that provider. We never receive your password with them.

1.2 Trips and planning

Trip names, dates, destinations, participants, day plans, tasks and checklists, budgets and expenses, notes and wishlists.

What the others on the trip see. A shared trip is made for planning together, so the other participants see what concerns the trip: plans, bookings, tasks, votes on where to stay (including who has not voted yet) and whether you have checked in for the flight. When you mark that you have checked in, the others get a notification. Notifications can be turned off in the notification settings.

When you find the place and dates together. When you answer the questions in a trip, the others see whether you have answered, the days you can travel, who a suggestion does not suit, dates and places you have suggested, and what you voted for. They do not see your budget, your departure airport or what you write to Noma. The suggestions only say «over the budget of 1 of 4», and only once at least three have answered. Places from your wishlist are already selected in your answer, and you can remove them. The ones you keep, the others see as suggestions from you, not that they came from your wishlist.

1.3 Photos and media

The photos you upload, along with captions, albums and any EXIF data. If a photo contains GPS coordinates, we use them to place it on the map.

1.4 Chat and messages

Messages, attachments, timestamps and read receipts in the trip chat, plus system messages such as invitations and task assignments.

1.5 Travel documents

If you upload – or forward by email to your trip’s own inbox address – a ticket, hotel confirmation, insurance policy or receipt, we store the file and the details we extract from it: journey numbers, times, booking references, passenger names and amounts.

1.6 Location and maps

GPS coordinates from photos, routes and travel history, map interactions and – if you turn it on for a trip – live location shared with the other participants. You control sharing and can turn it off at any time.

Around the travel day we send the coordinates of the arrival airport and your stay to Mapbox to estimate how long the drive takes. No name or other information about you is sent.

The map on the From → To pages in the travel book can be drawn with map tiles from OpenFreeMap (OpenStreetMap data). When you view or move the map in the Book Studio, your browser fetches tiles for that area, and OpenFreeMap sees your IP address and which area it is. The colours and relief of the landscape come from elevation data fetched from Amazon Web Services (AWS Open Data) in the same way, so AWS also sees your IP address and the map area. When the book is made, our server fetches the tiles and the elevation data for the same area. If you choose car, bus, train or on foot on a From → To page, our server fetches the way shown on the map: car and bus follow the fastest road and on foot the shortest walking route (with a ferry where needed) from Mapbox, and train follows the railway from BRouter (brouter.de), a routing service built on OpenStreetMap data. Only the coordinates of the two places are sent. No name, trip or other information about you is sent.

1.7 Social and community

Friends and followers, invitations, recommendations and travel tips you publish, votes and comments, plus points, badges and leaderboard position. Your bucket list is private. If you turn on «Share with friends», friends who have also turned it on can see which dreams you have in common – only the shared ones, never the rest of your list. You can turn it off at any time. If you choose one of your own photos from a trip as the photo for a recommendation, we store a copy without location data (EXIF) with the recommendation, and everyone who sees the recommendation sees the photo. The photo in the trip is not changed.

If you ask Noma about your friends’ trips, Noma only gets what you can already see under «Friends’ trips»: upcoming and ongoing trips that a friend has shared with friends (or publicly), with the friend’s first name, the place and the time. Private trips, the other participants, photos and the bucket list are never included, and users you have blocked or who have blocked you are left out. This only happens in the Noma chat, never in the trip chat. If you share a trip with friends yourself, Noma may in the same way mention your first name, the place and the time to a friend who asks.

The days you approve in your travel book can be read by the people you have shared the trip with: friends, followers, or everyone when the trip is public. We also show them in the friends feed under Friends, with your first name, profile photo, the trip name, the day, when it was shared, the photos and the places. They see the same photos as when they open the trip: all approved photos from the trip, including those uploaded by the others on the trip, even if a photo is marked private. Photos awaiting moderation or hidden photos are not shown. Under «Show what the day cost» you choose for each day whether they also see what you spent that day: the total, by category, and each expense with its title, amount and time, so the price can appear next to the place it belongs to. It is off until you turn it on, and it only covers your own expenses, never anyone else’s. If you turn it off again, they no longer see the amounts. If you write a title or a tip for a stop in the day review, they see it when they tap the stop. If you haven’t written anything, we use what the photos say about the place: the description, what the photo shows, the restaurant or building name you gave it, a well-known landmark and the dish. Who is in the photo is never included. If you tap «Get suggestions from Noma», we send what is written about the day’s photos (times, place names, category, dishes and descriptions) to DeepSeek, which writes a title and one sentence per stop. The photos, the coordinates and people’s names are not sent, and the suggestion is only saved if you use it. If there is a flight that day, they only see which countries you flew between, not the airport, flight number, time or booking. If you like a day on a friend’s trip, your friends see your first name and profile photo next to the day in the friends feed. Others only see how many people liked it. Anyone who can see a shared trip can tap «Follow trip». We then store who follows which trip, so we can notify them when a new day is shared. The notification can be turned off under «Trips you follow» in the notification settings. Users you have blocked, or who have blocked you, do not see your trips in the friends feed, cannot follow them and get no notifications. A public trip can still be read by anyone with the link. To draw the map of the day, the app sends the coordinates of the places where the photos were taken to Mapbox, without your name or anything else about you. Under «People you may know» we suggest friends of your friends, with their first name, profile photo and which of your friends you have in common. You appear the same way to friends of your friends. Blocked users are not shown, nor are people you already have a pending request with.

On new trips, the person who creates the trip chooses who can see it: Private, Friends or Public. Everyone who joins makes the same choice for their own photos, both when they join and later under «Who can see your photos». Private means only those of you on the trip see them. Friends means your friends see the trip, with the photos of everyone on the trip who shares. Public means the people who follow you see it too. You can follow someone without being friends. The others on the trip see what you have chosen. If you choose Private, no one outside the trip sees your photos, and your friends don’t see the trip through you. If you don’t follow, or aren’t logged in, you only see a small preview of a public trip: the name, the cover photo, the first names of those who share publicly, the cities and dates, the first day with one photo, and how many days and photos the trip has. If you have blocked someone, or someone has blocked you, that applies here too.

On new trips the travel book makes itself. Every night we put together one shared book from the photos, places, day plan and weather of everyone on the trip. No AI writes in it. Everyone on the trip can change the title, text and tips, choose the cover photo and the order of the photos, add a heading, a text or a quote, choose whether weather, map, day plan, hotel and flight are shown, and hide a day from others. Each of you can hide your own photos. We store who last changed a day. If someone taps «Get a suggestion from Noma», we send what is written about that day’s photos (times, place names, category, dishes and descriptions) to DeepSeek, which suggests a title and text. The photos themselves, the coordinates and people’s names are not sent, and the suggestion is only saved if someone uses it. Your friends see a day once it is over. To be safe, followers and others only see a day two hours after you have moved on from the place (we can tell from where the photos were taken), the hotel only after checkout and the flight only after landing. Everyone on the trip can also hide the hotel or the flights completely. What the day cost is only shown if the person who created the trip turns it on, and then per person and by category, based on the expenses of everyone on the trip.

From the shared book we create posts on the wall for those who can see the trip: the highlight of the day, the day summed up, arriving in a new country, milestones, «so far on the trip» and when the trip is over. The first names of everyone who shares are shown as the senders. There are at most two posts a day, at set times in the morning, the middle of the day and the evening, by the clock where most of the people who see the trip live. We guess that from the home country in their profiles. When a day is shared, those of you on the trip get a notification and can change or hide it. When you see a post from a friend, it may say that the country is on your bucket list, or that you have been there. Only you see it, and we only use your own bucket list and your own trips.

If you turn on visibility in Meetup, other signed-in users in the same country see your first name with your last initial, your profile photo, status, what you are open for, your dates and roughly where you are. Your location is rounded to about one kilometre before it is shown. If you choose «Women only», only women see your profile. If you choose «Verified profiles only», only verified hosts see it. Users you have blocked, or who have blocked you, do not see you. The same applies to posts on the board. You can hide yourself at any time.

If you play today’s challenge in the Flags, Capitals, Country shapes, Neighbors, Which country is bigger? or Noma’s Fact Hunt quiz, we store which game it is, when the round started and finished, which country you picked for each question (in Neighbors: which countries you checked, and the six options you were given; in Which country is bigger?: the two countries in each pair; in Noma’s Fact Hunt: where you placed the pin on the map, the distance and the points for each question), how many you got right (in the Fact Hunt: hits), your points and your time. The day’s leaderboard in each game shows your first name with your last initial, how many you got right, your time and your points to all signed-in users, because a leaderboard is about comparing yourself with others. Your profile photo, email and the rest of your profile are not shown. The list resets at midnight Norwegian time. Ordinary rounds in the game are stored only in your browser.

1.8 Payments and banking

Subscription plan and status, plus payment metadata from Stripe. We never store your card number. When you buy Noma+, Noma credits or prints (photo book, calendar, poster or canvas), you give your billing address to Stripe. Stripe uses it, together with the country your card was issued in, to determine which country’s VAT applies to the purchase, as the law requires. When you buy prints, we send the delivery address you entered (name, address, email and phone) to Stripe, so you do not have to type it twice. For physical goods, the delivery address decides which country’s VAT applies. We also store whether, and when, you asked for the subscription to start right away, so we can calculate the right amount if you use your right of withdrawal. If you are a local guide and connect a bank account through Stripe Connect, Stripe handles the banking and identity data – we only see that the account is verified. As a local guide, you also give the country you live and offer experiences in, whether you are a business or a private individual, and your VAT number if you have one. The country decides where your Stripe account is created and whether we can pay you out. Travellers who book can see whether you are a business or a private individual, because marketplaces must disclose this. We use the VAT number in our accounts for our fee, and it is not shown to others. To know whether our fee should include VAT, we check the number in the European Commission’s VIES register (EU countries) or in the Norwegian Register of Business Enterprises (Norway), when you save it and then about once a month. We store the result: whether the number is valid, when it was checked, and the name the register gives, which for a sole proprietorship is your own name. If a customer disputes the payment for an experience with their bank, the guide is told that the payment is disputed and how the case ended, because it decides the payout. The guide is not told what the customer wrote to the bank. If you connect your bank to the travel budget through Tink, we store transactions (amount, date, description) linked to the trip. To suggest a category, the description of a transaction may be sent to the AI provider DeepSeek, without account and card numbers. Person-to-person transfers, such as Vipps, are not sent.

1.9 Technical information

IP address, browser type, operating system, device, screen size, time zone and language setting. The IP address on submitted forms is stored only as a one-way hash, so we can stop abuse without keeping the address itself.

1.10 Usage and error reporting

Page views, which features you use, performance measurements and error messages. If you send a bug report from the app, we store your text, which page you were on and – if you attach one – a screenshot.

1.11 Beta test application

If you apply to become a beta tester on nomadmapper.com, we store your name, email, country, your answers and how you heard about us. We save your answers step by step while you fill in the form, so you can pick up where you left off, and so we can see where people stop and make the form easier. We never use a draft you have not sent to contact you. If you do not send the application, the draft is deleted automatically after 90 days.

02Legal basis

We only process personal data where we have a valid basis under Article 6 of the GDPR:

Where processing relies on consent, you can withdraw it at any time. That does not affect the lawfulness of processing carried out before you withdrew it.

03What we use the information for

• Running the service: account, trips, photos, chat, maps and documents.
• Tailoring content and suggestions to your travel history and preferences.
• Sending confirmations, invitations, reminders and service notices.
• Handling subscriptions, purchases and payouts to local guides.
• Moderating publicly shared content, and preventing fraud and abuse.
• Measuring usage and errors so we can fix problems and prioritise work.

04Processors and third parties

We use the providers below to run the service. Those marked data processor handle data on our instructions under a data processing agreement. Those marked independent controller decide the purpose themselves – typically when you complete a booking with a travel partner, in which case their own privacy policy governs what they collect.

See all details about our subprocessors

Travel advice for your destination. The country check fetches up-to-date advice on entry, health, safety, money, transport, language, insurance, food and culture using Claude, an AI model from Anthropic, which searches the web and uses official government sites first. To find the advice that applies to your trip, we send the country you live in, the destination (country and city), today’s date, how many days the trip lasts and the language you use the app in. We never send your name, email address, trip name, travel dates or anything else that identifies you. The answer is stored by us and reused for others travelling from the same country to the same place. For “The area” (the guide to the neighbourhood you stay in) we only send the name of the neighbourhood your accommodation is in, the city, the country, today’s date and your language, never the address or the map position. The answer is shared with everyone staying in the same neighbourhood. If you type what you are looking for in “The area” (“Looking for something?”), we also send what you typed, so Noma can search for exactly that. The search is stored without being linked to you and shared with others who search for the same thing in the same neighbourhood. To show the places on the map, we look up their names with Google. Anthropic processes the data outside the EU/EEA and does not use it to train its models.

Travel documents and group suggestions. When you upload a travel document, an AI model (DeepSeek) reads the text to find dates, places and bookings. Before the text is sent, we remove national ID numbers, account numbers, card numbers and the machine-readable zone of passports. When Noma makes suggestions for a group, we send the participants’ first names and age groups (for children, their age), so the suggestions suit everyone. When you have answered the wishes for the trip, the suggestions also get your budget, so no one gets suggestions they cannot afford. The suggestions for a trip are made by DeepSeek. It receives the trip type, the dates that suit the group (without common dates: the periods each of you can travel), the interests, the places you have suggested and what you write to Noma in your answer. Your budget, periods and what you write to Noma are sent without your name. For flight prices we send only the code of your departure airport and the dates to Travelpayouts (Aviasales), never your name. To answer what you ask about a trip, DeepSeek also receives the latest messages in the trip’s Noma channel, including those from the others in the trip, and the first name of whoever is responsible for a task. If you ask about something nearby and share your location, we send it rounded to about 100 metres. If you ask about the accommodation or a booking, we send the address or the booking reference. Noma also receives your home city and country from your profile. If you ask Noma about your friends’ trips, DeepSeek receives the friend’s first name, the place and the month or dates of trips the friend has shared with friends – only when you ask.

We update this list whenever we adopt or drop a provider. If you need it as an annex to a data processing agreement, request it at privacy@nomadmapper.com.

05Where data is processed

Our own systems – database, files and background jobs – run on Amazon Web Services in Stockholm, Sweden (EU/EEA).

Some providers process data outside the EU/EEA. This applies in particular to the AI services and some map services, which are marked in the table above. For those transfers we rely on the European Commission’s Standard Contractual Clauses, together with technical measures such as encryption in transit.

06Cookies and browser storage

6.1 Necessary cookies

• Session cookie – an `httpOnly` cookie that keeps you signed in. It cannot be read by JavaScript in the browser.
• CSRF cookie – protects against other sites performing actions on your behalf.
• Language preference – remembers your language across nomadmapper.com and app.nomadmapper.com.
• Your consent choice – remembers for 12 months whether you said yes or no to statistics, on nomadmapper.com and in the app.

6.2 Analytics cookies

PostHog sets a cookie and stores a pseudonymous ID in the browser to recognise the same session. This only happens after you say yes to statistics. Umami, which we use for basic visitor statistics, sets no cookies.

On nomadmapper.com and in the app, we ask before PostHog captures anything, and your choice applies in both places. If you say no, no analytics cookies are set and your screen is not recorded. The app still fetches feature flags from PostHog, meaning which features are switched on, without storing anything in your browser. On nomadmapper.com we then only count anonymously how many people open and send the beta form. You can change your mind at any time under “Cookies” at the bottom of nomadmapper.com, or under Settings → Preferences → Marketing in the app. If you withdraw consent, we delete PostHog’s cookies from your browser.

6.3 Local storage

We store theme, language, display preferences and cached reference data in the browser’s `localStorage`. Your session token is not kept there – it lives only in an `httpOnly` cookie.

If you fill in the beta application on nomadmapper.com, your answers are also saved in your browser so you can pick up where you left off. They are deleted when you send the application, and otherwise after 90 days.

You can clear cookies and local storage in your browser settings. Clearing the necessary ones will sign you out.

07Analytics, session replay and error reporting

We use PostHog (EU hosting) for product analytics, error tracking and feature flags. PostHog can also record sessions – a replayable reconstruction of how you moved through the interface – so we can see where people get stuck.

Recordings mask typed text and anything we have marked as sensitive. Pages with chat, Noma conversations, documents, banking, budget, diary, payment and profile are not recorded. Safety Card fields are never sent to PostHog.

To keep an eye on Noma’s quality, we also send the questions you ask Noma and Noma’s answers to PostHog, both the answers from the AI model and the answers Noma builds from the trip data without an AI model (for example when you need to leave). They may contain trip details and first names in your travel group, and when you ask about your friends’ trips, your friends’ first names, places and times. Text from documents and attachments you upload, such as passports and tickets, is not sent – only that the parsing happened and how long it took. If you give a Noma answer a thumbs up or down and write a comment, the comment is sent to PostHog together with the answer, so we can see what was good or wrong. The field only appears if you have said yes to statistics.

We also use Umami for cookie-free visitor statistics, and we store performance measurements and client errors in our own database for 30 days.

08Safety Card – health data stays on your device

The Safety Card lets you note allergies, medication, blood type, insurance and next of kin, so the information is available if something happens while travelling.

09Booking with travel partners

Some bookings are completed directly in NomadMapper. When they are, we send the details the trip requires – such as passenger name, date of birth and contact information – to the provider fulfilling the booking.

Elsewhere we hand you over to the partner’s own site. In that case the partner is the controller for what you enter there, and their privacy policy applies.

In “Stay”, the accommodation search field may be Booking.com’s own, loaded in a frame inside the app. Your browser then talks to Booking.com before you click through, and they receive the destination, dates and number of travellers you search with.

If you click through to Booking.com, the link goes via the affiliate network CJ, which records that the click came from us. We pass along a short placement code identifying where in the app you clicked – never your name, email address, trip ID or trip content.

If you open the car rental search at VIP Cars, the link carries the pick-up location and the dates you need the car, so the search is filled in when the page opens. That is all it carries – never your name, email address, trip ID or other trip content.

We fetch the eSIM plans from Saily ourselves, without sending Saily anything about you or your trip. We pick the plans that fit your trip’s countries and dates on our side. If you click a plan, the link goes through Saily’s affiliate network, which records that the click came from us. The link carries the plan, the language, the currency and our discount code – never your name, email address, trip ID or trip content.

We may receive commission when you book through a partner link. That does not change what data is shared, nor the order of recommendations in the app.

10Security

• All traffic is encrypted over HTTPS/TLS.
• Passwords are stored as salted hashes (bcrypt) and cannot be read back.
• Sign-in uses `httpOnly` cookies with CSRF protection, so the session cannot be stolen by scripts on the page.
• Files and photos live in private storage buckets with time-limited access.
• Access to production data is limited to staff who need it.

11How long we keep data

• Your account: for as long as the account is active. If you delete it in Settings, your profile, trips, photos, chat and documents are removed immediately and permanently. There is no grace period.
• Trip content shared with others: messages and content in a shared trip remain for as long as the trip exists, including after you leave it.
• Performance measurements and client errors: 30 days, then deleted automatically.
• Beta application you did not send: 90 days after you last typed in the form, then deleted automatically.
• Rounds in today’s challenge in Flags, Capitals, Country shapes, Neighbors, Which country is bigger? and Noma’s Fact Hunt: 35 days, then deleted automatically. They are also deleted when you delete your account.
• Analytics in PostHog: when you delete your account we ask PostHog to delete the person. Aggregate statistics that cannot be linked to you are kept.
• Payments: Stripe keeps transaction history for as long as accounting rules require, normally five years after the end of the financial year.
• Bank transactions from Tink: deleted when you disconnect the bank or delete your account.
• Support enquiries: kept for as long as needed to follow up the case and document what was agreed.

12Your rights

You have the right of access, rectification, erasure, restriction, data portability, and to object to processing based on legitimate interest.

Two of these you exercise yourself, instantly, without contacting us: under Settings you can download all your data as JSON and delete your account permanently.

Everything else we handle manually within 30 days. See how to use each right.

13Automated decisions

We make no decisions with legal or similarly significant effects based solely on automated processing. Noma makes suggestions – never binding decisions – and you choose what to act on.

Automated moderation can temporarily hide a photo. If you disagree, you can ask for a human to review it.

14Age limit

NomadMapper is not intended for children under 16, and you must confirm that you are 16 or older when registering. If we discover we hold data about a child under 16 without a guardian’s consent, we delete it. If you are a guardian and believe your child has signed up, contact us at privacy@nomadmapper.com.

15Changes to this notice

We update this notice when the service or the rules change. The version and date are shown at the top of the page. For material changes we will notify you in the app or by email before they take effect.

16Contact and complaints

Send privacy enquiries to privacy@nomadmapper.com or use the contact form.

If you believe we are processing your data unlawfully, you can complain to the Norwegian Data Protection Authority (Datatilsynet): datatilsynet.no. We would appreciate hearing from you first so we have a chance to put things right.

This notice is governed by Norwegian law and the General Data Protection Regulation (GDPR).