Privacy

Last updated: 15 November 2026

Short version: you don't need an account, and without one we keep almost nothing about you personally: no name, no email, no password, no payment data. If you choose to log in, we keep your email address and what you save. In the app, the AI and booking features otherwise use an anonymous account that isn't tied to who you are, and we keep product analytics so we can tell which features are useful. We don't sell your data. This policy applies to Icebreaker, the free Iceland travel app, and to the website icebreakerapp.is, including tours booked through its Book buttons.

1 · Who we are

Icebreaker ehf. is a private limited company registered in Reykjavík, Iceland. We make the Icebreaker app ("Icebreaker", "the app") and are the controller of the data described here. You can reach us at hello@icebreakerapp.is.

2 · What we collect

Your location, if you grant the permission

When you grant the iOS or Android location permission, the app reads your latitude and longitude to show you what's nearby (cafés, bars, events, activities). Your exact coordinates never reach our own servers; only a rounded location for notifications does, as described under “Notifications about your area” below. Two outside services receive them: the app sends them to Open-Meteo to get the weather where you are, and Mapbox receives location data when it draws the map (see §4). On Android, location is provided through Google Play Services.

Your IP address, at our servers

Like any web server, our servers see the IP address of each request, because that is where the answer goes.

  • Our API server does not write it to its request log: that log holds only a request id, the method, the path and the status code.
  • Our AI and booking functions (on Supabase) never store your raw IP address. They turn it into a one-way hash, used only for the usage limits described below. We call this pseudonymised rather than anonymous: it is not your IP address, but it is still derived from it, so we treat it as personal data.
  • Supabase, which runs those functions and the anonymous accounts, records IP addresses in its own request and sign-in logs, which are kept for a short time (see §5).

An anonymous account, for the AI and booking features

You don't need to sign up or log in. If you aren't logged in, the first time you use Hulli, the trip planner or book a tour in the app, the app quietly creates an anonymous account with our backend provider, Supabase. It has no name, email, phone number or password, and it isn't linked to your identity or to the analytics install ID. The app keeps the account's session on your device and uses it to show our functions that requests come from the app, and to count usage per account.

  • What Supabase stores with it: a random account id, when it was created and last used, and, for the active session, the IP address and device type (user agent) it signed in from.
  • Deleted automatically: an anonymous account that hasn't been used for 30 days is deleted, together with its sessions. If you come back later, the app simply creates a new one. Nothing is lost, because without an account your chat history and saved plans live on your device.
  • A random chat ID is still sent alongside it. It is created by the app, separate from the analytics install ID, and kept in the iOS Keychain, so it survives deleting and reinstalling the app. On Android and older versions of the app, which don't use the anonymous account yet, it takes the account's place for usage limits.

An optional account, if you log in

Logging in is optional: you can browse, chat with Hulli and book without it. On icebreakerapp.is an account is needed to save a chat or turn your plan into an itinerary; in the app it lets you keep the chats and itineraries you save and see them again when you log in. If you create one, Supabase stores for us:

  • Your email address and password. The password is stored hashed (scrambled) by Supabase's log-in service; nobody at Icebreaker can read it.
  • Your name and phone number, only if you add them to your profile.
  • The chats and itineraries you save: the conversation, the trip settings you chose (dates, number of travellers, budget, interests) and the places you picked.
  • Your account id on your device's row in the device list while you are logged in to the app (see “Push notifications and the device list” below).

We use it only to run your account, and keep it until you delete it. To delete the account, your profile and everything you saved, use “Delete your account” on your dashboard, or email hello@icebreakerapp.is. The log-in, sign-up and password-reset forms on the website use Cloudflare Turnstile to keep bots out (see §4).

Usage limits

