Privacy Policy

Effective date: October 19, 2026

This Privacy Policy describes how the Voyager Maps mobile application (the “App”) processes personal data. On Google Play the App is listed as “Toilet Finder - WiFi Water” (package name com.voyagermap.voyagermobil.voyagermobil); on the Apple App Store it is listed as “Voyager Maps”. The App provides travel-related features such as discovering points of interest, saving places, planning and sharing trips, reporting changes to places, map interaction, guest access, and related communication features.

This Policy also applies to the Voyager Maps website, including cookie-based analytics and consent management used on the website.

Important: This Policy distinguishes between (a) features and processing that are currently active and (b) features that are planned or conditionally enabled in the future. Where a processing activity is not currently active, it is marked as planned / where applicable.

1. Data Controller

The App is operated by an individual developer, who is the controller of your personal data:

• Controller: Kálmán Fekete (Fekete Kálmán), individual developer, trading as Voyager Maps, developer of the App (listed on Google Play as “Toilet Finder - WiFi Water” and on the Apple App Store as “Voyager Maps”)
• Contact email: [email protected]

No data protection officer has been appointed, as none is required. Every request concerning your data can be sent to the email address above.

2. Categories of Personal Data

2/A. Currently active categories

• Account and profile data: name, email address, profile image URL (via social login), social login identifiers (Google, Apple), authentication metadata.
• Optional profile details: phone number, address data, date of birth, gender.
• App language: the language you use the App in, so that emails we send you are written in it.
• Consent records: your choices on the Terms, this Policy, analytics and the newsletter, with the date and the version of the document you accepted or withdrew.
• Location data (with permission): device location for map and nearby features, including one-time or active tracking while a feature is enabled. When you report a place, the App also uses your position to work out how far you were from it; only that distance is stored, not your position.
• Map and preference data: saved places, favourites, preferences and app interaction data needed for core functionality.
• User-generated content: custom places (private or public), descriptions, uploaded images, Wi-Fi details of a place (its network name and, if you add it, its password), visibility depending on your sharing settings. Image metadata (EXIF, including location) is removed when an image is uploaded. If a venue asks us not to show its Wi-Fi password, we delete the stored password and do not accept a new one for that place.
• Reports and proposed changes to places: what you reported or proposed, an optional note to us, the time, your distance from the place, a photo you choose to add to a report that a place is closed, and what became of the report (see section 3/B).
• Trips and sharing: itineraries, their stops and notes, the members of a shared trip and their roles, share links, and the email address of a person you invite to a trip.
• Guest-mode data: a device identifier generated by the App and stored on your device, a guest identifier assigned to it, first/last visit and visit count, and the number of requests that guest session made per hour together with a truncated network prefix, the platform and the app version. See section 3/A.
• Feedback and bug reports: submitted feedback and diagnostic information.
• Analytics and technical data (with consent): in-app events, device and app data, crash reports, performance data, SDK-generated identifiers, and masked screen recordings (section 5/A).
• Server and security data: IP address, user-agent, request time and error information (see section 7).

2/B. Planned or conditionally enabled categories (where applicable)

• Trip cost data: expense entries and cost-related information provided by you.
• Advertising and attribution data (where applicable): identifiers and event data processed subject to legal requirements.
• Billing and transaction data (where applicable): records required for invoicing and accounting.

3. Purposes and Legal Bases of Processing

• Account creation and authentication – performance of a contract
• Core app functionality, including saved places, trips and the App language – performance of a contract
• Trip sharing and invitations initiated by you – performance of a contract; for the person you invite, our legitimate interest in delivering the invitation you asked us to send
• Location-based features – performance of a contract and device permissions
• Reviewing reports and contributing place data to OpenStreetMap – performance of a contract and legitimate interest in keeping the map accurate
• Service emails (security notices, password reset, changes affecting your use of the App) – performance of a contract and legitimate interest
• Newsletter – consent
• Keeping consent records and a list of addresses that must not be emailed – legal obligation (proving consent) and legitimate interest
• Customer support and security – legitimate interest
• Guest-mode operation – legitimate interest
• Preventing abuse, automated bulk extraction and excessive use of our services – legitimate interest
• Billing and legal compliance – legal obligation
• Product analytics, crash and performance reporting and masked screen recordings in the App (PostHog and Firebase, see section 5) – consent
• Advertising and marketing measurement – consent, where required

