Privacy Policy
Effective date: September 25, 2026 · Version: 2026-09-25
Roamer is operated by Lumin LLC (“Lumin,” “we,” or “us”), a limited liability company formed in Washington State and the entity responsible for information handled through the service. This policy explains how Roamer collects, uses, and shares information when you use the Roamer website, Android app, iOS app, and related services.
Contact
For privacy questions, complaints, rights requests, or account deletion requests, contact support@bearoamer.com.
Information we collect
- Account information, including your name, email address, profile photo, authentication provider, Firebase user ID, and sign-in/session metadata. When you affirmatively sign in or create an account through an updated notice, we record the Terms and Privacy Policy versions presented, your confirmation that you are at least 18 and have reached the age of majority where you live, the action and platform, and a server timestamp. We record the confirmation, not your birth date. Existing sessions are not evidence that you accepted a newer version.
- Profile and preference information, including budget tier, travel pace, interests, traveler type, home location you choose to provide (used for regional defaults and trip origins), currency, temperature unit, dietary restrictions, notification preferences, household travel-prep details, and onboarding choices.
- Travel document information you choose to enter, including passport/residency countries and passport expiry date. These profile features do not require a passport number or scan. Freeform content, documents, photos, or support materials you voluntarily submit may contain additional personal information; avoid including sensitive information a feature does not need.
- Trip content that you create, import, or share, including destinations, dates, itineraries, place names, place IDs, coordinates, reservations, budgets, expenses, packing and checklist items, notes, collaborators, votes, public-share links, private place ratings, AI chat messages and conversation history, and generated travel guidance.
- Historical Gmail information if you previously connected Gmail, including the Gmail OAuth access token and expiry, travel-reservation email search results, message content needed to parse booking confirmations, and the reservation details you choose to import.
- Location information when you grant permission, including approximate or precise device location, background/live-trip location where enabled, and last-known location used for maps, nearby places, reminders, geofence alerts, running-late nudges, and trip context.
- Device, notification, and usage information, including device/app identifiers, FCM push tokens, notification delivery/open events, app interactions, diagnostic logs, crash reports, IP address, browser/device metadata, cookies, and local storage.
- Some trip information comes from other travelers who invite you or add shared reservations, expenses, or itinerary details. Authentication providers supply account information, and maps, places, weather, and other travel-data services supply information used in your plans.
- Optional dietary preferences and details you enter about accessibility, allergies, or health can reveal sensitive information. Provide only what a travel feature needs and do not enter someone else’s sensitive information without appropriate permission. Accepting the Terms or acknowledging this policy is not explicit consent to every use of sensitive information.
- Support information you choose to send, including your reply email, message, trip ID, screenshots or attachments you provide, and request metadata.
How we use information
- Provide, personalize, and sync trip planning, itinerary, map, reservation, packing, expense, budget, collaboration, notification, live-trip, and AI-assisted travel features.
- Authenticate users, sync data across devices, protect accounts, prevent abuse, and respond to support or account deletion requests.
- Generate and refine user-facing itineraries, travel suggestions, budgets, packing lists, visa guidance, route context, smart nudges, and other trip-specific outputs based on information you provide. Relevant prompts, conversation history, trip details, preferences, reservation content, and location context may be sent to Google AI services to perform the feature you invoke. Do not submit information you do not want processed for that feature.
- Requested AI features send relevant feature inputs to Google’s AI services. We do not use your private trip content to train our own publicly available general-purpose foundation models. Google’s applicable Gemini paid-service terms do not use prompts or responses to improve its products. Provider safety and legal retention can still apply, and feature-specific services such as Search grounding have additional terms.
- Deliver push notifications, schedule reminders, recover stale notification tokens, and route notification taps to the relevant trip screen.
- Analyze reliability, performance, product usage, abuse patterns, and crashes so we can operate, secure, debug, and improve Roamer.
Legal bases where EU/EEA or UK law applies
- Where EU/EEA or UK data protection law applies, each use of personal information requires an applicable legal basis. Account authentication, synchronization, collaboration and requested AI planning rely on performance of our contract only to the extent necessary to provide the feature you request.
- Optional usage analytics relies on your consent. Location features use information when you request the feature and allow access, relying on contractual necessity or consent as applicable. A device permission is separate from any additional consent required by law.
- Security, abuse prevention and necessary service diagnostics may rely on legitimate interests in protecting users and operating a reliable service only where applicable law permits and those interests are not overridden by your rights. Support and privacy requests use contractual necessity, legitimate interests or an applicable legal obligation according to the purpose. Legally required records rely on the relevant legal obligation.
- Accepting the Terms does not make optional processing necessary. Sensitive information requires an additional applicable condition; this policy does not itself supply explicit consent for that processing.
Gmail and Google Workspace data
- Gmail reservation import is currently disabled. We do not request new Gmail access through that disabled feature. Disabling it does not itself delete previously imported reservations or stored credentials. Contact us for help with historical records or credentials; if we enable the feature later, we will present its access request and applicable disclosures before use.
- When available, Roamer uses Gmail data only to search for travel booking confirmations, parse candidate reservations, show them to you, and import the reservations you select.
- Roamer does not use Gmail data for advertising or to train Roamer's own generalized AI models. Relevant Gmail message content may be sent to Google AI services to provide the user-facing reservation-import feature you invoke. Acknowledging this policy or signing in does not itself connect Gmail or grant Gmail access.
- Roamer's use of information received from Google Workspace APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
- When import is available, raw Gmail messages are used to generate candidate reservation results during a search. Roamer stores imported reservation fields if you choose to import them; it does not store raw Gmail message bodies as trip records.
Service providers and sharing
- We do not sell your personal information.
- We share information with service providers as needed to operate Roamer, comply with law, protect rights and safety, or complete actions you request.
- Service providers may include Firebase and Google Cloud for authentication, database storage, hosting, push notifications, analytics, and crash reporting; Google Maps and Places for maps, place search, photos, directions, and location context; Google AI services for AI generation; Open-Meteo for weather; Frankfurter or other exchange-rate providers for currency conversion; Sentry when error monitoring is configured; Vercel for hosting and consent-based web analytics; Resend for transactional email such as trip invitations; and app-store or payment processors if paid features are enabled.
- Enabled optional integrations are used only when you connect or invoke those features. Gmail import is currently disabled; historical records are described above. Splitwise OAuth credentials are encrypted at rest and used to show connection status and export trip expenses when you request it.
- If you share a trip or invite collaborators, the trip details you choose to share may be visible to those collaborators.
- If you enable a public share link, anyone with that link can view the shared itinerary, including its locations and schedule, and the owner display name and profile photo included in the shared view, until you revoke the link. Review that view before sharing. Copies, screenshots, or exports already made by other people cannot be recalled by revoking the link.
- If you export expenses to Splitwise, Roamer sends the selected trip and expense information needed to create the Splitwise group and expenses.
- We may disclose information if required by law, to protect rights and safety, or in connection with a merger, acquisition, financing, or sale of assets, with appropriate notice where required.
Maps, places, and location
- Roamer uses Google Maps and Google Places features and content. Location and map requests may be processed by Google under Google's terms and privacy policy.
- Use of Google Maps features and content is subject to the Google Maps/Google Earth Additional Terms of Service and Google Privacy Policy.
- You can deny or revoke device location permission. Maps, nearby suggestions, live-trip alerts, background geofence checks, and running-late reminders may not work without location permission. Ending a live-trip session does not itself erase the last-known location already stored with the session; it remains subject to our retention and deletion practices.
Retention and deletion
- We retain active account, trip, preference, conversation and reservation information while needed for requested features, subject to deletion and any specific lawful retention reason. Conversation summaries and ended live-trip records can remain after individual messages or a live session end; ending a session or revoking location permission does not itself erase earlier coordinates.
- Expired Gmail access tokens are not used for access, but expiration or disabling import does not itself remove stored credentials. Contact us about historical Gmail credentials and records. Splitwise credentials are cleared on disconnection or account deletion. Imported reservations and exported expenses are separate records and are not erased simply by disconnecting. Raw Gmail message bodies are not stored as trip records.
- The in-app account-closure flow schedules deletion after a cancellable 30-day period. Scheduled cleanup processes removal after that period; completion can take additional time if work must be retried. This elective closure period does not postpone an applicable legal right to erasure. To exercise that right, contact support@bearoamer.com for assessment under the applicable deadline and lawful exceptions.
- Cloud Logging default-bucket logs are retained for 30 days and required-bucket logs for 400 days. These periods do not describe every analytics, crash-reporting or hosting provider’s records. Other operational, analytics, crash, support and administrative records are retained according to their purpose, applicable provider settings and any specific legal requirement; they remain subject to applicable rights and exceptions.
- Firestore point-in-time recovery is enabled. Scheduled daily Firestore backups have a 7-day retention and weekly backups a 98-day retention. Account deletion does not mean immediate disappearance from every backup. Retained information is restricted to its necessary purpose; backup retention is not permission to continue ordinary use of erased data.
- Shared-trip contributions, records held independently by other users, collaborators’ copies and records exported to third-party services may remain after account deletion. Contact us to identify information that should be removed. Deleting Roamer does not delete your account with Google, Apple, Splitwise or another provider.
Your choices
- You can decline or revoke optional location, background location, photos, camera or notification permissions, though related features may not work. You can change notification preferences, disconnect enabled integrations where supported and edit or delete trip, reservation, expense, profile and travel-document information where the app allows.
- Depending on applicable law, you may have rights to access or obtain a copy, correct inaccuracies, request deletion, restrict processing, object to processing or obtain a portable copy of information you provided. Where we rely on consent, you may withdraw it without affecting earlier lawful processing. Rights have conditions and exceptions; any retained information needs a specific lawful reason.
- Where applicable, you may object to processing based on legitimate interests and to direct marketing if we undertake it. Exercising a privacy right does not require accepting new Terms.
- Send requests to support@bearoamer.com. We will ask only for verification information reasonably needed and handle requests within the period required by applicable law. If a permitted extension or refusal applies, we will explain it and available complaint routes. You may complain directly to the relevant privacy authority without first contacting us.
- EU/EEA users may contact the data protection authority where they live, work or where an alleged infringement occurred. UK users may contact the Information Commissioner’s Office at ico.org.uk/make-a-complaint/. Canadian users may contact the relevant federal or provincial regulator. Indian users have rights under applicable laws as those provisions take effect. This policy does not waive local rights or imply that every provision of a law with phased commencement is already in force.
Cookies, local storage, and diagnostics
- The website uses cookies and browser storage for required authentication, security, preferences and application state. Mobile apps store account, trip and preference information locally for features and offline use. Location, photo and notification permissions are controlled separately through your device.
- Optional usage analytics is disabled until you enable it. Web analytics uses Firebase Analytics, Vercel Analytics and Speed Insights to measure use and performance. Mobile usage analytics uses Firebase Analytics. On the web, Accept all and Reject all control optional analytics; Customize lets you review required storage and save your analytics preference. Reopen Privacy choices from Settings. On Android and iOS, change Usage analytics in Settings. Core trip-planning access does not depend on this choice.
- Choices apply to the browser or device where you make them, rather than every device on your account. Withdrawal stops future optional collection; it does not automatically erase previously collected provider records. This choice does not authorize advertising.
- Crash reporting and operational error reports are handled separately from optional usage analytics. Reports can include account identifiers, request identifiers, error or status information and sanitized API paths. We use them to investigate failures and protect the service; this policy does not treat every diagnostic use as exempt from applicable consent requirements.
- You can manage cookies, storage and permissions through your browser or device settings. Clearing site data may sign you out or reset saved preferences. Contact us for help with an optional processing choice if your app version lacks a control.
International processing
- Lumin LLC is based in the United States. Roamer and its providers may process information in the United States and other countries when you use the service from another country. Our primary Firestore database is configured in North America. Other processing locations depend on the provider and service configuration.
- Those countries’ laws can differ from the laws where you live, and authorities may have access under their laws. International processing remains subject to applicable legal requirements, including a valid transfer arrangement where required. Contact support@bearoamer.com for information about the safeguards applicable to your information and how to obtain a copy, subject to necessary redactions.
- Acknowledging this policy does not waive applicable protections or provide blanket consent to international transfers.
Security
- Roamer uses Firebase Authentication, Firestore security rules, HTTPS, server-side authentication checks, rate limiting, and token cleanup to protect user data.
- No service can be guaranteed perfectly secure. Contact us promptly if you believe your account or data has been accessed without permission.
Children
- Roamer is intended for people who are at least 18 and have reached the age of majority where they live. It is not directed to children. If you believe someone below that age has provided personal information, contact us so we can investigate and take appropriate action, including restricting the account and handling deletion as required by law.
Changes
- We may update this policy as Roamer changes and will identify the updated version and effective date. We will give direct notice of material changes, such as through the app or email, before they take effect where feasible and as required by law. Where a change requires new consent, we will request it before the affected processing. Merely posting an update is not a substitute for legally required notice or consent.