TapNomad
CoveragePricingFAQ

Privacy Policy

Effective 24 October 2026 · Operated by Rabotto (Timo Voutilainen), business ID 3646938-8, Arometsänkatu 35 A 1, 15680 Lahti, Finland

TapNomad is built so that we know as little about you as possible. The app has no user accounts, no advertising, no third-party analytics SDKs and no tracking. This policy explains the little that remains.

1. Who we are

TapNomad is operated by Rabotto, a sole trader registered in Finland (business ID 3646938-8) (“we”, “us”). We are the data controller for the processing described here.

Contact for privacy matters: privacy@tapnomad.app

2. The short version

  • No account. The app does not ask you to create a TapNomad account or provide your name or email.
  • Your location is used for lookups and guidance. The app uses it to show where you are, to find places and water points, and to guide you. Coordinates needed for a lookup go to our server with the request and are not stored. If you turn on usage statistics and a lookup finds no covered place, your phone’s geocoding service (Apple or Google) receives the coordinates to find the place name. Directions sends the destination to Apple Maps or Google Maps.
  • No advertising, no trackers. The app contains no ad networks and no third-party analytics SDKs. Usage counters exist only if you opt in, go only to our own servers, and carry no user or device identifier (see 3.4).
  • Purchases are handled by Apple on iPhone and by Google Play on Android. We do not receive your full card number.
  • Public content requests carry no account and no name. When the app fetches online water-quality answers, public map tiles or the pack catalog, our servers receive your IP address and the requested content.
  • One exception, and only for Premium downloads and their automatic updates. To download an offline pack or update its water data, the app asks our server for permission. It sends a random installation identifier, a random RevenueCat app-user identifier and the pack name. We use these to check the subscription and enforce download limits. Granted requests are recorded as described in section 3.2.

3. What data is processed, and why

3.1 Location

If you grant location permission, the app uses your device’s location to show your position on the map, provide route guidance, and find the nearest place and water points.

  • Position display, route guidance and working out which country you are in before a download over mobile data happen on your device.
  • When you tap “Use my location” or view nearby water points, the app sends your coordinates in that one request to our server, which answers it and does not store them. We keep no history of where you have been. The coordinates travel in the request body, never in the request address, so they do not appear in our hosting provider’s request log either.
  • If a location lookup finds no covered place and usage statistics are on, the app sends your coordinates to the phone’s geocoding service to obtain a place name (see 3.4).
  • Directions opens an Apple Maps link on iPhone or a Google Maps link on Android. The link includes the destination’s coordinates and, on iPhone, its name. It may open a maps app or your browser. The provider’s privacy policy applies.
  • The app remembers your last map position on the device only, so the map reopens where you left it. It is never uploaded.
  • The permission is optional: search and all water-quality information work without it.
  • You can revoke the permission at any time in your device settings.

Legal basis: consent (the operating system permission), GDPR Art. 6(1)(a).

3.2 Content requests (server logs)

When the app loads water-quality data, map tiles or offline packs, your device makes requests to our infrastructure: a Supabase database in the United States (AWS us-east-1) and Cloudflare storage and CDN (bucket location: eastern North America). This infrastructure stores water-quality data and map content. It also processes request information and keeps the operational and download records described below. Download records link a random identifier to the packs requested.

Like every web server, that infrastructure necessarily processes your IP address and the content you requested, and the providers keep short-lived operational logs for security and reliability. We do not use those logs to identify or profile anyone. Identified offline-download records are described below.

To keep the service available for everyone, our API also keeps short-lived request counters (rate limiting). The database counters use a salted hash of the IP address and are cleared by an hourly cleanup once their current window is more than one hour old. The request handler also keeps a temporary in-memory counter keyed by the address. They are used for nothing except slowing down abusive traffic.

Because these providers are outside the EEA, that transient log processing is a transfer to a third country. It happens under each provider’s data processing agreement incorporating the European Commission’s Standard Contractual Clauses.

If you ask for a map, we count the place, not you. Tapping “Ask for this map” on a destination we do not cover yet sends us that place’s name, on its own. There is no identifier attached, so we can count that a place was asked for a hundred times and still have no way to know whether that was one person or a hundred. We keep a running tally per place, plus when it was first and last asked for and when we delivered it, so we can tell how quickly we respond. Your device remembers which places you asked for, so the button can say “Asked”; that list stays on the phone.

