Legal
Privacy Policy
Last updated: November 9, 2026 (draft corrections pending counsel review)
Information We Collect
We collect information you provide directly, such as your name, email address, and trip details when you create an account and use Roamze. We also collect usage data to improve our service.
How We Use Your Information
We use your information to provide and improve Roamze, personalize your experience, and communicate with you about your account and our services.
Data Sharing
We do not sell your personal information. We may share data with service providers who help us operate Roamze, subject to confidentiality agreements.
Text Messages (SMS)
If you tick a text box on Roamze (on a booking request, when you sign up as a guide, or in guide Settings), we collect your mobile number and record that you agreed, with the date, time and the words you saw. We use your number only to send the booking texts you asked for, described in our SMS Terms. Reply STOP to any text to stop them; we keep a record of the opt-out so we never text you again unless you reply START or tick the box again.
We send texts through our messaging provider, Twilio, which receives your number and the message only to deliver it. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties.
Analytics & Cookies
We measure how Roamze is used with our own first-party analytics. To do this we store two first-party cookies in your browser: rz_did (a random device identifier) and rz_sid (a session identifier). These let us count visits and understand which pages and features are used. For this first-party analytics we record the page path (never query strings), coarse country and state or region from your network (never your city or precise location), and product events, including the words you type into Roamze search. We drop a search entirely if it looks like it contains an email address, a phone number or a web address, and we use searches only in aggregate, for example to show a local business what people search for around its town. It does not store your IP address or use fingerprinting.
Roamze.com also loads tags operated by third parties, which collect information under their own privacy policies, such as your IP address, device and browser details, cookie identifiers and the address of the page you are viewing:
- Advertising and marketing tags: Google Tag Manager (which loads a marketing attribution pixel), the Reddit pixel and the Google Ads tag. On guide pages, guides’ ads may also use the Meta Pixel. These may use device and network signals to recognise your browser across sites.
Separately, for advertising, we and our advertising partners — including Google and Reddit — use cookies and similar technologies for marketing and remarketing, such as showing you a Roamze ad on other websites after you have visited roamze.com. For Google Ads specifically, we may securely share a one-way cryptographic hash (SHA-256) of your email address with Google — never your email address itself — so Google can match you to a Customer Match remarketing audience; a hash cannot be reversed back into an email address. You can review and control how Google personalizes ads to you at adssettings.google.com or myadcenter.google.com. Under the California Privacy Rights Act (CPRA), sharing a hashed email address with Google for advertising purposes is a “sale” or “sharing” of personal information. You can opt out of this sharing — and any other cross-context advertising use of your information, including via Global Privacy Control — at any time on our Your Privacy Choices page. Opting out there suppresses your device from all future Google Ads Customer Match syncs, in addition to the other advertising uses described there.
AI Processing
Roamze’s planning features are AI-assisted, and so is the Roamze connector for AI assistants such as Claude. When you use them, the request you make and the Roamze data needed to answer it — for example a trip’s activities, your gear list, or a location — are sent to the AI provider that generates the response. We currently use Anthropic, OpenAI and Google (Vertex AI and Gemini) for this, and RunPod, a cloud provider that runs Roamze’s own AI models on our behalf. We do not send your email address, password or payment details to any AI provider.
For businesses listed on Roamze, our AI-visibility report checks how AI search engines describe the business. To do this we send the business’s public name, type and location (never customer data) as questions to Perplexity, OpenAI, Anthropic and Google.
To make answers fit what you are looking for, your recent activity on Roamze may also be sent to our AI provider along with your request. That is a short summary, such as the kinds of activities and the states you have been viewing, trips you have saved or planned and, if you are signed in, questions you recently asked Roamze’s AI. It never includes your exact location or any dates. We may also include aggregate counts of what visitors to Roamze explore in a state, which never identify anyone.
If you connect Roamze to a third-party AI assistant, that assistant receives whatever Roamze data you ask it to work with, and its own privacy policy governs what it does with it. You can revoke a connector’s access at any time from your Roamze account.
Helping improve Roamze’s AI answers
Separately from the AI processing described above, you can choose to let us save your conversations with Roamze’s AI to make its answers better.
This is off unless you turn it on, and we rely only on your consent. You will find it in your account settings under Privacy, as “Help improve Roamze’s answers.” We collect nothing described in this section unless you have turned that setting on. You can turn it off at any time.
Who can turn it on. You must be 18 or older, and we ask you to confirm that when you turn it on. It is not offered in the European Union, the European Economic Area, the United Kingdom or Switzerland. We decide that from the country your connection comes from, both when you turn it on and each time something would be saved.
What we save when it is on. The questions you ask Roamze’s AI, the answers it gave you, and what you did next, for example whether you saved the trip, rated an answer helpful or unhelpful, or asked the same thing a different way. We also save which AI model produced the answer.
We remove personal details before saving. Email addresses, phone numbers, street addresses, exact map coordinates, social handles and names we can identify are removed and replaced with placeholders. Specific dates are removed too, so a saved question does not record when you plan to be somewhere. Locations are reduced to the trail, campground or place in our catalog rather than an exact position.
The removal is automatic, and automatic removal of names from free text is imperfect. A name written plainly, with nothing around it to mark it as a name, can be missed. So this information is not anonymous. We treat it as personal information that relates to you, protect it accordingly, and delete it when you ask.
What we use it for. To evaluate how well Roamze’s AI answers questions, and to train AI models to answer better. That training may be done by us or through the third-party AI model providers we work with. We do not use it to teach an AI facts about trails, conditions or closures, because that information comes from our live data every time you ask. We do not use it to decide when the AI declines to answer; those rules are fixed in our software and are not learned from anyone’s conversations. If we ever want to use it for a different purpose, we will ask you again first.
What we never use it for. We do not sell it. We do not use it for advertising. We do not use it to build a profile of you.
Conversations through another AI assistant are excluded. If you use Roamze through a connector in a third-party AI assistant, those conversations are never saved under this setting, whatever the setting says.
How long we keep it. Up to 365 days. After that it is deleted automatically and can no longer be used for any of the purposes above.
Turning it off. Turning the setting off stops any further saving and deletes what was already saved. You can do that from anywhere, including a country where the setting is not offered. If you delete your Roamze account, this information is deleted with it. One thing turning it off cannot do: if information was already used to train a model before you turned it off, we cannot remove it from that model. That is why we check your consent again at the moment we build any training set, so anything you withdraw is deleted before it can be included in a later one.
Browser Extensions
Roamze offers two Chrome extensions: “Roamze: Campsite Alerts & Trail Conditions” and “Roamze New Tab: Get Outside.” This section covers what they do with your data.
What they read. The campsite-alerts extension reads the address and title of the page you’re on, only on Recreation.gov, AllTrails, NPS.gov and the Forest Service site, or on a page where you open the Roamze panel yourself, to look that place up in Roamze’s catalog. It reads a page’s text only when you send a question from the Ask tab with “Asking about this page” turned on: then it reads the text you’ve highlighted, or the page’s main text, at that moment. It never reads pages in the background, and never reads your browsing history. On sites beyond the four above, Chrome asks your permission once before the extension can read a page at all. The new-tab extension reads nothing from your browsing.
What they send to Roamze. The name of the place being looked up, or the home base you chose, so we can find matching places, nearby places and closures. When you create a campsite alert, the campground, your dates, and either the email address you typed or your Roamze account; we email that address once to confirm and send alerts only after you click the confirmation link. If you sign in, your Roamze sign-in token, so the extension can show your alerts and saved places. A random device identifier and the label “chrome_extension,” so we can count how many alerts come from the extension; it is not linked to your identity unless you sign in.
Questions you ask. If you’re signed in and ask Roamze a question from the extension’s side panel, your question, the conversation so far, the place you’re asking about (its name and location), and, when “Asking about this page” is on, the page’s address, title and up to about 6,000 characters of its text are sent to Roamze’s chat to answer you, just as if you’d pasted them into Ask on roamze.com. The conversation, including that page text, is saved to your Ask Roamze history on your account, where you can see or delete it. Turn the page off with the × next to it before you send.
What stays on your device. Your sign-in session, the last email you used for an alert, campground names for your alerts list, your home base, and a few hours’ cache of nearby places. Uninstalling the extension deletes all of it.
What we never do. We don’t sell or share extension data, use it for advertising, or use it for anything other than the features above. The extensions never read, scrape or poll Recreation.gov from your browser; Roamze checks campsite availability from its own servers.
Your choices. Unsubscribe from any alert with the link in its emails, or stop it from “My Roamze” in the side panel if you’re signed in. To delete your data, contact us at support@roamze.com.
Google User Data
Some Roamze features connect to your Google account, but only when you choose to. This section covers what Roamze reads from Google, what it does with it, and what it never does.
Sign in with Google. If you sign in with Google, we receive your name, email address and profile photo, and use them to create and identify your Roamze account.
Google Business Profile (guides only, optional). If you connect your Business Profile from your guide dashboard, Roamze lists the Business Profile accounts and locations you manage, reading only each location’s name, title and street address, so you can pick where to post. We store the locations you pick. When you create or approve a post, we publish it to those locations as a Google update, with its text and, if you added them, a photo and a button, and we store the post’s Google ID and link so you can see where it went. We also set your profile’s “Book” link to your Roamze booking page: to do that we read the profile’s existing booking links, then add ours or update a Roamze link already there. We don’t change or remove other providers’ booking links. Roamze does not read your reviews, messages, insights or customer information.
Google Calendar (guides only, optional). If you connect your calendar, Roamze reads only the busy start and end times on your primary calendar, never event titles, attendees or any other details. We use those times only to stop travelers from requesting a slot when you’re busy. They are held in server memory for a few minutes and never written to our database.
Google Analytics (guides only, optional). If you connect Google Analytics from your guide dashboard, Roamze has read-only access. We list the Analytics accounts and GA4 properties you can see, by name, so you can pick your website’s property, and we store only that property’s ID and name. For that property we read totals for the last 30 days and the 30 before: visitors, sessions, page views and key events. We also read sessions per day, sessions by traffic channel, your most-viewed page paths, and how many sessions came from Roamze. These are counts, not information about individual visitors. We show them only to you, in your dashboard, labeled as your Google Analytics numbers, and never combine them with Roamze’s own analytics. The report is kept in server memory for up to 30 minutes so the page loads quickly, and is never written to our database. Roamze never changes anything in your Google Analytics.
How we protect it. Your Google OAuth tokens are encrypted with AES-256-GCM before we store them, and only our servers can read them. The full list of safeguards is under Data Security and Protection of Sensitive Data below. You can disconnect Business Profile, Calendar or Google Analytics at any time from your Roamze account: we ask Google to revoke Roamze’s access and delete the stored tokens. Google revokes all of Roamze’s access to that Google account at once, so disconnecting one of these also disconnects the others connected with the same Google account. You can also remove Roamze’s access from your Google account at myaccount.google.com/permissions.
What we never do. We don’t sell data we receive from Google, use it for advertising, or transfer it to anyone except as needed to provide the features above. We don’t send it to the AI providers described in “AI Processing” above, and we don’t use it to train AI models, including under “Helping improve Roamze’s AI answers.”
Roamze’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Apple Health
If you connect Apple Health in the Roamze iPhone app, Roamze reads your workouts (type, time, duration, distance, elevation gain and route) to build your profile. We don’t read other health data, never use it for advertising, and delete it when you disconnect or delete your account.
Connecting is optional and only happens when you allow it in the Health permission prompt. Roamze only reads from Apple Health and never writes to it. You can disconnect from Settings → Integrations in the app, which deletes every workout we imported, or turn off Roamze’s access in the Health app at any time. We don’t sell this data, and we don’t share it except with the service providers that host Roamze for us.
Connected Fitness Apps
You can choose to connect a fitness app or device account to Roamze: Strava, Polar, Garmin Connect, COROS, Suunto, Wahoo, Komoot, or Health Connect on Android. Connecting is optional and only happens after you approve it on that service’s own permission screen.
From a connected app we keep only your activities’ sport type, start time, duration, distance, elevation gain and, where the app provides it, the route or start point. We don’t keep heart rate, calories, sleep or other health data. For Strava, we don’t store your individual activities at all; we keep only a summary of your ability (such as how far and how much you typically climb), as Strava’s terms require.
We use this data only to personalize Roamze for you, for example to suggest a skill level that you confirm or change yourself, and trails that fit what you do. It is shown only to you. We never sell it, never use it for advertising, and never share it with operators, advertisers or other users; only the service providers that host Roamze for us process it. You can disconnect any app from Settings → Integrations (or Connected accounts in your profile on roamze.com). Disconnecting revokes our access with that service and deletes every activity we imported from it, and deleting your account does the same for every connected app.
Data Retention
We keep your account and trip data for as long as your account is open. If you delete your account, it is deactivated immediately and scheduled for permanent deletion 90 days later; during those 90 days you can sign back in to reactivate it, and after that it is removed. You can start this from your account settings.
Business (operator and guide) accounts: deleting your personal Roamze account does not yet automatically delete a business profile you manage or the business records it holds, such as inquiries, bookings, customer lists, text-message history and signed waivers. To have your business’s data exported or deleted, email support@roamze.com and we will handle it. We are building automatic deletion on the schedule described in our Data Processing Addendum. Signed waivers may be kept for the legal limitation period after a trip, because they are evidence for both the business and its customers.
Raw first-party analytics events are kept for 13 months and then deleted automatically; aggregated counts that cannot identify you may be kept longer. Some records are retained past account deletion where we are required to keep them, such as billing and tax records.
Where Your Data Is Stored
Your data is stored on managed cloud infrastructure in the United States, encrypted in transit and at rest. Our service providers — including our database, hosting and email providers — process it on our behalf under confidentiality agreements and may not use it for their own purposes. The current list is on our subprocessors page.
Data Security and Protection of Sensitive Data
We treat the credentials and account data you entrust to us, including all data we receive from Google, as sensitive, and protect it with these safeguards:
- Encryption in transit. Roamze’s website and API are served only over HTTPS, and tell browsers to always use HTTPS (HTTP Strict Transport Security). Our servers call Google and other providers over HTTPS.
- Encryption at rest. Your data is stored on managed cloud infrastructure that encrypts it at rest.
- Encrypted access tokens. When you connect an account such as Google, the OAuth tokens it gives us are encrypted with AES-256-GCM, using a fresh random value for each record, before they are written to our database. They are never stored in plain text, and if the encryption key is unavailable we refuse to store them rather than store them unencrypted.
- Keys kept apart from the data. The encryption key is held in Google Cloud Secret Manager and given only to our backend service when it runs. It is not stored in our database, so a copy of the database alone cannot be used to read your tokens.
- Restricted database access. The tables that hold connected-account tokens can only be read by our backend service. Database access rules block them from every signed-in or anonymous user, and the tokens are never sent to your browser or app.
- Access only to your own account. Every request to connect, use or disconnect an account must come from your signed-in session, and our servers act only on the account that session belongs to.
- Protected sign-in to connected accounts. When you connect Google or another provider, the request carries a signed, short-lived security code that we check when the provider sends you back, so nobody else can attach their account to yours, or yours to theirs.
- Least data, least access. We request only the permissions a feature needs and read only the data described in this policy. Some data, such as your Google Calendar busy times, is held briefly in server memory and never written to our database.
- Revocation and deletion. When you disconnect an account, we ask the provider to revoke Roamze’s access and delete the stored tokens. Deleting your Roamze account deletes your data as described under “Data Retention” above.
No method of transmission or storage is completely secure. If you believe your data has been put at risk, contact us at support@roamze.com with “Security” in the subject. More about how we protect business and customer data is on our Trust & Security page.
Contact Us
If you have questions about this privacy policy, please contact us at support@roamze.com.