To stop abuse and keep costs under control, every request to Hulli, the trip planner, stop swaps and in-app bookings is counted before it is handled. We count per anonymous account (or random chat ID), per hashed IP address, and in total for everyone. Each counter is stored in our database with an expiry: hourly counters expire at the end of the hour and daily ones at the end of the day (UTC), and expired counters are deleted. On the website, Hulli messages are counted per hashed IP address in 10-minute and daily windows, and those counters are deleted after two days; the booking sheet is counted per hashed IP address and per a random id it keeps in your browser's local storage.

Push notifications and the device list

To send notifications, such as the morning weather and what to wear, and northern lights alerts, we keep a list of app installs in our Supabase database, one row per install. Newer versions of the app update their row each time they open, with:

  • The push token Google's Firebase Cloud Messaging gives your device and, on iPhone, the matching Apple push token. These let us address a notification to your phone and nothing else.
  • The random chat ID described above, used as the row's id, so reinstalling the app updates the same row instead of adding a new one.
  • Whether you allow notifications, your device model, operating system version, app version, language, time zone and region setting, and when the app was first and last opened.
  • Your account id, if you are logged in to an Icebreaker account. Logging out removes it.

The app keeps its row up to date even if you haven't allowed notifications, so the list shows that you haven't; we only send notifications to devices that allow them. The row holds no name or contact details, and no location unless you allow it (see below). We also log each notification we send (its text and how many devices it reached), without recording who received it.

If you allowed notifications in an earlier version of the app, which used OneSignal, we copied your push token, device model, operating system and app version, language, time zone, country and the dates you first and last opened the app from OneSignal's export into this list, so your notifications keep working. We did not copy IP addresses. We no longer use OneSignal and have deleted our data there.

Notifications about your area

If you allow Icebreaker to use your location, the app sends us your approximate location so the notifications we send can be about where you are, for example today's weather and what to wear. Before it leaves your phone, your location is rounded to about 1 km, so we never store your exact position. We also store the name of the nearest town (for example “Kópavogur”), which your phone looks up through Apple's location services.

This approximate location is stored together with your device's notification registration. If you are logged in, it is also linked to your account. It is updated when you have moved more than about 1.5 km. If you have allowed location access “Always”, this can happen while the app is closed.

We use it only to decide what each notification says. To find out the weather for your area, we send the coordinates of the area, not anything that identifies you, to our weather provider, Open-Meteo. We don't sell your location, we don't use it for advertising, and we don't share it with anyone else, apart from Supabase, which hosts our database.

To stop sharing it, turn off location access for Icebreaker in your iPhone's Settings. The app then deletes the saved location on your phone and on our servers the next time it is opened. If you stop using the app, your device record, including its location, is deleted automatically after 180 days.

What you send to Hulli and the trip planner (sent to Anthropic)

Hulli, the AI chat, and the trip planner are built on Anthropic's Claude. Before your first chat message, the app asks for your agreement, and nothing you write to Hulli is sent until you give it. If you say no, the rest of the app works as normal.

  • Hulli chat: the recent conversation (at most the last 20 messages) goes to our chat function, which looks up places in our own venue database and forwards the conversation to Anthropic to write the reply. Please don't put personal or sensitive information in the chat.
  • Trip planner: your interests, the regions you picked, the number of days, the first day of your trip and any wishes you typed are sent to our itinerary function and on to Anthropic, which picks places from our database. This includes the suggested itinerary the app builds from your onboarding answers. The trip planner doesn't ask for agreement first, because these choices don't identify you: they are only used to build the plan you asked for.
  • On icebreakerapp.is: Hulli and the trip planner on the planning page work the same way. The whole conversation, not only the last 20 messages, goes through our website chat function to Anthropic, together with the trip settings you choose (dates, number of travellers, budget, rental car, where to stay, interests and regions). The website has no separate agreement step: sending a message is what starts it.
  • Swapping a stop: the stop being replaced, its region and type, a short summary of that day and any wishes you typed are sent the same way.
  • Not sent to Anthropic from the app: your location, your party size, your anonymous account, your chat ID, your install ID or anything else about you. For tours in a plan, the app checks availability for your trip days with TourDesk (see §4).
  • Chat history and saved plans, without an account, are stored only on your device. Chat can be wiped with “Clear chat”, and plans can be deleted in the app. We keep no copy of either on our servers. If you log in and save a chat or an itinerary, it is kept in your account until you delete it (see “An optional account” above). Our functions keep no copy of the requests, apart from the AI analytics described next.
  • Conversations and plans also go to PostHog's AI analytics. Our website chat function sends each turn of a conversation on icebreakerapp.is (your messages, Hulli's replies, the trip settings it was given and the place searches it ran, with timing and token counts) to PostHog, so we can see where the planner goes wrong. The app's trip planner does the same with each plan request (the days, the first day, interests, regions and any wishes you typed) and the plan it returns. Website conversations are keyed to the chat's random id, and app plan requests to your anonymous or logged-in account id, never to your name or email. Both are sent from our servers, whatever you answer on the consent banner. The app's Hulli chat does not do this.
  • Function logs record timing, token counts, cost and a request id per request, not the text of your messages. If something goes wrong, the error log can include the raw reply the model wrote.