Offline pack downloads and water-data updates require download permission. The water-quality database is what this service is, and it used to be downloadable by anyone who guessed a file name. Pack files now live in private storage, and the app has to ask our server for a short-lived, single-file permission before each download. That request carries a random identifier your app installation created for itself, the random RevenueCat app-user identifier, and the name of the pack you are downloading. The app also requests download permission automatically when it needs to update a downloaded pack’s water data. These requests send the same installation identifier, RevenueCat app-user identifier and pack name as a manual download. Failed updates may be retried. We record one row per granted request (identifier, a quota key based on the purchase, or the RevenueCat app-user identifier in the cases described below, pack name, timestamp) purely to enforce a daily and monthly download limit and to cut off a leaked subscription. The rows are scheduled for deletion in a daily cleanup once they are more than 31 days old. The identifier is not your device id or an advertising id: it is created inside the app. Deleting the app removes its local copy of the identifier. It does not delete records held by us or our providers.

Download permission and block lists. We keep identifiers, notes or reasons, and dates added to these lists to allow support exceptions and developer tests, or to stop misuse. Entries do not expire automatically. We keep support permission entries while the exception is needed. We remove test entries as soon as the test ends. We keep block entries as long as the misuse risk they address exists.

Legal basis: legitimate interest in operating a secure, functioning service and in protecting our database against bulk extraction, GDPR Art. 6(1)(f); for the entitlement check itself, performance of a contract, GDPR Art. 6(1)(b).

For the curious: app requests and external services

The list below explains requests for app content and the services described in this policy.

  • search with q: the city or country you typed, sent to our server to find matches. Not stored, not counted.
  • search with lon, lat: your coordinates, when you tap "Use my location", to find the nearest covered place. Answered and discarded.
  • refill with lon, lat, limit: your coordinates, when the map asks for nearby water points (with layer=shops, for nearby shops that likely sell bottled water). Answered and discarded.
  • The three requests above carry their values in the request body, not in the request address, because our hosting provider's request log records addresses and never bodies.
  • answer/<city>: the city page you opened, by its public name.
  • Map tiles: plain file downloads from our CDN. The request names the tile, nothing about you.
  • The public offline/manifest.json catalog lists available packs, their sizes and water-file hashes. The app requests it for browsing packs and automatic update checks. Requests include a timestamp to avoid cached responses and may include an ETag for its saved catalog copy. They send no installation or RevenueCat identifier.
  • download-token asks for permission to download an offline pack or update its water data. The app sends this request for manual downloads and automatic water-data updates. It carries the random installation identifier, the RevenueCat app-user identifier and the pack name. Granted requests use the same download limits and 31-day retention rule. Premium only. Our server records your installation identifier and a quota key. For store subscriptions, that key uses the store and the earliest TapNomad subscription purchase date RevenueCat reports for that store. If those purchase details are unavailable, or a support exception allows the download, the key can instead be the RevenueCat app-user identifier. Answered with links that carry your installation's identifier and a signature and expire in 10 minutes. Within those minutes the link itself is the key: anyone holding it could fetch that one file, which is why the app never shows or shares it.
  • Offline pack files themselves, from downloads.tapnomad.app, each with the link above in its address. Without a valid link the file is not served to anyone. Request logging is switched off on that service, so the identifier in the address is not kept there.
  • events: the opt-in usage counters of section 3.4. Sent only with your consent, in batches; contents listed below.
  • request-pack: sent only when you tap "Ask for this map" on a place we have no offline map for. It carries the name of that place and nothing else: no identifier, no coordinates, not even your app language. We count how many times each place was asked for so we build the most-wanted maps first.
  • One call to your phone's own geocoding service (Apple or Google, not us) when a location lookup finds no covered place and the counters are on, described in 3.4.
  • When the app starts with subscriptions enabled, RevenueCat creates or reads a random identifier stored on your device and checks subscription information. This also happens if you have not subscribed. On iPhone, the request can include Apple's identifier for vendor (IDFV), section 3.3.
  • Purchases through the store (Apple on iPhone, Google Play on Android), and the purchase receipt (on Android, the Google Play purchase token) to RevenueCat, section 3.3. Crash reports to Sentry only with the separate consent of section 3.6.
  • Directions opens an Apple Maps link on iPhone or a Google Maps link on Android with the destination's coordinates and, on iPhone, its name (section 3.1).
  • Source links you open yourself go to that source's website in your browser. The website's own policy applies.

3.3 Purchases (Premium subscription)

