Campmora privacy notice

Campmora is a camping community app. This notice describes the information used by the website and iPhone app.

Information you provide

You can sign in with Apple or a verified email and CM password. Apple supplies an account identifier and an email address, which may be an Apple private relay address. We record your confirmation that you are 18 or older; we do not collect your date of birth for this confirmation. Your profile includes a required name and username, and optional biography, phone number, and profile photo. We store the posts, photos, comments, likes, follows, messages, campground information, amenity reports, and Campfire participation you choose to share.

Who can see your information

Your name, username, profile photo, biography, and profile counts are visible to signed-in members. Private profiles restrict posts and photos to approved followers. Public-profile posts can be discovered by signed-in members. Public POIs, place reviews and review photos can be visible to visitors on the public map regardless of profile privacy. Private-profile viewing rules still apply when opening a member’s profile. Members can search for profiles by name or by a full matching email address or phone number; contact details are not displayed on profiles.

Direct and group messages are available to conversation participants. Campfire messages are shared with participants at your selected campground and campgrounds within 30 miles. Messages show your username and the campground they were sent from. Campfire participation is separate from your public/private post setting. Authorized moderators can review reported content. New public posts, comments, reviews and community POIs are held for administrator approval before they appear to other campers; edits to public content require a new review. Authors can see their own pending submissions. Private posts, direct messages and restricted Campfire chats are not submitted to this public approval queue. These messages are not end-to-end encrypted.

Photos and locations

You choose photos and locations to share. When photo metadata contains GPS coordinates, Campmora adds the detected location to the post draft, with a Remove Location option before posting. Uploaded images are re-encoded without embedded GPS metadata; a retained location is stored separately with the post and shown to its permitted audience. Locate Me uses your device location when requested to center the map. Joining Campfire uses your device-reported position to offer camping facilities within 3 miles and check the distance on the server. That position is not saved to your profile or as a trip; the selected campground and 24-hour Campfire access are saved. Joining does not create a feed post. You can leave Campfire from its details. Map tile providers receive the requested map area. Campmora does not continuously track your location or record background trip breadcrumbs.

Optional background hazard alerts

On supported app versions, you can opt in under Push notifications and choose hazard types independently of map filters. With Always location permission, the app sends recent background positions to Campmora only to check mapped hazards and send alerts when you enter an area or a new alert covers your recent position. Only the latest position and its accuracy/time are retained, for up to 6 hours; it is replaced rather than kept as a route or trip history. Background positions are not used for social discovery, feed ranking, analytics or advertising, and are not sent to NOAA or other hazard sources. Private hazard-match and notification records are retained for up to 7 days. Turning hazard alerts off or signing out stops device updates and requests deletion of its hazard location and subscription; deletion may wait for connectivity, and location records expire within 6 hours. Device permissions can be revoked in Settings. Delivery depends on iOS, network access, fresh location and source availability; this is not an emergency warning or evacuation service.

Location-based feeds

When you request location-based recommendations, your device position is used temporarily to rank public posts by distance. A recent position you requested for Locate Me or Campfire may also be used during the current app session. If that is unavailable, your selected Campfire campground can provide a local reference. Your device position is not saved to your profile or used for background tracking. Without a location reference, recommendations use recency and community engagement. For You ranks friends’ posts using distance and recency; Discover prioritizes distance, recency and community engagement. Public recommendations can fill a quiet feed.

How information is used

Information is used to provide accounts, the map and feed, messaging, notifications within the app, community moderation, and service security. Campmora does not currently run advertising or cross-app tracking. CM requests permission for iPhone push notifications. Apple controls permission; you can change it in CM and iPhone Settings. Device push tokens, unread state and delivery records support these notifications.

Community analytics

For signed-out website use, we record approximate visits and visible foreground time separately from registered accounts. A random first-party browser cookie lasts up to 30 days; private visitor totals are retained for up to 90 days. We do not collect page paths, search terms, content or location for these counts. A daily keyed network identifier is used briefly to limit abuse; raw IP addresses are not stored in the analytics database. We omit recognized pre-launch browsers, known automated clients and browsers sending Do Not Track or Global Privacy Control. Different browsers or cleared cookies may count separately. Reports use Pacific time.