Anonymous product analytics, inside the app (PostHog)

We use PostHog inside the app to understand how it is used in aggregate: which features people open, how long the app is in the foreground, which screens get touched, and whether common flows fail. PostHog stores:

  • Anonymous events (the screen you opened, the button you tapped, whether you agreed to AI use, etc.).
  • When you start a booking, the tour, the date you pick, the number of guests and the price; when you choose a venue, which one; when you generate a plan, the interests, regions, trip dates and party size you picked.
  • Device-level metadata (OS version, app version, screen size, language, country at IP-level).
  • A randomly-generated install ID, a UUID created the first time you open the app. It is not tied to your name, email, phone number, your anonymous account or your chat ID.

We do not enable PostHog session replay, do not capture form input, do not send the text of your chat messages, and do not attach your name, email, or any contact information to events. Icebreaker has none of those to attach. PostHog data is hosted in PostHog Cloud's EU region.

Anonymous product analytics, on icebreakerapp.is (PostHog)

The website also uses PostHog to understand how the trip planner, chat and itinerary pages are used in aggregate: which features get opened, where people drop off, and whether common flows fail. PostHog stores:

  • The page you visited, when, and how long you stayed.
  • Anonymous product events, such as picking a place, answering a question in the chat, editing or saving an itinerary, or clicking a Book link. These carry ids and counts, never the text you typed or a place's name. (The conversation text the chat function sends from our server is described under Hulli above.)
  • Device and browser type, screen size, language, country at IP-level.
  • A randomly-generated browser id, so a single visitor isn't counted as many.

If you sign in to save a chat or itinerary, this id is not linked to your account: PostHog on the website never receives your email, name or account id, even signed in. Same as in the app: no session replay and no form input capture. PostHog loads with consent denied by default and is controlled by the same banner as Google Analytics below: click "No thanks" and it records nothing about you. PostHog data is hosted in PostHog Cloud's EU region.

Cookieless visit counts, on icebreakerapp.is (Plausible)

We also count visits with Plausible, which uses no cookies. It records the page address, the site that sent you, your browser and device type, your country, and clicks on outbound links and form submissions. It does not store your IP address and keeps nothing that identifies you or follows you between days. It loads through Google Tag Manager on every page, whatever you answer on the consent banner. Plausible is hosted in the EU.

Page views for our social media reporting, on icebreakerapp.is (Metricool)

We run our social media accounts with Metricool, which also counts visits to the website, so we can see which posts bring people here. For each page you open, it receives the page address, the site that sent you and the size of your browser window, and, as with any request your browser makes, your IP address. It sets no cookies and gives your browser no ID. Metricool says it keeps IP addresses in a form that identifies you for no more than 36 hours before deleting or anonymising them. Like Plausible, it counts every page view, whatever you answer on the consent banner.