Premium subscriptions are sold through Apple’s App Store on iPhone and Google Play on Android. The store processes your payment. We do not receive your full card number. We receive purchase records needed to manage subscriptions, accounting and support. Google Play may also make buyer information available to us under its payments privacy policy. Our subscription processor RevenueCat uses a random RevenueCat app-user identifier with the store’s purchase record (Apple’s receipt, or Google Play’s purchase token) to activate your subscription across reinstalls. RevenueCat uses this identifier to associate subscription information with an app installation. It does not contain your name. When the app starts with subscriptions enabled, RevenueCat creates or reads this identifier on your device and checks subscription information. This also happens if you have not subscribed. On iPhone, RevenueCat also receives Apple’s identifier for vendor (IDFV) in request headers when it is available. RevenueCat uses it during receipt validation. RevenueCat keeps operational request logs for monitoring and troubleshooting for up to 45 days. These logs may include the RevenueCat app-user identifier and, on iPhone, the IDFV.

Legal basis: we process subscription data to provide your subscription, under GDPR Article 6(1)(b). Where bookkeeping law requires us to retain personal data, the basis is a legal obligation under Article 6(1)(c).

3.4 Usage statistics (opt-in)

If you turn on Share usage and reliability stats (off by default), the app counts a small, fixed set of events: the app was opened, a city page was viewed, a lookup or search found no data, an offline pack was downloaded or failed to download, an answer was served from an offline pack, guidance started, arrived, fell back or was reported blocked, a Premium subscription was active, and a server request failed. Each count carries the event name, any label listed below, the app language and the platform (iOS/Android), and is stored as a daily total in our own database, with no user identifier, no device identifier, no IP address and no time more precise than the calendar day. When a location lookup finds no covered place near you, the app asks your phone’s built-in geocoding service (Apple on iOS, Google on Android) for a place name and counts that name, so we know where coverage is missing; your coordinates go only to that system service, never to us, and this too happens only while the toggle is on. We store these counters as daily totals without user or device identifiers. Supabase hosts the database for us. We use the totals to decide which places need better data and to find where the app fails. Usage totals are scheduled for deletion in a monthly cleanup once they are more than 24 months old. Turn the toggle off at any time to stop immediately; anything not yet sent is discarded.

Legal basis: consent, GDPR Art. 6(1)(a).

For the curious: every counter, exactly

Each stored row is calendar day + event name + label + app language + platform → count. The label ("slug") is listed per event; where none is listed, the event has no label at all. This is the complete set: the database rejects anything else.

  • app_open: the app was opened.
  • city_opened: a city page showed an answer. Label: the city.
  • answer_unknown: a city page had no verdict. Label: the city.
  • search_no_result: a text search found nothing. No label: the event does not include what you typed.
  • nearest_no_place: "Use my location" found no covered place. Label: the place name from your phone's geocoder, e.g. fi-jarvenpaa. Never coordinates.
  • pack_downloaded / pack_download_failed: an offline pack finished or failed. Label: the pack.
  • offline_answer_served: an answer came from a downloaded pack. Label: the city.
  • nav_started, nav_arrived: guidance started / reached the water point.
  • nav_fallback: routing was not possible and guidance fell back to compass mode. Label: the technical reason, e.g. no_path.
  • route_broken_tap: you tapped "Route blocked?".
  • premium_active: a subscription was active, at most once per open.
  • api_error: a server request failed. Label: the endpoint and status class, e.g. answer_5xx.

3.5 Data stored on your device

The app stores preferences, recent places, map position and offline files on your phone. It also stores the identifiers described in sections 3.2 and 3.3. Those identifiers are sent as described there. Usage statistics include the app language if you turn them on. Deleting the app removes its local working data. It does not delete records held by us or our providers.

To choose a calm moment for the store’s rating request, the app counts answers temporarily in memory. It does not save that count between app runs. You can also choose Rate TapNomad in Settings to open the store.

