Legal
Privacy Policy
The short version
- We collect what Camplore needs to work: your account, the places, trips and check-ins you save, and basic usage and crash data.
- Your saved sites, trips and check-ins are private by default. Nobody else sees them unless you share them.
- We use your location only while you're using the app, to center the map. We don't track you in the background.
- We don't sell your data, and Camplore has no ads.
- You can export your data or delete your account from inside the app at any time.
Who we are
Camplore is an app for finding legal places to camp on public land, planning trips and keeping a camping journal. It is operated by Camplore LLC, a Colorado limited liability company ("Camplore", "we", "us"). Questions about this policy or your data: hello@camplore.app.
What we collect
On the website (camplore.app)
- Waitlist sign-ups. Your email address, when you signed up and confirmed it, and where you came from (for example a link from a partner, or "direct"), including the tags on the link if it had them (source, medium, campaign and content). We email you once to confirm the address. After that, confirmed addresses get updates about Camplore before and at launch: progress news, beta invites, your referral link, and early-access offers such as the Founding Member presale.
- Website analytics. Pages viewed, the referring site and campaign tags, browser and device type, which links and buttons you click, how long you stay and how far you scroll, and whether you joined the waitlist. We use PostHog for this, reached through our own domain. It stores an identifier in your browser's local storage so return visits can be counted. We don't record your screen on the website.
- Guide maps. The Colorado guides (camplore.app/guides/) show a map from Mapbox, with Camplore's public-land and road overlays served through Cloudflare. Loading the map sends your device's IP address and the map area you're looking at to them, like any web request. The page doesn't ask for your location, and we don't record where you look.
- Trip invite pages. When you open a trip invite link (camplore.app/t/…) without the app, the page loads a short preview of that trip from our database: its name, dates, the first name of the person who invited you, how many stops it has and the general area. It never shows exact locations. The link itself works like a key, so we keep these pages out of search engines and don't pass the link on to other sites. The same goes for site links (camplore.app/s/…) and badge links (camplore.app/b/…).
- Profile pages. When you open someone's profile (camplore.app/u/…), the page loads what that person shows publicly on Camplore from our database. It never shows where they camped. See What other people can see.
In the app
- Account. Your email address and a password (stored securely by our authentication provider), or the name, email and profile photo shared by Sign in with Apple or Google if you use those. Your account's email address is also sent to OneSignal, our email provider, so we can send you account and Camplore emails (see below). With it, OneSignal receives a few counts about your use of the app (how many trips, check-ins and saved sites you have), so we can send emails that fit, such as a tip about planning a trip if you haven't made one yet. It never receives your sites' locations or anything you've written.
- Sign in with Google. If you sign in with Google, we receive your name, email address and profile photo from your Google account. We use them only to create and run your Camplore account: your name and photo on your profile, and your email to sign you in and send you account messages and Camplore's own emails about using the app, which you can unsubscribe from in any of them. We don't sell them, use them for advertising, or share them with anyone except the service providers listed below that run Camplore. Camplore's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
- Trip invites before you have an account. Joining a trip needs an account. If you open an invite first, the app keeps the invite on your phone and joins you to the trip once you've signed up or signed in. Before October 12, 2026, people could join as a guest with no name or email; those guest identities are only used for the trips they were invited to, and move to an account if one is made.
- Profile. Anything you add: display name, bio, profile photo, vehicle type and unit preferences.
- Things you create. Campsites you save (including their map coordinates), tags, trips, stops, packing and grocery lists, meals, check-ins, journal entries, and the photos and videos you attach.
- Location. With your permission, your device's location while the app is open, used to center the map and suggest nearby spots. We don't collect location in the background and don't store your device's location on your profile. The places you choose to save do include their coordinates.
- Photos, camera and microphone. Only when you choose to attach a photo or video to a campsite, check-in, journal or your profile. Before a photo or video is uploaded, the app removes the metadata your phone adds to it, including where it was taken and which device took it; the copy on your phone keeps it.
- Usage analytics. Which screens and features are used, app version, device model and operating system, and anonymized recordings of app sessions to find where people get stuck. In those recordings, text you type, images and maps are masked, so they can't show your writing, your photos or where you are.
- Crash reports. Technical details when the app crashes or hits an error, linked to your account ID only, not your name or email.
- Notifications. A device token so we can send push notifications you've allowed, such as reminders about unfinished drafts.
- People you share with. If you share a site by typing someone's email address, we store that address with the share, so the site appears for them once they have an account, and we email them to let them know. We send that email even if they've unsubscribed from Camplore's other emails, because you asked us to send it.
- Your handle and the people you follow. In test versions of the app: your @handle (we make one from your name, and you can change it), an optional link on your profile, whether your account is Private, who you follow and who follows you, friend requests and friends, and the posts you give a thumbs up. If you share a site with a friend or add a friend to a trip, we store that too.
- Reports, hides and blocks. If you report someone's site, photo or lore, we store the report (what you reported, the reason and any note you add) with your account, so our team can review it. The person you reported isn't told who reported them. If you hide something or block someone, we store that too, so it stays hidden on all your devices. The person you block isn't told.
- Tester feedback. If you are a beta tester we have added to our testing list, we store the test tasks assigned to you and your answers: your result or rating, any comments you write, the phone model you optionally enter, and when you opened and answered each task. You can also send us feedback from inside the app (the Beta tab), and the app may ask after you take a screenshot whether you want to send it. With an answer or feedback sent from the app we store what you write, any screenshot you choose to attach (a picture of the app's screen, or one you pick from your photos), and details the app adds: which screen you were on, the app version, your phone model and system version, which test build you use, and the ids of that moment in our crash reporting (Sentry) and analytics (PostHog), so we can see what led up to it. Screenshots are kept privately, and you can remove one before sending. If you send feedback or a crash report through Apple's TestFlight app, Apple passes it to us with your email address, and we copy it (your comment, any screenshot, your phone model and system version, and the build) into the same list, matched to your Camplore account if one uses that email; we keep the email itself only when no account matches. At the end of the alpha and the beta we may ask you to fill in a short survey on the tester page; we store your answers the same way. Only you and the Camplore team can see any of this. We use an AI assistant (Anthropic's Claude) to read and sort tester answers and draft our replies; it sees your answers and comments, not your name or email. Using the tester page at camplore.app/testers needs your Camplore sign-in, and nobody else can open it.
- Purchases. Your subscription status and purchase history. Payments are handled by Apple or Google, or for a purchase on the web by Stripe, which sells it to you through its Link checkout as the merchant of record; we never see your card details.
- Mailing address for badge patches. If you're on Camplore Plus and ask us to mail you a badge's woven patch, we store the name and US mailing address you enter, and a copy of it with each patch you ask for, so the envelope goes where you confirmed. The address is saved so the app can offer it for your next patch, and you can change it then. Only you and the Camplore team can see it. We use it only to mail your patches, which we post ourselves with the US Postal Service. It's deleted with your account.
- Beta tester thank-you. If you were in Camplore's closed beta, the tester page at camplore.app/testers asks where to mail your thank-you pack (stickers, a patch and a note). We store the name and US mailing address you enter there the same way as a badge-patch address: only you and the Camplore team can see it, you can change it until the pack is mailed, we use it only to mail the pack ourselves with the US Postal Service, and it's deleted with your account. At launch we also look up the email address of your beta account to find your Camplore account with the same email, so we can add the Beta Crew badge and a year of Camplore Pro to it. The Pro year is recorded with RevenueCat, our subscription provider, under your account's id.
How we use it
- To run Camplore: sign you in, save and sync your data across devices, show the map, and provide the features you use.
- To manage subscriptions and Founding Member access.
- To send notifications you've turned on, and, if you joined the waitlist, emails about Camplore's launch, beta invites, your referral link and early-access offers such as the Founding Member presale.
- If you have an account, to email you about your account and about using Camplore: getting started, reminders about trips you've planned, seasonal ideas, and offers such as sales on Camplore Plus. Every one of these emails has an unsubscribe link.
- To understand how Camplore is used, fix bugs and crashes, and improve the app.
- To keep Camplore secure and prevent abuse.
We don't sell your personal information, share it for targeted advertising, or show ads.
Who we share it with
We use a small set of service providers who process data on our behalf, only to provide their service to us:
| Provider | What they do |
|---|---|
| Supabase | Accounts, database and file storage, including the waitlist |
| Anthropic | Claude, the AI assistant we use to build Camplore, reads beta testers' answers and comments so we can fix what they find. It doesn't receive testers' names or email addresses. |
| Bluehost | Hosts the website |
| Cloudflare | Runs camplore.app's domain name service and serves the map's overlay tiles. Like any web request, a tile request carries your device's IP address and the map area being loaded. |
| PostHog | Website and app analytics, and masked app session recordings |
| Sentry | Crash and error reports |
| OneSignal | Push notifications, waitlist emails (starting with the confirmation email), account and Camplore emails to account holders (it receives your account's email address and counts of your trips, check-ins and saved sites), the email we send when you share a site with someone by their address, and the notifications you choose to get by email (it receives their words: for example a first name and a trip name). If you tick Email for a notification in the web app, your browser loads OneSignal's web software to connect your address, even if browser notifications are off. |
| hCaptcha | Checks that a real person is signing up or signing in with email. It receives technical signals from your device, such as browser or app details and how the form is used. |
| RevenueCat, Apple, Google | Subscriptions and in-app purchases |
| Stripe (Link), RevenueCat | Web purchases of Founding Member and subscriptions, where they're offered. Stripe is the merchant of record: it sells the purchase to you through Link, its checkout service, and receives your email address, card details and billing location (which it needs to work out tax) to take payment, handle tax and prevent fraud. For that it acts as an independent controller of your data under the Link Privacy Policy, and a Link account is used to manage a web subscription. RevenueCat receives the purchase record and your Camplore user ID so we can unlock what you bought. We don't see your card. |
| Apple, Google | Sign-in, if you choose Sign in with Apple or Google |
| Mapbox | Maps. Mapbox's software may collect usage and approximate location data under Mapbox's privacy policy. |
| U.S. Geological Survey | Elevation for a site, shown on Site Detail and on share cards. It receives the site's coordinates, not who you are. |
| U.S. National Weather Service, NOAA, Iowa State University's Iowa Environmental Mesonet, and Esri (which hosts NOAA's smoke data) | Weather forecasts for your trips and the weather layers on the map. They receive the coordinates or map area you're viewing, not who you are. |
We may also disclose information if required by law, to protect someone's safety, or as part of a sale or reorganization of Camplore, in which case this policy would continue to apply to your data.
What other people can see
- Your saved sites, trips, check-ins and journal are private by default.
- When you invite people to a trip, the people who join can see the whole trip: its dates, notes, stops and the campsites on it (including their exact locations), meals, packing and grocery lists. They also see the name and profile photo of everyone on the trip, and you see theirs. People you let edit can change the plan; people you let view can only look.
- Anyone who has an invite link can see a short preview of the trip before joining: its name, dates, your first name, how many stops it has and the general area, but not where the campsites are. Joining needs an account. Invite links stop working after 14 days, you can turn one off at any time from the trip's Crew tab, and you can remove anyone from the trip, including everyone who joined with a particular link.
- When you check in at a stop during a trip, the people on that trip can see that check-in: its date, number of nights, your short note and its photos and videos. Your journal for that check-in stays private unless you choose to share it with the trip, which you can change for each entry at any time. A shared journal entry doesn't add anything about where you were beyond the stop that people on the trip can already see.
- When you send a link to a site with Share this site, you choose how much of its location the link shows: the exact location (public sites only), the name of the area it's in (such as a national forest), or nothing. A shared or private site is never shown more exactly than its area. Anyone who has the link can also see the site's type, tags and photos (with their location data removed), and the check-in notes other people can already see there. A link stops working after 90 days; you can turn one off sooner in You › Shared links, and changing a site to Private turns off every link to it.
- Each site has a visibility setting, and new sites start as Private. If you make a site Public, your check-in notes there, with your display name, the date and the number of nights, are visible to other Camplore users. In test versions of the app, a Public site also appears on other people's maps with its exact location, type, tags and photos, and a Shared site appears only for the people you add. Your private notes and your journal are never shown with a site.
- When you share one of your check-ins, or a trip that's over, Camplore makes a card for it: as a link (camplore.app/c/…) or as a picture you can post. Anyone who has the link or the picture sees the date and number of nights, your first name, up to three photos (your own from that check-in or trip first, then the site's own photos if the site is public or you added them, all with their location data already removed), your lore from that check-in, the site's tags, its elevation, and any badges you earned then. If you switch on Include journal for that share, it also shows your journal's title and first few lines. A trip card also shows the trip's name, how many stops and check-ins it had, and how many people were on it, but not who they were. You choose how much of the location goes with it, the same way as a site link: the exact spot (a public site's check-in only), the area's name, or nothing; a trip card never goes closer than the area. A card never includes your journal or anyone else on the trip. You can turn a card's link off in You › Shared links, and leaving a trip turns off the cards you made for it. A picture you've already posted stays wherever you posted it.
- When you share a badge with Share badge, anyone who has the link can see a page with that badge, its tier, the date you earned it and your first name. It never shows where you camped. You can turn a badge link off in You › Shared links. If you add a badge to a trip with Add to trip lore, the people on that trip see it on the trip's log.
- In test versions of the app, you have a profile at camplore.app/u/your-handle. Anyone except people you've blocked can see your display name, handle and profile photo there, in the app or on the website, even without an account. Unless your account is Private, they can also see your bio and link, how many people follow you and how many you follow, how many nights you've camped, and anything you put on your profile:
- journal entries you put on your profile;
- check-ins you choose to show there;
- your badges;
- the public sites you've added, showing their type, elevation and rating.
- Your profile photo is stored at a link that anyone with the link can open. Don't use a photo you'd want kept private.
Keeping and deleting your data
- Delete your account in the app (You → Delete account). This permanently removes your profile, saved sites, trips, check-ins, journal entries and media, and asks our push, subscription and analytics providers (OneSignal, RevenueCat and PostHog) to delete what they hold about you. Trips you created are deleted for everyone on them; trips other people shared with you stay with them, and you're removed from them. Sites you made public stay on the map for others without your name; a private site stays only if it's part of someone else's trip or check-in. Deleting your account doesn't cancel a subscription; cancel it in the App Store, Google Play or your Link account so you aren't billed again. Stripe keeps its own record of a web purchase under the Link Privacy Policy.
- Export your data in the app (You → Export my data) as a file you can keep.
- Leave the waitlist by using the unsubscribe link in any email, or by writing to hello@camplore.app.
- Stop Camplore's emails to your account by using the unsubscribe link in any of them, by unticking Email for a notification in the web app's You → Notifications, or by writing to hello@camplore.app. Messages you need to use your account, such as sign-in and password emails, still arrive.
- We keep your data while your account is active. Analytics and crash data are kept for a limited period and then deleted by our providers. Backups may take a short while longer to clear.
Your choices and rights
- You can turn off location, photo, camera, microphone and notification access at any time in your phone's settings. Camplore still works; some features won't.
- You can ask us to access, correct, export or delete your personal information, or to stop using it for analytics, by emailing hello@camplore.app. We'll respond within 45 days.
- Depending on where you live, including Colorado and California, you may have additional rights under state privacy laws. We honor these requests for everyone, wherever you live.
Children
Camplore isn't directed to children under 13, and we don't knowingly collect personal information from them. If you believe a child has given us information, contact us and we'll delete it.
Security
We protect your data with encryption in transit, access controls that limit each account to its own data, and providers with established security programs. No system is perfectly secure, but we work to keep your information safe and will notify you as required by law if a breach affects you.
Changes to this policy
If we change this policy, we'll update the date at the top. If a change materially affects how we use your information, we'll let you know in the app or by email before it takes effect.
Contact
Camplore LLC · Colorado, USA · hello@camplore.app