For signed-in accounts, CM records approximate visible foreground time and opens, separated into iPhone app and website usage. These private account/day totals help us understand community activity. We do not record message content, photo content, browsing history or precise locations for analytics. Reporting covers the most recent 90 days; older measurement records are removed as usage is recorded. Usage collection pauses while the app is hidden and excludes the sysadmin dashboard and photo share extension. Authorized sysadmins can review signup contact details and account-setup status, including incomplete registrations, to operate and support CM. Deleting your account removes its usage records.

Experience troubleshooting

For signed-in accounts, we collect limited reports of completed place searches with no results, and slow or failed map-directory loads, feeds, place details, uploads, post/review/POI saves and trip-planning actions. Reports contain a fixed action category, elapsed time, general error category, app or website platform, timestamp and account reference. We do not collect search text, entered addresses, message content, photos, coordinates, request bodies or raw error messages for these metrics. Repeated reports are limited, and only authorized sysadmins can view aggregate counts and timing to improve the service. These records are retained for 90 days and removed when the associated account is deleted.

Trip planning interest

When you calculate a route or save a trip, we record which public Campmora facilities and POIs appear after the origin. We count each place once per trip and account, so repeated calculations do not inflate popularity. Existing saved plans provide an initial baseline. These analytics exclude private addresses, origins, private POIs and waypoint order, and do not establish that you visited or stayed anywhere. Only authorized sysadmins can see aggregate place rankings, which help prioritize reviews and data improvements. The records remain while your account exists; deleting your account removes its contributions.

Failed-route troubleshooting

When a trip route cannot be calculated, we retain a private troubleshooting record containing the submitted stop names and exact coordinates, trip reference, departure and stopover settings, rig specifications, avoidance settings, and provider error and retry results. It can also include the recovery options checked, the option you selected, and whether its route was verified. This may include an origin address you entered. Only authorized sysadmins can review these records to investigate and correct routing issues; they are not public posts or a travel-location history. API keys, sign-in tokens and passwords are not included. Records are available for 90 days and then removed by scheduled cleanup. Deleting the associated account removes its live route troubleshooting records.

Service providers

Apple provides sign-in and TestFlight distribution. Supabase hosts authentication, database records, and uploaded media. Vercel serves the website and server routes. TomTom supplies address searches and route calculations, receiving the submitted trip coordinates, departure time and applicable rig and avoidance settings. Resend delivers verification, recovery and account-security emails. Cloudflare Turnstile checks website authentication requests for automated abuse. Satellite imagery is delivered through CM from USGS services. Geoapify and OpenStreetMap/Overture-derived place data support the directory and readable photo locations. Street-map tiles are requested from OpenStreetMap, which receives the network request and map area requested. Providers may process technical information such as IP addresses and service logs under their own policies. TestFlight feedback and crash information may be shared with the developer through Apple.

Your choices and retention

You can edit your profile, change public/private visibility, remove content using the controls offered in the app, and block or report members. Data is retained while needed to operate your account and the service; security logs, backups, and records needed to resolve abuse may remain after content is removed. To delete your account, open ☰ → Account → Delete account and confirm DELETE. We remove your sign-in, profile, posts, uploaded photos, reviews, comments and messages. Most requests finish immediately. A failed processing attempt or shared ownership may need staff attention, with a 7-day processing target. Shared profiles are not automatically erased out from under another owner. De-identified campground facts may remain; personal attribution is removed. Backups and technical service logs expire under provider retention schedules and are not part of the live community. A minimal deletion receipt retains the request date and outcome without the deleted login ID. Apple users can remove CM from Sign in with Apple settings if automatic token revocation is unavailable; this does not block CM data deletion. For other access or correction questions, contact us from the email associated with your account.

Age requirement

CM accounts and community features are for adults 18 and older. The age confirmation is self-declared and is not an identity-verification service. If you believe a minor has created an account, contact us.

Contact

For privacy questions, account deletion requests, or beta feedback, email contact@airlineboard.com.