Anonymous web analytics, on icebreakerapp.is (Google Analytics 4)

The website at icebreakerapp.is uses Google Analytics 4 to count pageviews and to attribute visits to the QR codes, print ads, and referrers that brought them in. GA4 stores:

  • The page you visited, when, and how long you stayed.
  • Device and browser type, screen size, language, country at IP-level (Google truncates the IP before storage).
  • UTM tags from the URL, the tracking labels on our own QR codes and campaign links, so we can tell which channel a visit came from.
  • A randomly-generated client ID cookie, so a single visit isn't counted as many.

Google Analytics loads with consent set to denied by default. Google Tag Manager, the script that loads it, is fetched on every page before you choose, so Google receives your IP address. Until you click “OK, count me” on the consent banner, GA4 sets no cookies and records no visit, although Google's Consent Mode may send cookieless pings while consent is denied. Click “No thanks” and the site works exactly the same. You can change your mind by clearing cookies for icebreakerapp.is, or by opening browser dev-tools and running localStorage.removeItem('icebreaker-consent'). The app itself is unaffected either way: it does not use Google Analytics.

Advertising measurement, on icebreakerapp.is (Meta Pixel)

The website also loads the Meta Pixel so we can tell which of our own ads and posts actually bring people here, and so Meta can show Icebreaker ads to people who look likely to want it. The pixel sends Meta:

  • The page you visited and when, as a PageView event.
  • Which outbound links you click: the App Store or Google Play buttons, a “Book here” button, or our email address. We send Meta the name of the thing you clicked, so we can tell which ads lead to downloads and bookings rather than just visits. Not who you are, and never the content of anything you type.
  • Some clicks we did not ask for. Once you agree, Meta's pixel may also record button clicks on its own, without us configuring them, as an automatic SubscribedButtonClick event. We do not choose which ones. We are listing it because it happens, not because we wanted it.
  • Your IP address and browser user-agent, which Meta uses to match the visit to a Facebook or Instagram account if you have one.
  • An _fbp cookie in your browser: a randomly-generated browser ID that lets Meta recognise the same browser on later visits.

This one is different from GA4, and we would rather say so plainly: it is advertising data, not an anonymous headcount. Meta can link it to your Facebook or Instagram profile.

The pixel does not load at all until you click “OK, count me”. That one button turns on both the headcount above and this pixel. Click “No thanks” and the script is never fetched, no _fbp cookie is set, and Meta is never told you were here. Same opt-out as above: clear cookies for icebreakerapp.is, or run localStorage.removeItem('icebreaker-consent').

The app itself contains no Meta SDK and no advertising tracker of any kind.

The website itself (hosting, listings, booking)

icebreakerapp.is is hosted by Netlify, which receives your IP address with every page request and uses Netlify's performance measurement (RUM) to record how fast pages load. The site's fonts are served from icebreakerapp.is itself, not from Google Fonts. The home page's opening animation loads its player from cdnjs, so cdnjs also sees your IP address.

The listings on the site (places, events, fun facts, phrases, road signs and the rest) are read by your browser straight from our Supabase database, using its public, publishable key. So Supabase sees your IP address and browser type when you open those pages, as it does for the app. Reading the listings writes nothing to it. The site writes to it only if you log in (your account and what you save) and to count usage, as described under Usage limits.

Some pages load data from elsewhere, and each of those services sees your IP address too: the aurora and road-condition pages ask our own API server on Fly.io; the fuel prices page reads the Gasvaktin price feed from GitHub; the trip planner reads NOAA's northern lights (Kp) forecast and the Icelandic Met Office's weather stations, forecasts and warnings straight from your browser; and event and venue photos load from wherever they are stored, which is our Supabase storage or the server of the site they were listed on, such as the venue, the organiser or the ticket seller.

