Roam & Board is run by one person. This policy describes exactly what the service collects, what it deliberately does not, and how to make it all go away. It is written against the actual database schema, not from a template.
Roam & Board is operated by Josiah Cloud, a sole proprietor doing business as Roam & Board, based in Colorado, United States. For any privacy question, request, or complaint, write to roamandboardcamping@gmail.com.
Roam & Board's own database stores no email address and no name. Accounts are handled by Clerk; payments by Stripe. What we hold against you is a random account identifier, a Pro flag, and whatever camping data you chose to save.
We do not sell personal information, we do not run advertising, and we set no tracking cookies of our own.
The one exception worth naming up front: the gear links are Amazon affiliate links. We earn a commission when you buy through them. Following one hands you to Amazon, which then applies its own cookies and tracking — as it would if you had typed the address yourself. We send Amazon nothing about you, and nothing happens if you don't click.
Account creation and sign-in are handled entirely by Clerk, an authentication provider. If you sign up with email, Clerk holds your email address and a hash of your password. If you use "Continue with Google", Clerk receives the basic profile Google returns. We never see or store your password, and your email address is not copied into our database.
What our database receives from Clerk is a single opaque user identifier — a string like user_2abc…. Every row below is keyed to that identifier and nothing else.
The service runs on Cloudflare D1. These are the tables that can contain anything about you:
| Table | What it holds | Why |
|---|---|---|
users | Your account identifier, whether Pro is active, the date it started, and your Stripe customer and subscription identifiers | To know whether to unlock Pro features |
tripstrip_sites | Trip names and a snapshot of each campsite you added | So a trip built on your phone appears on your laptop |
site_notes | The personal notes and road notes you type on a site, as free text | To sync your notes across devices |
road_reports | The road condition you selected, any details you typed, the site it applies to, the time, and your account identifier | To show conditions to other campers |
user_saves | Saved scan names, regions, and site lists | So a scan saved on your phone reloads on your laptop |
Two things worth being precise about. First, community road reports are shown without your identifier — the endpoint that serves them does not return it, so your reports are anonymous to other campers even though we can trace them for abuse handling. Since 25 August 2026 that endpoint is public, so a report you submit is visible to anyone viewing the site, signed in or not, and reports stop being served 90 days after they are posted. Second, saved scans now sync: while you are signed in they are stored in the user_saves table above, and while you are signed out they stay in your browser.
Whether or not you have an account, the app keeps three things in your browser's local storage: your site notes (rb_notes), your road notes (rb_road_notes), and your saved scans (rb_saves). If you never sign in, none of it reaches us. Clearing your browser data deletes it.
Signing in changes this for saved scans only: scans already in rb_saves are uploaded to your account the first time you sign in — up to the limit your plan allows — and from then on the copy in your account is the one the app shows. Anything that could not be uploaded stays in your browser and is labelled this device only in the list.
If you tap Near Me, your browser asks your permission and hands us your coordinates. They are used immediately to work out which state you are in and where to centre the map. They are not stored and not sent to our servers. Decline the prompt and every other part of the app still works.
Upgrading sends you to a payment page hosted by Stripe. Card details are entered on Stripe's systems and are never seen by, transmitted through, or stored by Roam & Board. We pass Stripe your account identifier so that a completed payment can be matched to the right account, and Stripe returns a customer and subscription identifier that we store.
The site uses Cloudflare Web Analytics, which is cookieless: it records page views and performance without fingerprinting you or following you to other sites. Separately, Cloudflare's network keeps standard request logs — including IP address and browser user-agent — as a normal part of serving and protecting the site. We do not build profiles from either.
Using the map necessarily involves other services, because the map, the weather and the road data are theirs. Each receives only what it needs to answer:
These companies process data under their own privacy policies. We do not sell or share your personal information with anyone for their own marketing.
Your trips, notes and reports are kept until you delete them or delete your account. Cloudflare's request logs expire on Cloudflare's own schedule. Stripe retains transaction records for as long as tax and financial law requires, independently of us.
Road reports you submit are intended to be useful to other campers; if you delete your account, your reports are deleted with everything else.
Whether or not a particular privacy law covers you, these are available to everyone:
Colorado residents have rights under the Colorado Privacy Act, including access, correction, deletion, portability, and opting out of targeted advertising, sale, and profiling. Roam & Board does not carry out targeted advertising, sale of personal data, or profiling of any kind, so there is nothing to opt out of. To exercise any right, email roamandboardcamping@gmail.com from the address on your account. We aim to respond within 45 days.
Roam & Board is not intended for anyone under 18, and accounts are limited to adults. We do not knowingly collect information from children. If you believe a child has created an account, write to us and we will delete it.
Traffic is served over HTTPS with HSTS. Passwords are held and hashed by Clerk, never by us. API requests are authenticated with signed tokens verified on every call, and payment webhooks are signature-verified. No system is perfect, and we will not claim otherwise; if something goes wrong that affects you, we will tell you.
If this policy changes materially, the effective date at the top changes and signed-in users are notified in the app before the change takes effect. Continuing to use the service after that means the new version applies.
user_saves; while you are signed out they stay local, as before.Josiah Cloud, doing business as Roam & Board · Colorado, United States · roamandboardcamping@gmail.com