Where we rely on legitimate interest, you may object to the processing at any time (section 11). We do not make decisions based solely on automated processing that produce legal or similarly significant effects for you.

3/A. Guest Mode and the Device Identifier

The App can be used without an account, in guest mode. So that a guest session is not lost every time the App is closed, the App generates a random device identifier on first launch and keeps it in the device's secure storage. It is sent with the request that creates or renews a guest session, and the server links a guest identifier (in the form G-…) to it.

• It is stored on your device. Deleting the App, or clearing its data, removes it; the next launch generates a new one, and the previous guest session is no longer reachable.
• No device fingerprinting. We do not derive an identifier from your device's technical characteristics (such as the user-agent, language or screen), and a guest session is not linked to your IP address or user-agent.
• Content made in guest mode stays on the device. Places, travel plans and the photos added to them without an account are kept in the App, not on our servers. If you later create an account, they are transferred to it; until then, losing or replacing the device means losing them.
• Traffic is counted, for security only. Because a large part of our map can be read without an account, we record per guest session how many requests it made in a given hour, from which network (the address truncated to its network prefix — IPv4 /24, IPv6 /48 — never the full IP address), and with which platform and app version. This is used to detect and stop automated bulk extraction and abuse, on the basis of our legitimate interest. It is not used for analytics, profiling or advertising.
• Pseudonymous, not anonymous. These identifiers do not contain your name or email address, but under applicable data protection law they are still personal data, and this Policy treats them as such.

The guest token issued to the device is valid for 30 days and is renewed automatically by the App while it is in use, with the same device identifier.

3/B. Reports and Contributions to OpenStreetMap

Much of our map comes from OpenStreetMap (OSM), a public map database. When you report that a place has changed or propose a new place, the report is checked automatically and then reviewed by a person, who may correct it or reject it. Accepted place data is then either written to OSM or left for local OSM mappers as a public note, under our own OSM account and never in your name. You can withdraw a report in the App until it has been reviewed.

• What goes to OSM: only place data — for example type, opening hours, fees, accessibility, whether the place has a toilet or Wi-Fi, the Wi-Fi network's name, and a place's description as approved by the reviewer. A new name and a report that a place is somewhere else (with the position you marked for the place) are left to local mappers as a public note rather than written directly. A place reported as closed for good is marked as closed on OSM when the report was made at the place; otherwise it, too, is left to local mappers as a note. Either way, an accepted report that a place is closed for good first shows in the App for two weeks as “reported closed”, without your name, so that anyone at the place can say it is still open; only then does it take effect and go to OSM. A temporary closure is never sent to OSM: it stays in the App and ends by itself. Nor is a report that a drinking-water place has no water, or has water again: it greys the place on the App's map, or clears it, for everyone at once, without your name, and ends by itself. We look at who made such reports, how long their accounts have existed and how much they have contributed only to spot automated or malicious reports. For a report made at the place, the day of the report is recorded as the day the place was checked on site.
• What never goes to OSM: your name, account, email address, photos, Wi-Fi passwords, the note you wrote to us, your own location, and the town, region and country we fill in for our own use. A place marked as a home never goes to OSM in any form — neither as data nor as a note — even if you share it with other users of the App.
• How reports are weighed: the person reviewing a report sees how long your account has existed, how many of your earlier reports were accepted or rejected, and a reliability score worked out from those outcomes alone. It helps that person decide and spot automated or malicious reports; nothing is decided by it automatically (see section 3).
• What we keep: the report itself, its review and its outcome, linked to your account while the account exists. OSM data is published under the Open Database License and cannot be withdrawn from OSM once published; see section 4.4 of the Terms of Service.