The Book buttons open a booking sheet on the page. It asks TourDesk for the tour, its dates and its prices through our booking function on Supabase, the same one the app uses, and sends the booking details (the tour, time slot, number of guests and pickup) the same way; the tour's photos load straight from TourDesk's servers. Your browser then moves to TourDesk's own checkout page, where you enter your name, email and card details. Those go to TourDesk and its payment provider, never to us.

QR code scans, counted on our server

Our printed QR codes point at short addresses on icebreakerapp.is (/s, /p, /f and /g). When you scan one, our API server counts the scan and sends you on to the download page. Older codes that point straight at the front page are counted the same way, once per browser tab, when the page opens. Each count holds the code (or, for the older codes, the campaign tags), the time, and whether the phone is an iPhone, an Android or something else, read from the browser's user agent. No IP address, cookie or ID is stored with it, so a count cannot be traced to a person, and it works whether or not you answer the consent banner.

3 · What we don't collect

  • Your identity, unless you log in. Without an account we don't know who you are: no name, email address, phone number or password, and no social login. The anonymous account described in §2 isn't tied to you. If you choose to log in, we keep what is listed under “An optional account” in §2.
  • Your payment details. The app doesn't take payments itself. When you book a tour or activity, the app sends the booking details (the tour, time slot, number of guests and pickup place) through our booking function to TourDesk, and TourDesk's own secure checkout page opens inside the app. Your name, email and card details are entered there and go to TourDesk and its payment provider, never to us. On icebreakerapp.is it works the same way, through the same booking function, and the checkout opens in your browser.
  • Advertising IDs, in the app. We do not read your IDFA / GAID, and the app contains no advertising SDK. We never sell data to data brokers. The website is the exception, and we would rather flag it than bury it: icebreakerapp.is loads the Meta Pixel if you opt in on the consent banner (see §2). That is the one place where advertising data leaves us.
  • Session recordings or form input for analytics. PostHog session replay is disabled and form input is not captured. The only typing that leaves your device is what you send to Hulli or the trip planner and, if you log in, your account details (email, password, and any name or phone number you add) and the chats and itineraries you save. Website chat conversations and app trip-planner requests also reach PostHog's AI analytics, as described in §2.
  • Children's data. Icebreaker is not designed for users under 13. We don't knowingly collect data from anyone we have reason to believe is a child.

4 · Who we share data with

