Privacy Notice for roam.
Last updated: 8 November 2026 · App version: 1.1
1. Who is responsible?
MTK Consulting, Germany, operates roam. Privacy contact: info@mtk-consulting.de.
Postal address and the complete legal identity of the controller: [[CONTROLLER_LEGAL_DETAILS]].
2. What roam. does
roam. is a personal travel atlas and journal. You can mark visited countries, enter destinations and travel dates, add notes and selected photos, create checklists and view memories. You choose which travel content to enter. Providing travel content is voluntary; an email address or identity-provider account is needed only for optional account features.
The current app does not contain advertising or advertising-tracking SDKs, a separate product-analytics SDK, AI analysis, automatic GPS tracking, contact-book access or in-app purchases. The app does not use your content for automated decisions with legal or similarly significant effects.
3. Guest mode and local data
Without signing in, your travel content is stored on your device. No anonymous cloud account is created and guest trips or photos are not uploaded to our cloud service. Countries, places, routes, notes, dates, checklists, photos, language preferences and reminder settings may be stored locally. In the web preview, local data is stored in your browser.
Opening the sign-in screen contacts Supabase to check available sign-in methods. This request can disclose technical connection data, including your IP address, without uploading your guest atlas. If a signed-in session already exists, the app can restore it and resume enabled synchronization when reopened.
Device backups or browser/operating-system services may create their own copies according to your Apple, Google or device settings. These are separate from roam.'s optional cloud synchronization.
4. Optional accounts and cloud synchronization
When you create or use an account, Supabase Auth processes your email address, account identifier, authentication/session information and technical connection or security information. Sign-in emails are sent through the configured email-delivery service. If Apple or Google sign-in is enabled and you select it, that provider also processes your sign-in; Supabase may receive the identifier, email address and profile information supplied by the provider, such as a display name or profile-image URL. Those providers' own privacy notices also apply.
With synchronization enabled, the account atlas's trips, destinations, coordinates, travel dates, journal text, country marks, checklists and attached photos are transmitted to the backend and associated with your account. Device language and notification settings are not part of the synchronized atlas document. Settings and session information can still be processed separately to operate the app and authentication.
Signing in opens a separate account atlas. Guest content is copied to that account only when you explicitly choose the guest-copy action and confirm it. With synchronization enabled, the copied content is then uploaded. An imported backup replaces the currently open atlas after confirmation; importing into an account can therefore change its cloud data.
You can pause synchronization in the profile. Pausing stops new atlas synchronization; it does not delete existing cloud data or prevent necessary authentication/session requests. Signing out returns to the guest atlas. The account's local cache, including unsent changes, remains for a later sign-in to that account.
5. Photos, places and permissions
Only photos you select through the system picker are attached to trips. The current app does not scan your entire library or automatically derive routes or memories from photo metadata. Picker processing can resize or recompress files; removal of all embedded metadata is not guaranteed. Selected files may retain information such as capture date or location.
Locations you enter or select include geographic coordinates. These can reveal precise places you visited, even though the app does not request your live GPS location. With account synchronization enabled, this information leaves the device with your atlas. Map geometry and place search are bundled locally; normal place searches do not contact an external geocoding or map-tile service.
Reminders are optional local notifications. Permission is requested when you enable them. Trip dates, device time zone and language are used on the device to schedule anniversary reminders. Disabling reminders cancels scheduled reminders through the app; permissions can also be changed in device settings.
6. Purposes and legal bases
Where the GDPR applies, processing needed to provide the features you request, including optional account synchronization, is based on Article 6(1)(b). Optional consent-based functions use Article 6(1)(a), where applicable; system permission is not a blanket consent to unrelated processing. Security and troubleshooting serve our legitimate interest in a reliable service under Article 6(1)(f). Article 6(1)(c) applies to processing necessary to meet legal obligations. Support correspondence is handled to answer your request and, where relevant, provide the service.
7. Service providers and processing locations
Supabase provides account authentication, the cloud database, private photo storage and the server-side account-deletion function. The configured database region is London, United Kingdom (eu-west-2), outside the EU/EEA. This does not establish the location of every supporting service, log, email delivery, support operation or subprocessor. Processing by international providers can also involve other countries, including the United States.
Applicable provider-contract and international-transfer details: [[PROVIDER_AND_TRANSFER_DETAILS]]. Configured sign-in email provider: [[EMAIL_PROVIDER_DETAILS]].
Provider information: Supabase Privacy Policy, Supabase Data Processing Addendum and Supabase Subprocessors. For provider sign-in, see Apple Privacy and Google Privacy.
We do not sell travel content or use it for advertising. Data may be accessed by authorized people or service providers as needed to operate, maintain, secure or support the service, and disclosed when legally required. Cloud storage is not end-to-end encrypted: backend infrastructure and appropriately authorized administrative access can process stored content.
8. Storage duration, deletion and backups
Local guest data remains until you remove it, replace the atlas with a backup, or clear the relevant app/browser data. Deinstallation, device backups and platform keychains behave differently across systems; deinstallation alone is not a reliable way to remove all credentials or copies.
Cloud atlas data is retained while the account is used, until you change/delete entries or request account deletion, subject to applicable retention obligations. Photos removed from a trip can remain as unreferenced private cloud objects until the account is deleted; the current version has no periodic cloud-photo cleanup. Changes made offline or while synchronization is paused do not update the server until a successful synchronization.
In the profile, choose the account-deletion action and confirm it to request removal of the account, cloud atlas and associated cloud photos, as well as that account's cache on the current device. The separate guest atlas remains. Other devices' local caches and previously exported files are not remotely erased. Rare failed cleanup operations require operator follow-up; contact the privacy address if deletion does not complete.
Configured technical-log and provider-backup retention: [[LOG_AND_BACKUP_RETENTION]]. Backups, if present, can retain older copies until their rotation/deletion cycle completes. Copies subject to a necessary legal retention duty are restricted accordingly. Support correspondence is kept as needed to resolve the request and satisfy applicable duties.
9. Security and exported files
Connections to the configured backend use HTTPS. Account access is restricted by ownership rules, and photos are in private storage. Native authentication sessions use OS credential storage; iOS is configured without iCloud Keychain synchronization for these entries. Web sessions are stored in the browser for the relevant site.
The travel database and ZIP exports are not additionally encrypted by roam. Exported files contain private travel content and photos. Copies you save or send through a file picker, storage app, email or another service are controlled by that destination's settings and policies. Keep backups in a location you trust. If you send screenshots or logs to support, include only information needed to describe the problem.
10. TestFlight and the web preview
For TestFlight betas, Apple processes distribution, device/build, diagnostic and feedback information under its own terms. Information made available through TestFlight, including feedback, screenshots and crash reports, can reach the developer for beta support and improvement. See Apple's TestFlight privacy information.
The optional Flutter web preview can load rendering components or fonts from Google-hosted services; those requests disclose technical connection data to the hosting service. This is separate from the bundled offline map and place catalog. Native app behavior and the web preview should not be assumed to have identical network requests.
If this notice is hosted on GitHub or GitHub Pages, GitHub processes website connection data. GitHub Pages records visitor IP addresses for security purposes. See GitHub Privacy. The standalone notice pages supplied with this project use no analytics, scripts, external fonts or advertising cookies.
11. Your choices and rights
You can use guest mode, select which photos and places to add, pause synchronization, disable reminders, export the open atlas and request account deletion. Local-only information cannot be recovered by us if it has never been transmitted to us.
Where applicable, you have rights of access, correction, deletion, restriction, portability, objection and withdrawal of consent, without affecting earlier lawful processing. You may complain to a competent data-protection authority, including where you live, work or believe an infringement occurred. Contact info@mtk-consulting.de to make a privacy request. We may ask for proportionate information to verify account ownership.
12. Changes
This notice describes version 1.1. Material changes to processing, providers or features will be reflected in an updated notice before the relevant new processing begins, with any required information or choices provided in the app or through the service.