For the curious: everything on the device, exactly
  • Preferences: language, appearance (light/dark), avoid-stairs, and the two consent toggles (usage stats, crash reports).
  • A flag that onboarding was completed.
  • The last five places you opened (name and verdict, for the Recents list).
  • Your last map position, so the map reopens where you left it.
  • Downloaded offline packs (map tiles, water data, walking network) and a local copy of the pack catalog, so the offline screens work with no network.
  • For a city that downloads in several parts, which of its cities you picked it by, so the Downloaded list names it the way you did.
  • Local records used to check offline water data for updates. They include file hashes, publication and download times, update-check and retry times, automatic download-attempt counts, and flags for interrupted checks or replacements. Freshness history remains on the phone when you remove packs, so removing and downloading a pack again does not erase what the app knows about an outdated copy. These records are not uploaded.
  • The subscription state RevenueCat last reported, so Premium works offline, and the random RevenueCat app-user identifier (3.3).
  • The places you have asked for an offline map for, so the button can say "Asked" instead of inviting the same tap again.
  • The countries where you allowed manual offline-map downloads over mobile data. The app remembers your answer when it can determine the country. Offline maps lists these countries and lets you clear them. Automatic update checks and water-data updates may use mobile data without asking and do not use these saved permissions.
  • A random identifier created by this installation for offline downloads and water-data updates. It is sent in permission requests and signed file-download links, as described in section 3.2. It is generated on the device, not derived from your phone's identifiers. Deleting the app removes this local copy. It does not delete records held by us or our providers.
  • A flag that remembers when crash-report cleanup is still needed. It stays on your device and is cleared after cleanup succeeds.
  • A technical event log (two files, 512 KB each, newest overwrites oldest) recording app events such as "route computed" for troubleshooting on your device. Coordinates are refused at the writing layer, so it cannot contain locations.

3.6 Diagnostics (opt-in crash reports)

By default the app sends no crash reports or diagnostics; error information stays on your device. If you turn on Crash reports in Privacy & consent, the app sends a crash report when it crashes or hits an error, so we can fix it. A report contains the error and stack trace, your device model, operating system version, app version and app language. Sentry may also include a random installation identifier. Reports go to our error-reporting processor Sentry, stored in the European Union (Germany) and deleted after at most 90 days. You can turn crash reports off at any time. The app closes crash reporting and attempts to delete unsent reports and Sentry’s installation identifier from your device. Previously queued reports may still be sent during shutdown. Once reporting has closed, it can resume on a later app launch if you have turned it back on and cleanup succeeds.

Legal basis: consent, GDPR Art. 6(1)(a).

For the curious: what a crash report contains, exactly
  • The error message and stack trace (which line of our code failed).
  • Device model, operating system version, app version and build.
  • The app's last technical steps before the crash ("breadcrumbs"): which of our server endpoints were called and with what HTTP status. Query strings are stripped before sending, so these can never contain coordinates or search text.
  • Sentry may include a random installation identifier. We do not send it your TapNomad download identifier or RevenueCat identifier.
  • What it does NOT contain: no IP address stored with the event, no location (coordinate-shaped fields are deleted before sending), no searches, no account of any kind.

3.7 Emails you send us

If you write to privacy@tapnomad.app or hello@tapnomad.app, we receive your email address, message and any attachments. We use them to respond and handle your request. Our email provider is Proton AG in Switzerland. We keep these records as long as needed to handle your request and its follow-up. They are not deleted automatically.

We use messages to answer general enquiries under our legitimate interest, GDPR Article 6(1)(f). We use subscription messages as needed to perform the contract, Article 6(1)(b). We process privacy-rights requests to meet our legal obligations, Article 6(1)(c).

3.8 This website

tapnomad.app is a set of static pages served by Cloudflare. It sets no cookies and runs no analytics or tracking scripts. Cloudflare processes your IP address to deliver the pages and to protect them from attacks.

Legal basis: our legitimate interest in delivering and protecting the website, GDPR Art. 6(1)(f).

4. What we do NOT do

  • We do not sell or rent personal data. The recipients in section 5 receive data for the purposes described in this policy. Some process it on our behalf. Apple and Google process data for their own services under their own privacy policies.
  • We do not use advertising identifiers (IDFA/AAID) or cross-app tracking.
  • We do not fingerprint devices or profile users.
  • We do not use cookies in the app.
  • Subscription checks, download limits and abuse checks run automatically. They can stop a download. If you think a download was blocked by mistake, contact hello@tapnomad.app.

5. Data recipients

