Privacy Policy

This policy applies to the No Map Required website and app, including camping discovery, saved locations, trip planning, check-ins, the traveler community features and paid memberships.

Account information. When you create an account we store your email address and a display name. If you sign in with Google, we receive the basic profile information that sign-in provides.

Profile and rig setup. Anything you choose to enter: display name, home region, bio, avatar or rig photo, camping style, vehicle details and fuel details. All of it is optional beyond a display name.

Your content and activity. Saved locations, trips and trip stops, check-ins (including the coordinates you check in from, because a check-in is verified against the location), reviews, photos, reports, feedback, community profile fields, buddy requests and direct messages.

First-party analytics. We record a fixed list of product events by name — for example that a search happened, a location page was viewed, a location was saved or a trip was created. Events store the event name, a timestamp, an optional target id (such as which location), a small set of primitive-valued fields, the campaign and creative tags from your first touch (utm_campaign, utm_content) when you carried them, and your account id when you are signed in. We do not record page contents, full URLs, query strings, keystrokes, scrolling or session replays, and the Reddit click id is never attached to an event.

Acquisition attribution. If you arrive from a campaign link or another site, your browser remembers the campaign tags you carried (utm_source, utm_medium, utm_campaign, utm_content, utm_term), the referring site's host name, the path you landed on, and — for Reddit ad links — the click id Reddit adds to the URL. This is stored once as a "first touch" and is never overwritten by later visits. Once you have an account it is attached to your account.

Payments. Paid memberships are processed by Stripe. Card numbers never reach NMR. We store the identifiers and subscription status we need to know whether your membership is active.

Technical logs. Our hosting and backend providers process ordinary request information (such as IP address and user agent) in order to serve and secure the app.

• No advertising pixels or third-party ad trackers. NMR does not currently run Reddit Pixel, Reddit Conversions API, Meta Pixel, Google Ads tags or any other advertising SDK.
• No third-party analytics SDK. Product analytics is first-party and server-side.
• No background or continuous location tracking. Location is only read when you ask for it — a nearby search or a check-in.
• No selling of personal information.

• To run the product: sign you in, show your saved locations and trips, plan routes, verify check-ins and award journey progress.
• To operate community features you switch on yourself, such as discovery, buddy requests and messages.
• To manage memberships and entitlements, including verifying payment status.
• To understand, in aggregate, how the product is used and where members came from, so we can decide what to build and where to spend.
• To keep the service safe: reviewing reports, moderating content and preventing abuse.

Analytics is used in aggregate by NMR operators. It is never exposed to other members, and there is no interface that returns raw event rows.

Community visibility is off by default. Nothing about you appears in traveler discovery, messaging or trip visibility until you turn it on in Privacy & visibility. Any region shown is the general region you typed yourself, never a GPS position.

Content you deliberately publish — reviews, photos, reports on a location — is visible to other travelers alongside that location.

Your data is stored in our managed backend (a hosted Postgres database with private file storage) and is kept while your account exists so the product can show it back to you. We have not set fixed deletion timers for every record type; instead, deletion happens when you delete content or when you ask us to delete your account, and analytics is kept as an append-only log of event names and timestamps.

Access to your rows is enforced at the database level, so one member's account cannot read another member's private data. Analytics events and acquisition records are not readable by members at all.

You can edit or remove your profile details, photos, saved locations, trips and community fields yourself at any time. To delete your account, contact us through the channels on the contact page and we will remove your account and the personal data attached to it.

Two things survive by design: your member position number is retired rather than reused, and aggregate, non-identifying counts already recorded remain in aggregate reporting. Cancelling a paid membership does not delete your account or your data.

We use third-party infrastructure to run NMR — hosting, the managed database and file storage, email delivery for account emails, Stripe for payments, and public agency and mapping data sources for camping information. They process data on our behalf in order to provide those services.

Traffic to NMR is served over HTTPS. Access to your data is restricted per account at the database level, private files (such as avatars and rig photos) are served through short-lived signed links rather than public URLs, and operator-only reporting requires a verified admin or moderator role. No online service can promise perfect security, and we do not claim any certification or compliance audit.

NMR is intended for adults. It is not directed at children, and we do not knowingly collect information from children.

• Access or correct your information: most of it is editable in your profile and settings.
• Turn community visibility on or off at any time in Privacy & visibility.
• Clear your browser's stored campaign attribution by clearing site data for NMR.
• Ask us for a copy of your data, or ask us to delete it, through the contact page.

Depending on where you live you may have additional rights over your personal information. Contact us and we will work through your request.

We will update this page when our practices change and will change the "last updated" date above. Significant changes will be announced in the app.

Questions about privacy? Reach us through the contact page. Related pages: Cookies & Tracking and Terms of Use.