We do not sell your data. The only third parties that ever see any of it:

  • Anthropic (Claude): receives your chat messages to Hulli and your trip planner requests, as described in §2, and returns the reply. Processed under Anthropic's commercial API terms, which do not allow Anthropic to train its models on that data. Governed by Anthropic's Privacy Policy.
  • Supabase: hosts our venue database, the optional accounts and what you save in them, the anonymous accounts, the usage counters and the functions that run Hulli, the trip planner and bookings, so those requests pass through Supabase's infrastructure. It also stores the device list, including the rounded location and town name if you allow location for notifications (see §2). The website reads its listings from the same database, so Supabase also sees website visitors' IP addresses. Operates as a data processor on our behalf.
  • TourDesk: when you book a tour or activity, the booking details (tour, time slot, guests, pickup) go to TourDesk through our booking function, from the app and from icebreakerapp.is, along with the details you enter at checkout. The app also asks TourDesk which tours are available on the days of your plan. TourDesk handles the payment under its own privacy policy.
  • Mapbox: draws the map. Mapbox receives your IP address, device data and the map area you are looking at, and, if you have granted location permission, location telemetry.
  • Google (Firebase Cloud Messaging): the app registers your device with Google's Firebase Cloud Messaging, which gives it a push token and receives your device model, operating system version and IP address. We keep that token in the device list described in §2 and send each notification to it through Firebase, which delivers it to iPhones through Apple's push notification service. No name or contact details are attached. Governed by Google's Privacy Policy.
  • Apple and Google: if you install Icebreaker through the App Store or Google Play. On Android the app also uses Google Play Services for location. On iPhone, if you allow location, your phone looks up the name of the nearest town through Apple's location services, for the notifications described in §2. Their handling is governed by their respective privacy policies.
  • Google (Tag Manager and Analytics): every page on icebreakerapp.is loads Google Tag Manager, so Google sees your IP address. If you have opted in via the consent banner, GA4 also receives the anonymous pageview + UTM data described in §2. Governed by Google's Privacy Policy. The app never sends anything to Google Analytics.
  • Meta (Facebook / Instagram): when you browse icebreakerapp.is and have opted in on the consent banner, the Meta Pixel sends the pageview described in §2, together with your IP address and user-agent. Meta may match this to your Facebook or Instagram account and use it to target ads. Governed by Meta's Privacy Policy. The app never loads the pixel.
  • Fly.io: hosts our API server in the EU region. The website calls it too, for the aurora forecast, the road conditions, the fuel stations and the QR scan counts described in §2. Operates as a data processor on our behalf.
  • PostHog: receives the product analytics described in §2, from the app always and from the website once you consent, plus the website chat conversations and app trip-planner requests our functions send it (§2). The product analytics are not linked to your name, email or account; the trip-planner requests carry your account id. Hosted in PostHog Cloud's EU region. Their handling is governed by their Privacy Policy.
  • Plausible: counts visits to icebreakerapp.is without cookies, as described in §2. Hosted in the EU. Governed by Plausible's Privacy Policy.
  • Metricool: receives the page views described in §2, with your IP address, from every visit to the website, whatever you answer on the consent banner. Metricool Software S.L. is based in Madrid, Spain, and operates as a data processor on our behalf. Governed by Metricool's Privacy Policy.
  • Cloudflare (Turnstile): a bot check on the website's log-in, sign-up and password-reset forms. It sees your IP address and browser details. Governed by Cloudflare's Privacy Policy.
  • Netlify and cdnjs: Netlify hosts icebreakerapp.is and measures page-load performance (RUM); cdnjs serves a script on the home page. Both see your IP address.
  • GitHub and image hosts, on the website: the fuel prices page reads the Gasvaktin feed from GitHub, and some event and venue photos load from the venue's, organiser's or ticket seller's own servers. Each sees your IP address and nothing else from us.
  • Weather, currency and aurora data: the app asks Open-Meteo for weather, sending the coordinates it needs weather for, and Frankfurter for currency rates. Both requests go straight from your device, so these services also see your IP address. In the app, aurora data comes from NOAA through our own API server, so NOAA never sees you. On the website, the trip planner reads NOAA's Kp forecast and the Icelandic Met Office's weather and warnings straight from your browser, so those services see your IP address.

5 · How long we keep things

  • Anonymous accounts: deleted automatically after 30 days without use, together with their sessions (including the IP address and device type recorded with them).
  • Usage counters (anonymous account or chat ID, hashed IP): hourly counters expire at the end of the hour and daily ones at the end of the day (UTC); expired counters are deleted.
  • Chat history and saved plans: without an account, only on your device, until you clear or delete them, or delete the app. Saved to an account, until you delete them or the account.
  • Optional accounts: your email, hashed password and any name or phone number you add, until you delete the account.
  • Chat and trip planner requests: we keep no copy on our servers. Anthropic's own retention is governed by its API terms. The conversations and plan requests sent to PostHog's AI analytics are kept under our PostHog data retention settings.
  • Website chat counters (hashed IP): deleted after two days.
  • Supabase request, function and sign-in logs: kept by Supabase for at most 7 days, then deleted.
  • Notifications: a row in our device list is deleted when Firebase tells us the app has been uninstalled (we learn this the next time we send a notification), or after 180 days without the app being opened, together with any location stored with it. That location is deleted sooner if you turn off location access, the next time the app is opened. The log of sent notifications is kept for 1 year. Google keeps the push token for as long as it is in use.
  • Rate-limit / abuse counters on our API server: in-memory. Rate-limit window resets each hour; abuse cooldown lasts up to 30 minutes. Everything is lost on server restart and is never written to disk.
  • API server access logs: a request id, method, request path and status code. No IP address, message bodies or coordinates. Retained at most 7 days, then deleted.
  • QR scan counts: the code or campaign tags, the time and the phone type, kept for as long as we use the counts. Nothing in them points to a person.