Recipient Role Location / safeguards
Supabase Database and API hosting for water-quality content; answers nearest-place requests that carry your coordinates transiently (nothing stored); authorizes Premium pack downloads and keeps the 31-day download counters United States (AWS us-east-1); data processing agreement with EU Standard Contractual Clauses
Cloudflare Storage and delivery of map tiles and offline packs, and delivery and protection of this website. Processes IP addresses and request information. The content bucket holds no personal data. Request logging is off on the pack download service. Bucket in eastern North America, served from Cloudflare’s global network; data processing addendum with EU Standard Contractual Clauses
RevenueCat, Inc. Subscription checks at app launch, subscription activation and checks before authorizing offline downloads. Uses a random app-user identifier and store purchase information, including an Apple receipt or Google Play purchase token. Operational request logs may include the app-user identifier and, on iPhone, Apple’s identifier for vendor (IDFV). United States. RevenueCat has confirmed that its data processing agreement applies to all personal data processed on our behalf. Its published agreement still limits its main processor terms to people in the European Economic Area and the United Kingdom. The contractual scope of those terms and transfer safeguards for other users remains unresolved. Covered restricted transfers use European Union Standard Contractual Clauses, with the United Kingdom Transfer Addendum where applicable.
Proton AG Email hosting for support and privacy requests Switzerland
Apple App distribution and payment on iPhone; the phone’s geocoding service (3.4) and Apple Maps for Directions (3.1) Apple’s own terms and privacy policy apply
Google App distribution and payment on Android (Google Play); the phone’s geocoding service (3.4) and Google Maps for Directions (3.1) Google’s own terms and privacy policy apply
Sentry Crash reports, only if you opt in Stored in the EU (Germany); data processing agreement with EU Standard Contractual Clauses

Our service providers process data on our behalf under the agreements described above. RevenueCat’s scope confirmation and the remaining contractual uncertainty are explained in its row. Apple and Google process data for their own services under their own terms and privacy policies.

6. Data retention

  • Location: coordinates in a nearest-place request are processed to answer that request and are not stored; they travel in the request body, which the server logs below do not record. Your last map position lives only on your device.
  • Hosting and delivery logs: retained by our infrastructure providers for a short operational period (days to a few weeks) and then deleted.
  • RevenueCat request logs: kept for up to 45 days for monitoring and troubleshooting. They may include the RevenueCat app-user identifier and, on iPhone, the IDFV.
  • Rate-limit counters: the database counters are cleared by an hourly cleanup once their current window is more than one hour old.
  • Purchase records: retained as long as your subscription is active and thereafter as required by bookkeeping law.
  • Crash reports (if you opted in): deleted after at most 90 days.
  • Usage counters (if you opted in): daily totals only, scheduled for deletion in a monthly cleanup once they are more than 24 months old.
  • Offline download records (Premium only): one row per granted download or update permission, scheduled for deletion in a daily cleanup once they are more than 31 days old.
  • Download permission and block lists: support permission entries are kept while the exception is needed. Test entries are removed as soon as the test ends. Block entries are kept as long as the misuse risk they address exists. Entries do not expire automatically.
  • Support and privacy emails: kept as long as needed to handle your request and its follow-up. They are not deleted automatically.
  • Map requests: a per-place tally with no identifier, kept while the place is uncovered and as a record of how quickly we delivered it.

7. Your rights (GDPR)

You have the right to access, rectify and erase personal data concerning you, to restrict or object to processing, to data portability, and to lodge a complaint with a supervisory authority (in Finland: the Data Protection Ombudsman, tietosuoja.fi). You do not need a TapNomad account. We may hold download records linked to random identifiers, purchase records and messages you send us. Section 6 explains how long we keep each type of record. Contact privacy@tapnomad.app to exercise your rights.

We respond to privacy-rights requests without undue delay and within one month. If the law allows more time, we explain why within that month. You can turn off usage statistics and crash reports in Settings, Privacy. You can withdraw location permission in your device settings. Withdrawing consent does not affect processing that was lawful before withdrawal.

You do not need a TapNomad account or need to give us your name or email to look up water information. Online lookups send the request information described in section 3.2. Location permission is optional. Without it, you can search for a place. Usage statistics and crash reports are optional. Premium requires the purchase and subscription information described in section 3.3. To request a copy of the safeguards used for international transfers, write to privacy@tapnomad.app.

8. Children

TapNomad is not aimed at children and does not ask your age. This policy describes the data processed when you use the app.

9. Changes to this policy

We will update this page when the app’s data practices change and revise the effective date. Material changes will be highlighted in the app’s release notes.

Updated for version 1.0.3: automatic water-data updates for downloaded packs, crash-report cleanup when you turn reports off, emails and this website, the download permission and block lists, and clearer wording about identifiers, recipients and retention.

Updated after version 1.0.3: RevenueCat’s request logs may also include its app-user identifier, and the RevenueCat row now explains what RevenueCat has confirmed about its data processing agreement and what remains unresolved.

PrivacyTermsSecuritySupportContact
Water data from official regulators and utilities. Refill points © OpenStreetMap contributors (ODbL).
Verdicts are informational guidance, not a guarantee. Disclaimer
© 2026 TapNomad is a Rabotto product.