Please do not put personal data (your own or anyone else's) into a place's name or description.

4. Email Communication

We send service emails needed to operate the App, such as password reset, security notices, trip invitations you asked us to send, and information about changes affecting your use of the App.

We send the newsletter only if you asked for it: the box is unticked when you register, and you can change your choice at any time in the App. Every newsletter contains a link that unsubscribes you in one step, without signing in. We record when you subscribed and unsubscribed, to be able to prove your consent.

If a mail server permanently rejects an address, or a recipient marks our email as spam, we put that address on a do-not-email list so that we never write to it again. This list holds only the address, the reason and the date; it is kept even after the account is deleted, because its only purpose is to make sure that address is not written to again.

5. Analytics, Crash Reporting and Product Tools in the App

The App uses PostHog (product analytics, feature flags, surveys and masked screen recordings, see section 5/A) and Google Firebase (Analytics, Crashlytics crash reports, Performance Monitoring and In-App Messaging) to understand how the App is used and to fix errors.

These tools run only with your consent. Until you grant it, they collect and send nothing — the App works exactly the same either way. You can withdraw consent at any time in the App’s settings (Usage & Performance Analytics), which stops any further collection, including screen recordings.

PostHog data is processed on PostHog’s EU infrastructure. Firebase is provided by Google Ireland Limited; see section 9 for transfers outside the EEA.

If you allow notifications, the App receives a push token from Firebase Cloud Messaging so that we can send you notifications. You can turn notifications off in your device settings at any time.

5/A. Screen recordings (session replay)

With your consent, the App records how it is used, as a series of screenshots of the App’s own screens together with your touches, scrolling and the names of the screens you visit. Text, images and maps are covered in the recording, so what you read or type — including place names, descriptions and what you enter into forms — and the map itself are not visible in it. What remains is the layout of the screens and where you tapped. The masking is applied automatically, on your device, before anything is sent.

• Purpose: to find usability problems and errors in the App.
• Legal basis: your consent; the recordings are not made without it.
• Linked to: the same identifiers as the other analytics data — an SDK-generated identifier and, when you are signed in, your user ID.
• Storage: PostHog, EU infrastructure; recordings are deleted after 30 days (section 10).
• Withdrawal: there is no separate switch for recordings. Turning off Usage & Performance Analytics in the App’s settings stops them at once, together with the other tools in this section. You may also ask us to delete recordings of you before the 30 days have passed (section 11).

If you allow notifications, the App receives a push token from Firebase Cloud Messaging so that we can send you notifications. You can turn notifications off in your device settings at any time.

6. Advertising and Measurement Tools

The App currently runs no advertising or attribution tool. The Meta SDK included in the App has automatic event logging and advertising-identifier collection switched off. If we introduce advertising or measurement tools from Google, Meta or TikTok, they will run only with your consent where the law requires it, and this Policy will be updated first.

6/A. Website Cookies and Consent (Google Analytics 4)

The Voyager Maps website uses its own consent banner to collect, store, and manage cookie preferences. Until a choice is made, Google Consent Mode is set to denied for analytics, advertising, and personalisation, so nothing non-essential runs before consent is given.

• Strictly necessary cookies: used for essential website operation and security.
• Statistics cookies: include Google Analytics 4 (GA4) for aggregate usage analytics.
• Marketing cookies: used only if enabled and only with consent where required.

On the website, GA4 is configured to load only after the user grants consent for statistics cookies. If consent is refused, GA4 does not load and no GA4 analytics events are sent.

Legal basis for non-essential website cookies (including GA4): consent. Users can withdraw or change consent at any time via the cookie settings interface.

Where Google services involve transfers outside the EEA, such transfers are handled under applicable safeguards (for example, Standard Contractual Clauses, where applicable).

6/B. Cookie Retention (Website)

Cookie lifetimes vary by cookie type and provider. Strictly necessary cookies, including the record of your own consent choice, are kept for up to 12 months. Google Analytics 4 cookies are set only after consent and follow Google’s own lifetimes for that product. You can review or change your choice at any time through the consent banner, and clearing your browser storage removes the stored choice.

7. Server Logs and Diagnostics

Our servers record technical data such as request time, IP address, user-agent and error information, for operation and security (legitimate interest). The ordinary request log is rotated and kept only briefly. Warnings and errors, which may include the IP address and user-agent of the request that caused them, are kept for 30 days so that problems can be investigated. Refused requests (for example, too many sign-in attempts) are counted per minute, with the IP address, and kept for 30 days.

7/A. Issue Reports and Support Metadata

If you submit an issue report or support request through the App, we may process the information you provide (such as your email address, report type, description, and page/context information) together with technical metadata (such as IP address, user-agent, and timestamp) to investigate and respond to the report.

8. Data Storage and Infrastructure

Our servers, database and uploaded files are hosted by Hetzner Online GmbH in data centres in the European Union. Uploaded files are kept in object storage and referenced via stored URLs.

8/A. Data Kept on Your Device

Some data is kept in the App on your device, so that it keeps working without a connection:

• Waiting for a connection: places you add, changes to your own places, and the photos that go with them (and with your trips) while there is no connection. They are sent to us when the connection returns, when the App starts, or when you sign in, and removed from the device once they have arrived. If our server refuses one of them three times, the App tells you and removes it.
• Copies for offline use: the list of your own places, your trips, and copies of photos you have already seen (up to about 200 MB; the oldest go first). Your system may also clear the photo copies to free space. The copy of your place list is removed when you sign out.
• After signing out: anything still waiting stays on the device, separate from every other account, and is sent when the same account signs in again. It is never sent as anyone else.

Deleting the App, or clearing its data, removes all of this from the device.

9. Recipients and Transfers Outside the EEA

We do not sell personal data. We share it only to the extent needed, with the following recipients, who act as our processors or, where stated in their own terms, as independent controllers:

• Hetzner Online GmbH (Germany) – hosting.
• Google – Sign in with Google; Firebase (section 5); sending our emails through Google's mail service; Google Analytics on the website (section 6/A).
• Apple – Sign in with Apple.
• PostHog – product analytics and masked screen recordings, processed in the EU (section 5).
• Mapbox, Inc. (United States) – map display. To deliver map tiles, Mapbox receives your IP address, device and app information and the map area being viewed.
• OpenStreetMap Foundation – receives place data only, never personal data (section 3/B).
• Other members of a trip you share, and the people you invite, see what the sharing settings allow; other users see content you publish (public places, descriptions, images, Wi-Fi details). This includes a place you make public as your home: its position and its Wi-Fi details are shown to every user of the App.
• Authorities, where the law requires it.

Some of these recipients (Google, Apple, Mapbox) may process data in the United States or other countries outside the EEA. Such transfers take place on the basis of the EU–US Data Privacy Framework where the recipient is certified under it, or of the European Commission's Standard Contractual Clauses.

10. Data Retention

Data is retained only as long as necessary for the purpose it was collected for. In particular:

• Account, profile, preferences, saved places and trips: until you delete the account.
• Guest sessions: deleted after 90 days without a visit. A session is only ever restored for a returning guest within 30 days.
• Hourly guest request counts: deleted after 30 days.
• Content created in guest mode: held on your device, for as long as you keep the App installed; deleting the App deletes it.
• Data kept on your device for offline use: until it has been sent to us, or until you delete the App (section 8/A).
• Server warnings and errors, refused requests: 30 days (section 7).
• Screen recordings in the App (with consent): 30 days, then deleted (section 5/A).
• Consent records: kept after account deletion, without any other data about you, for as long as we may need to prove that consent was given (in general, the 5-year limitation period).
• Do-not-email list: for as long as we send email (section 4).
• Reports and proposed changes: for as long as the map data they concern is kept; after account deletion without any link to you.

10/A. What happens when you delete your account

Your account, profile, sign-in methods, consents, favourites, private places and the trips only you are part of are deleted. Content that other people rely on is kept, but no longer linked to you:

• public places, and places someone else has saved or put in their trip;
• images still shown with such content;
• trips shared with others, which pass to another member;
• your reports and proposed changes, and place data already published on OpenStreetMap.

If such remaining content itself identifies you (for example, a photo or a description), you can ask us to remove it at the address in section 1. After the deletion we keep only an anonymous count of deleted accounts per month, App language and sign-in method; it contains nothing that could identify you. See the Delete Your Account and Data page for how to delete your account.

11. Your Rights

Under the GDPR you have the right to:

• access your personal data and receive a copy of it;
• have inaccurate data rectified;
• have your data erased;
• restrict processing;
• object to processing based on legitimate interest;
• receive the data you provided in a structured, machine-readable format (data portability);
• withdraw your consent at any time, without affecting processing carried out before the withdrawal.

Requests can be submitted to [email protected]. We answer within one month; we may ask for information to confirm your identity.

You also have the right to lodge a complaint with a data protection authority, in particular in the country where you live or work. In Hungary this is the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), 1055 Budapest, Falk Miksa utca 9–11, naih.hu. You may also go to court.

12. Data Security

Appropriate technical and organisational measures are applied to protect personal data, including encrypted connections, signed session tokens and access restricted to the controller.

13. Children’s Privacy

The App is not intended for anyone under the age of 16, and we do not knowingly process personal data of children under 16. If you believe a child has given us personal data, please contact us and we will delete it.

13/A. Related Legal Documents

For related legal information, please also refer to the current versions of our Terms of Service and Delete Your Account and Data page.

14. Changes to This Policy

This Privacy Policy may be updated. Material changes will be communicated within the App, and where the law requires it, we will ask for your consent again.