6 · Where data is processed

Our API server runs in Fly.io's Amsterdam region (EU). PostHog analytics events stay in PostHog Cloud's EU region. Our venue database, the optional and anonymous accounts, the usage counters and the chat, trip planner and booking functions run on Supabase in Ireland. Chat messages and trip planner requests are processed by Anthropic on its own infrastructure, which is primarily in the United States, and push notifications are delivered through Google's Firebase Cloud Messaging, which runs on Google's global infrastructure. Where data leaves the EU / EEA, it is protected by the safeguards in the provider's data processing terms, such as the EU Standard Contractual Clauses.

7 · Why we're allowed to use it (legal bases)

  • Your consent: sending your chat messages to Anthropic from the app, notifications, location (including the rounded location we store so notifications can be about your area), and analytics and advertising cookies on the website. You can withdraw it at any time: stop using Hulli, turn off notifications or location in your phone's settings, or clear the consent on the website as described in §2. Withdrawing doesn't affect what was already done.
  • Providing the service you ask for: showing places, weather and maps, building your plan with Anthropic's Claude (on the website, when you send a message), handling a booking you start, and running the account if you create one.
  • Our legitimate interests: the anonymous account, usage limits and hashed IP addresses, to keep the service secure and stop abuse and runaway costs; server logs, to keep things running; anonymous in-app analytics, cookieless website visit counts (Plausible) and the website chat analytics, to learn which features are useful and where they go wrong; Metricool's page views, to see which of our social media posts bring people to the site; and the device list, to send the notifications you allowed and to know which devices allow them. We keep these to the minimum described above, and you can object (see §8).

8 · Your rights under GDPR

Because Icebreaker is built by an Icelandic company and EU / EEA visitors use the app, the GDPR applies to us regardless of where you live. Your rights:

  • Right of access: ask what we hold about you. (Without an account, the honest answer is almost always "nothing tied to your identity".)
  • Right to erasure: ask us to delete whatever we do hold. The quickest route is on your own device: “Clear chat”, delete your saved plans, or delete the app. If you have an account, “Delete your account” on your dashboard deletes it and everything saved in it. The anonymous account is then deleted automatically after 30 days, and your row in the device list as described in §5.
  • Right to object to processing based on our legitimate interests.
  • Right to withdraw consent at any time, as described in §7.
  • Right to data portability, where it applies.
  • Right to lodge a complaint with the Icelandic Data Protection Authority, Persónuvernd, or with the supervisory authority of your own EU / EEA country.

Without an account we don't know who you are, so we may not be able to find your data from a request alone. If you want us to act on a specific anonymous account or chat ID, tell us and we'll explain how to find it. To exercise any of these rights, email hello@icebreakerapp.is. We respond within 30 days.

9 · Children's privacy

Icebreaker is intended for adults visiting Iceland and is not directed to children under 13. We do not knowingly collect personal information from children. If you are a parent or guardian and you believe your child has provided us with personal information, contact us and we'll address it.

10 · Security

Our API server and our Supabase functions are served exclusively over HTTPS. Standard transport security applies to every request your device makes to us and to the weather and currency APIs. The anonymous account's session is kept in your device's secure storage. Passwords for optional accounts are stored hashed. No system is perfectly secure, but we hold no payment data, accounts are optional, and without one your chat history and plans live only on your device, so there is very little to leak in the first place.

11 · Changes to this policy

When something material changes, we update this page and bump the "Last updated" date at the top. If a change meaningfully expands what we collect, we'll surface a notice in the app the next time you open it.

12 · Contact

Icebreaker ehf.
Reykjavík, Iceland
hello@icebreakerapp.is

← Back to Icebreaker