CampGuide Privacy Policy

Last updated: July 29, 2026

CampGuide Inc ("CampGuide," "we," "us," or "our") operates CampGuide, a platform that helps campgrounds and RV parks run their businesses and helps campers find and book a place to stay. This Privacy Policy explains what information we collect, how we use it, who we share it with, and the choices and rights you have.

This policy applies to the CampGuide websites, apps, and products, including:

software.campguide.app, our marketing site, where you can request an invitation, download a report, or subscribe to our newsletter
campguide.app, the CampGuide application. This single app serves the operator console used by campground and RV park businesses ("CampGuide Host"), the traveler experience and CampGuide ID account, each park's public page and booking checkout at campguide.app/<park>, and the guest Stay Hub
park websites and booking pages published through CampGuide, including a park's own custom domain connected to our Website Builder, and legacy per-park subdomains such as <park>.campguide.app
the CampGuide Host mobile app for park staff
sandbox.campguide.app, our test-mode environment
any other page, feature, email, text message, or service that links to this policy

We refer to all of these together as the "Services."

Please read this policy together with our Terms of Service. If you do not agree with it, please do not use the Services.

Note on how to read this policy. CampGuide plays more than one role depending on whose information is involved, and that distinction shapes the rest of this document. Section 2 explains it. It matters most if you are a camper, because for most of the information a park holds about you the park is the party in charge, and your requests go to that park rather than to us.

Who we are
Our roles: controller, service provider, and CampGuide ID
Information we collect
How we use information
Consent and how we record it
Text messages and SMS
Email and push notifications
Payments
Identity verification (CampVERIFY)
Channel distribution and online travel agencies
Artificial intelligence features
How we share information
Service providers and sub-processors
Cookies and tracking
How we protect information
How long we keep information
Your privacy choices and rights
U.S. state privacy rights
Notice for the EU, EEA, UK, and Switzerland
International data transfers
Children's privacy
Third-party links
Changes to this policy
Contact us

1. Who we are

CampGuide is operated by CampGuide Inc, a Delaware corporation. Our mailing address and contact details are in Section 24.

Throughout this policy we use a few terms:

Operator (also "Park" or "Customer") means a campground or RV park business that subscribes to CampGuide Host and uses it to manage sites, reservations, payments, and guests. Where several parks are run as one organization or portfolio, the organization and its parks are treated together.
Guest (also "Camper") means an individual who books, stays at, or otherwise interacts with a park through the Services.
Traveler means an individual who holds a CampGuide ID, our optional portable camper account described in Section 3.3.
Personal information means information that identifies, relates to, or could reasonably be linked to a particular person or household. It does not include information that has been aggregated or de-identified so that it can no longer be tied to a person.

2. Our roles: controller, service provider, and CampGuide ID

CampGuide handles personal information in more than one capacity. Knowing which one applies tells you who to go to with a request.

When we act as the controller. For some information we decide why and how the information is used, so we are the controller (the "business" under U.S. state laws). This covers:

information about Operators and their staff, such as account and contact details, role assignments, and subscription billing
information about people who visit our marketing site, request an invitation, download a report, contact us, or subscribe to our newsletter
information we collect automatically through the Services for security, troubleshooting, and product improvement
the CampGuide ID account itself, as described below

When we act as a service provider. When an Operator uses CampGuide Host to manage its business, the Operator enters and generates information about its guests, reservations, payments, and communications. For that information the Operator is the controller, and CampGuide acts as a service provider (a "processor") that handles the information only to provide the Services and only on the Operator's instructions. We do not use guest information for our own independent purposes such as marketing to those guests.

If you are a Guest and you want to access, correct, delete, or otherwise control the information a park holds about you, please contact that park directly. The park is the party responsible for deciding how your information is used. If you send a request to us, we will, where appropriate, pass it to the relevant Operator or ask you to contact them, and we will support the Operator in responding. Our handling of guest information is also governed by our agreement with the Operator, which controls if there is any conflict with this policy. Operators who need a data processing addendum can request one using the details in Section 24.

CampGuide ID. A camper can also hold an optional CampGuide account, the CampGuide ID, which is separate from the records a park keeps. For the CampGuide ID account, its profile, and the sharing choices attached to it, CampGuide is the controller and you can contact us directly. When you use that account to book, the information you agree to share is passed to the park, and from that point the park's copy of it is the park's responsibility as controller. Holding a CampGuide ID is never required to book a stay.

3. Information we collect

3.1 Information Operators and staff provide

When an Operator sets up and runs a park on CampGuide Host, we collect:

Account and identity details: name, business email address, phone number, and the password used to sign in. Operator and staff accounts are created by invitation.
Business and park details: legal and trade names, park address and location, time zone, currency, photos, site maps, house rules, and policies entered during setup.
Role and team information: the roles assigned to each staff member (such as owner, manager, front desk, housekeeping, or maintenance), organization-level roles for multi-park portfolios, and a record of actions taken in the account.
Payout and tax onboarding details: information needed to accept payments and receive payouts. This is collected and verified directly by our payment provider, Stripe, during Connect onboarding. We receive the resulting account status and limited summary details, not full banking or government identification numbers. See Section 8.
Subscription and billing details: plan, status, and the billing information needed to manage your CampGuide subscription, processed through Stripe.
Content you upload: including park map images, which may be processed to detect site labels as described in Section 11.
Device and notification details: if you enable browser or mobile notifications, the push subscription identifier for that device.

3.2 Information about Guests

Most guest information is provided by the Operator or by a Guest during online booking, and we process it on the Operator's behalf as described in Section 2. It can include:

Contact and identity details: name, email address, phone number, and mailing or billing address.
Reservation details: arrival and departure dates, the site or site type booked, party size (adults, children, and pets), vehicle and rig details such as class, length, height, and hookup needs, referral source, and any notes added to the reservation.
Payment records: the amounts charged, paid, refunded, or held, the payment method type, and transaction status. Card numbers and similar payment credentials are handled by Stripe, not stored by us. See Section 8.
Folio and billing history: invoices, line items, deposits, fees, adjustments, point-of-sale purchases at the camp store, and any guest credit balance.
Communications: the content and delivery status of messages exchanged through the platform by SMS, email, in-app chat, and push notification, including replies a Guest sends through a tap-to-reply link.
Consent records: what a Guest agreed to, when, and the exact wording and version they saw. See Section 5.
Documents and signatures: agreements, waivers, leases, and check-in confirmations that a Guest signs electronically, along with the related signing events and timestamps.
Identity verification results: where a park uses CampVERIFY, whether a check passed and when. See Section 9.
Reviews and loyalty: ratings and category feedback that a park records about a Guest after a stay, and loyalty balances where a park or portfolio runs a loyalty program.
Utility usage: electric, water, or gas meter readings recorded for long-stay guests, used to calculate utility charges.

Where a park belongs to a multi-park organization, that organization may maintain a shared guest record across its own parks. The organization and its parks remain the controller of that record.

3.3 CampGuide ID traveler accounts

If you create a CampGuide ID, we collect and hold, as controller:

your account and profile details, such as name, email address, phone number, and password
your camping preferences and your rig inventory, such as class, length, height, and tow length
your stays timeline across parks, and any household members or trip companions you invite
saved payment methods, which are stored by Stripe and referenced by a token, not stored as card numbers by us
your sharing choices, including which fields you shared with which park, when, and the exact consent wording you agreed to

You control this account. See Section 17 for the self-service tools available to you.

3.4 Information from our marketing site

On software.campguide.app we collect what you submit to us, such as your name, park name, email address, and the operational figures you enter to generate a report, along with your marketing preferences and unsubscribe status. We use a customer relationship management service to manage these inquiries and an email delivery provider to send the resulting emails.

3.5 Information we collect automatically

When anyone uses the Services, we and our providers collect certain technical information, including:

IP address, device and browser type, operating system, and language and regional settings
pages viewed, links clicked, searches run, and timestamps and other usage activity
the referring page and the page you navigate to next
error and diagnostic data when something goes wrong, and edge request logs used to serve, secure, and rate limit the Services

We use this information for security, fraud prevention, rate limiting, troubleshooting, and improving the Services. Some of it is collected through cookies and similar technologies, described in Section 14.

3.6 Information from other sources

We may receive information about you from sources such as our payment provider (transaction and payout status), our messaging provider (delivery and opt-out status), our email provider (bounce and complaint status), our identity verification provider (verification outcome), connected online travel agencies (bookings made on those channels, see Section 10), analytics providers, and publicly available sources. Operators may also import existing guest, reservation, and site records into CampGuide Host.

We do not seek to collect sensitive categories of information such as race, ethnicity, religious beliefs, health, or sexual orientation, and we ask that Operators do not enter that kind of information into the platform unless it is genuinely required and lawful. The one place the Services touch government identification is the optional identity check described in Section 9, which is run by a specialist provider rather than stored by us.

4. How we use information

We use information for the following purposes:

to create and secure accounts and verify who is signing in
to provide the Services, including taking bookings, pricing stays, processing payments, managing folios, coordinating cleaning and maintenance, and running the camp store
to send transactional messages such as booking confirmations, pre-arrival and check-in information, balance reminders, departure notices, and receipts
to enable communication between parks and their guests by SMS, email, in-app chat, and push notification
to generate documents for electronic signature and to record self check-in
to run an identity check when a park asks for one, and to record the outcome
to calculate utility charges for long-stay guests from meter readings
to publish a park's public page, booking checkout, and website, including on a custom domain
to exchange availability, rates, and bookings with the online travel agencies a park connects
to produce reports and analytics for Operators about their own parks
to provide customer support and respond to inquiries
to maintain security, prevent and investigate fraud and abuse, and enforce our Terms of Service
to operate, troubleshoot, and improve the Services
to comply with our legal, tax, and accounting obligations
with consent where required, to send Operators and prospective customers marketing about CampGuide

We use guest information only to provide the Services to the relevant park, and not to independently market CampGuide products to guests.

Several parts of the Services ask for your agreement, including the legal agreement at checkout, email marketing opt-in, text message consent, waitlist notifications, and the reuse of a verified identity at another park.

When you give one of these consents, we record what you agreed to along with the exact wording and version you were shown, the date and time, and the park it applies to. We keep that record so a park can demonstrate the basis for contacting you, and so you can see the same wording later. Consent language is versioned rather than edited in place, which means the record always reflects what you actually read.

Withdrawing a consent is always available and takes effect going forward. Withdrawing it does not erase the record that it was given, because that record is the proof the consent existed.

6. Text messages and SMS

Parks use CampGuide to send guests text messages about their reservations, such as confirmations, check-in links, and balance reminders, and guests can reply by text. To support this, each park is assigned a dedicated phone number, and CampGuide registers messaging campaigns under the carrier program known as A2P 10DLC.

A few points about how SMS works on the platform:

Consent. A park should obtain a guest's consent to receive text messages before messaging that guest, and may only send messages related to the guest's stay and account. Operators are responsible for the messages they send through the platform. Consent is captured and recorded as described in Section 5.
Opting out. A guest can stop receiving messages at any time by replying STOP. Replying START resumes messages, and replying HELP returns help information. We honor these keywords automatically and record opt-outs so that suppressed numbers are not messaged again.
Costs. Message and data rates may apply depending on the guest's mobile carrier and plan. CampGuide does not charge guests for text messages.
Transactional messages. Even after opting out of non-essential messages, a guest may still receive certain confirmations or receipts that are part of completing a booking, where permitted by law.

We do not sell or share mobile phone numbers or SMS consent information with third parties for their own marketing.

7. Email and push notifications

Transactional and marketing email is delivered through our email provider. When an email bounces or is reported as spam, we record that so we stop sending to the address. Marketing emails include an unsubscribe link, and a guest can also use the preference center link in a park's messages to turn off communications from that park.

Push notifications are optional. If you allow them in your browser or on your device, we store the subscription identifier for that device and send notifications only while that permission and the related consent remain in place. Turning notifications off in your browser or device settings stops them, and you can also turn them off in the product. Push is an additional convenience channel; email and SMS remain the channels parks rely on.

8. Payments

Payments on CampGuide are processed by Stripe, including online card payments, in-person card payments through Stripe Terminal and Tap to Pay on supported devices, saved payment methods, and payouts to parks through Stripe Connect.

When a payment is made, card and bank details are collected and processed by Stripe over an encrypted connection. CampGuide does not receive or store full card numbers.
CampGuide operates as the platform in the Stripe Connect relationship. A park completes Stripe's onboarding, and Stripe verifies the business and payout information directly. We receive the park's account status and limited summary details so we know whether the park is able to accept charges.
We retain transaction records such as amounts, dates, status, and the related reservation or order, which we need to provide receipts, run reports, reconcile payouts, handle refunds and disputes, and meet our financial recordkeeping obligations.

Stripe's handling of payment information is governed by Stripe's own privacy policy at https://stripe.com/privacy.

9. Identity verification (CampVERIFY)

Some parks ask guests, and some ask long-term workers, to confirm their identity before or during a stay. This optional feature is called CampVERIFY, and the check itself is run by our verification provider, Didit, in a hosted flow.

What the check does. It confirms that a government photo ID is genuine, captures a live selfie to confirm a real person is present, and compares the face in the selfie to the photo on the ID.

What CampGuide keeps. We keep the outcome of each check, when it was done, the park that requested it, the provider's session reference, and how the result was reached (for example, completed in the hosted flow, confirmed manually at the front desk, or reused from a previous verification). We do not store your ID document images or your selfie on your CampGuide record, and no park sees your ID number or your photos. The images and the underlying signals are handled by Didit under its own privacy policy and retention practices.

Reuse across parks. If you verify at one CampGuide park, you can choose to let another CampGuide park see that you are verified without repeating the check. That reuse happens only with your consent, shares only your verified status and when and where it was verified, never your documents or photos, applies to the park you agreed to, and can be stopped at any time. The exact wording you agreed to is recorded with the grant.

Fees. Depending on the park's settings, a one-time identity verification fee may appear on your folio.

If a check does not pass. A failed or unfinished check does not cancel your booking. You can try again or verify in person at the front desk.

10. Channel distribution and online travel agencies

A park can choose to connect CampGuide to online travel agencies and other booking channels through our channel management integration. This feature is enabled park by park.

What we send out is inventory information: availability, rates, and booking restrictions. That information is about sites and pricing, not about people.
What comes back is a reservation made on that channel, including the guest details the channel provides, such as name, contact details, stay dates, and party information. Once that reservation is in CampGuide, the park is the controller of it in the same way as a direct booking.
The channel you booked through also holds your information under its own privacy policy, which is separate from ours and from the park's.

If a park has not connected any channel, no reservation or guest information flows through this integration.

11. Artificial intelligence features

Some features use AI models provided by a third-party AI provider to save operators time. These are the places we use them, and what they see:

Reading a park map. When an operator uploads a site map, we use an optical character recognition service and, for labels that OCR cannot read, an AI vision model to locate site labels. The input is the map image the operator uploaded. Results are always presented as drafts for the operator to review.
Drafting site descriptions and marketing copy. The input is site and amenity details, such as name, type, hookups, and length.
Market research (MarketRadar). The input is publicly available information about nearby competing parks, including public business listings and public reviews gathered from a business-data provider and public web pages. It is used to summarize themes and rates, not to profile individuals.
Revenue assistant. The input is an aggregate, park-scoped snapshot of that park's own operating figures, such as occupancy and rate trends. The assistant is read-only, has no ability to take actions, and cannot see another park's data.

Guest contact details, payment information, message content, and identity verification data are not sent to these AI features. Under our provider's commercial terms, content sent through its API is not used to train its models. Every AI output in the product is a draft or an explanation for a person to review, and no AI feature makes an automated decision that produces a legal or similarly significant effect about anyone.

We do not sell personal information for money. We do use analytics cookies on our marketing site, including Google Analytics, and under some state privacy laws that activity may be treated as a "sale" or as "sharing." You can opt out of it as described in Sections 14 and 18. Apart from that, we disclose information only as described here.

With the relevant park. When a Guest books or stays at a park, we share that Guest's information with the park so it can manage the reservation and the stay. The park's use of that information is governed by the park's own privacy practices. Where a park belongs to a multi-park organization, that organization may also have access.
With another CampGuide park, at your direction. A verified identity or a CampGuide ID profile field is shared with a second park only when you consent to it, and you can stop that sharing at any time.
With booking channels a park connects. As described in Section 10.
With service providers. We use the categories of providers described in Section 13 to host the platform, process payments, send messages and email, verify identity, enable e-signature, read utility meters, distribute inventory, and monitor for errors. They may access information only as needed to perform their work for us, under contracts that require them to protect it and bar them from using it for their own purposes.
For legal reasons. We may disclose information when we believe in good faith that it is necessary to comply with a law, regulation, subpoena, or other legal process, to enforce our agreements, or to protect the rights, property, or safety of CampGuide, our users, or others. Where appropriate and permitted, we will notify the affected Operator of a legal demand for their data.
In a business transfer. If CampGuide is involved in a merger, acquisition, financing, reorganization, or sale of assets, information may be transferred as part of that transaction, subject to this policy.
With your direction or consent. We share information in other ways when you ask us to or agree to it.

13. Service providers and sub-processors

We rely on service providers, sometimes called sub-processors, to deliver the Services. Each handles information only as needed to perform its function for us, under contracts that require it to protect the information and bar it from using it for its own purposes. We use providers in the following categories:

Category of provider	Function	Information involved
Cloud infrastructure and hosting	Application hosting, database, authentication, file storage, backups, edge delivery and caching, custom domains for park websites, security and rate limiting	Account, reservation, document, and related platform data; request and connection data; published website content
Payment processing	Online and in-person payments, saved payment methods, payouts, platform fees. Our payment processor is Stripe, so that you know who handles your card details. Some parks also offer third-party pay-over-time options at checkout	Payment and payout details, transaction records
Text messaging	Guest text messaging and carrier (A2P 10DLC) registration	Guest phone numbers, message content and delivery status
Email delivery	Transactional and marketing email, bounce and complaint handling	Recipient email address, message content, delivery status
Identity verification	CampVERIFY identity checks, performed by Didit, named here because these checks involve government ID and biometric information	Government ID images, selfie, and verification signals, handled by the provider; CampGuide receives the outcome
Electronic signature	Agreements, waivers, leases, and dockage and storage agreements	Signer name and email, document and signing events
Channel management	Distribution to online travel agencies, where a park enables it	Availability and rate data outbound, channel reservation and guest details inbound
Utility metering	Remote meter reading for long-stay billing	Meter readings tied to a site or stay
Artificial intelligence	The AI assists described in Section 11, including optical character recognition on uploaded maps	Map images, site and amenity details, aggregate park metrics, public competitor content
Business and location data	Competitor discovery for MarketRadar	Public business listing and review content
Error and performance monitoring	Diagnosing faults and outages	Technical and diagnostic data, which may include limited identifiers
Marketing and sales CRM	Managing inquiries from our own marketing site	Name, park name, email address, and inquiry details
Website analytics	Marketing site usage measurement. We use Google Analytics, named here so that the opt-out in Section 14 is meaningful	Usage and device data, IP address, cookie identifiers
Internal alerting and documentation	Operational alerts to our team and help center content	Technical alerts, which may reference an account or transaction identifier
App distribution	Distribution of our mobile application	Handled by the app store under its own policy
Weather	Optional forecasts	No personal information

The current list of the specific providers we use is available on request. Write to us at support@campguide.app and we will send it. Operators who need a named sub-processor list for their own compliance records can request one with a data processing addendum. We may change providers within these categories from time to time; where a change is material, we will reflect it in an updated version of this policy.

14. Cookies and tracking

We use cookies and similar technologies to keep you signed in, remember your preferences, keep the Services secure, and understand how the Services are used so we can improve them. Some cookies are necessary for the Services to function, and others, such as analytics cookies, are optional.

We use Google Analytics, a service provided by Google LLC, on our marketing site at software.campguide.app, to understand how visitors find and use it. Google Analytics sets cookies and collects information such as your IP address, the pages you view, how you reached our site, and how you interact with it, and it reports this to us mostly in aggregate. Google handles this information under its own privacy policy at https://policies.google.com/privacy, and you can read how Google uses information from sites that use its services at https://policies.google.com/technologies/partner-sites.

The CampGuide application itself, including the operator console, park booking pages, and the staff mobile app, does not carry third-party advertising or cross-app tracking SDKs. Cookies there are used to keep you signed in and to keep the app working.

You can control cookies through your browser settings, including blocking or deleting them, though some features may not work properly without them. To opt out of Google Analytics specifically, you can install the Google Analytics Opt-out Browser Add-on at https://tools.google.com/dlpage/gaoptout.

We do not use the Services to serve third-party behavioral advertising to guests. Because analytics cookies can be considered a "sale" or "sharing" of personal information under some U.S. state privacy laws, we treat them as covered by the opt-out described in Section 18.

Some browsers offer a "Do Not Track" or Global Privacy Control signal. Where required by law, we treat a recognized opt-out preference signal as a valid request to opt out of any "sale" or "sharing" of personal information, including through analytics cookies.

15. How we protect information

We use technical and organizational measures designed to protect personal information from unauthorized access, use, alteration, and loss. These include:

access controls that limit each user to the park, organization, and role they are authorized for
row-level security in the database so that one park cannot see another park's data
encryption of data in transit, enforced HTTPS, and short-lived signed links for guest-facing pages
isolation of payment, messaging, and other sensitive credentials so they are not readable by ordinary users and are excluded from data exports
signature verification on inbound webhooks from our payment, messaging, e-signature, verification, and channel providers
append-only records for financial and audit data, and logging of privileged actions
a separate sandbox environment and a platform test mode, so demonstrations and testing do not send real messages or charges
managed database backups with point-in-time recovery, and periodic restore drills
error monitoring and alerting on payment and system failures

No method of transmission or storage is completely secure, so we cannot guarantee absolute security. You can help by keeping your password confidential and signing out after each session. If a breach affecting your personal information occurs and the law requires us to tell you, we will notify you as required.

16. How long we keep information

We keep personal information for as long as needed to provide the Services and to meet our legal, tax, accounting, and dispute-resolution obligations. Retention varies by the type of information.

Financial and transaction records, such as invoices, payments, refunds, platform fee records, reservations, and audit logs, are kept for at least seven years to satisfy accounting and legal requirements. Cancellations and refunds preserve the underlying records rather than erasing them.
Guest information is kept by a park for as long as the park maintains it. When a Guest is deleted, identifying details are anonymized while the financial records required for recordkeeping are retained in a form no longer tied to the individual.
Park information. When a park is closed or removed, its guest information is anonymized and the park record is archived rather than permanently destroyed, so that required financial history remains intact.
Consent and opt-out records are kept for as long as needed to prove a consent was given and to keep honoring an opt-out. A suppressed phone number or email address stays on the suppression list so we do not message it again.
Identity verification records. We keep the outcome, timestamp, and requesting park. Document images and selfies are retained by the verification provider under its own schedule, not by us.
Access tokens for guest preference centers and stay pages are short-lived and expire automatically, typically within 30 days.
Sandbox and test data is kept separately from production data and may be reset at any time.
Aggregated or de-identified information that can no longer be linked to a person may be kept indefinitely.

17. Your privacy choices and rights

Depending on where you live and your relationship with us, you may have rights over your personal information. Subject to local law and the limits below, these can include the right to access a copy of your information, to correct it, to delete it, to obtain it in a portable format, to object to or restrict certain uses, and to withdraw consent.

How requests are routed. If you are an Operator, a staff member, a CampGuide ID holder, or a website visitor, contact us directly using the details in Section 24. If you are a Guest asking about the records a park holds, most of that information is controlled by the park you booked with, so please direct your request to that park. We will assist the park and, where appropriate, route your request to it.

Verification. To protect your information, we will take reasonable steps to verify your identity before acting on a request, and we may ask for information to match against our records. You may use an authorized agent where the law allows, and we may require proof of the agent's authorization and verification of your identity.

Tools in the product.

For Operators: CampGuide Host includes built-in tools to export all of a park's data, to export or delete an individual guest's information, and to anonymize a park at offboarding. These help Operators respond to the requests they receive as controllers.
For CampGuide ID holders: your account includes a preference center to turn off communications, a shared-with list where you can stop future sharing with a park, an export of your data, and the option to close your account. These controls apply going forward and do not erase records a park must keep, such as financial history.
For Guests without an account: the preference center link in a park's messages lets you manage communications, and replying STOP stops texts.

Marketing choices. You can opt out of CampGuide marketing emails at any time using the unsubscribe link in those emails. You can opt out of text messages by replying STOP. Even after opting out, you may still receive transactional or service messages such as booking confirmations, receipts, and account or policy notices.

Timing. We aim to respond to rights requests within the time required by applicable law, generally within 30 to 45 days, and will let you know if we need more time. We will not discriminate against you for exercising your rights.

18. U.S. state privacy rights

Several U.S. states, including California, Colorado, Connecticut, Virginia, Texas, and others, give residents specific rights over their personal information. Subject to the exceptions in those laws, residents of these states may have the right to:

confirm whether we process their personal information and access it
request a copy in a portable format
correct inaccurate personal information
delete personal information
opt out of the "sale" or "sharing" of personal information and of targeted advertising
limit the use of sensitive personal information, where applicable

We do not sell personal information for money. We do use analytics cookies on our marketing site, including Google Analytics, and under some state privacy laws that activity may be treated as a "sale" or as "sharing" of personal information for targeted advertising. You can opt out by using the browser and Google Analytics controls described in Section 14, and by enabling a recognized opt-out preference signal in your browser.

Some state laws treat information used to verify identity as sensitive. We use identity verification only to confirm identity for a stay or a work assignment at a park's request, never to infer anything else about you, and never for advertising. See Section 9.

California residents

Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act, California residents have the rights to know, to access, to correct, to delete, and to opt out of sale or sharing, and the right not to be discriminated against for exercising them. The categories of personal information we may collect are described in Section 3, the purposes in Section 4, and the categories of recipients in Sections 12 and 13. We collect this information directly from you, automatically through the Services, and from the sources described in Section 3.6.

Where CampGuide acts as a service provider to an Operator, our handling of that information is governed by our agreement with the Operator, and California guests should direct rights requests to the relevant park.

How to exercise state rights

Operators, CampGuide ID holders, and website visitors can submit a request using the contact details in Section 24. If you are not satisfied with our response, some states allow you to appeal by contacting us again, and to raise an unresolved concern with your state attorney general.

19. Notice for the EU, EEA, UK, and Switzerland

If you are in the European Union, the European Economic Area, the United Kingdom, or Switzerland, the following applies.

For information about Operators, prospective customers, CampGuide ID holders, and visitors to our sites, CampGuide is the controller. For guest information that an Operator manages through the platform, CampGuide is a processor acting on the Operator's instructions, and you should contact the Operator to exercise your rights.

Where we act as controller, we rely on one or more of these legal bases: your consent, the performance of a contract with you, compliance with a legal obligation, and our legitimate interests in operating and improving the Services and communicating with current and prospective customers. Where a check involves biometric processing, such as matching a selfie to a photo ID, it is carried out on the basis of explicit consent through the provider's flow, and you can decline and verify in person instead. Where we rely on consent, you may withdraw it at any time.

You have the rights to be informed, to access, to rectify, to erase, to restrict or object to processing, to data portability, and to not be subject to a decision based solely on automated processing that produces legal or similarly significant effects. You also have the right to lodge a complaint with your local data protection authority.

20. International data transfers

CampGuide is based in the United States, and we and our providers process information in the United States and potentially in other countries, including within the European Economic Area where our channel management and identity verification providers operate. These countries may have data protection laws different from those where you live. When we transfer personal information across borders, we use appropriate safeguards where required, such as standard contractual clauses. By using the Services, you understand that your information may be transferred to and processed in the United States and elsewhere as described in this policy.

21. Children's privacy

The Services are intended for businesses and adults. They are not directed to children, and we do not knowingly collect personal information from children under 13. We do not knowingly sell or share the personal information of anyone under 16. If you believe a child has provided us with personal information, please contact us and we will delete it. A reservation may include the number of children in a party, but that figure is occupancy information rather than personal information about a specific child.

22. Third-party links

The Services may link to or work with websites and services operated by third parties, including a park's own website, a booking channel, and app stores. We are not responsible for the privacy practices of those third parties. We encourage you to read their privacy policies before providing them with personal information.

23. Changes to this policy

We may update this policy from time to time. When we make material changes, we will post the updated policy here with a new "Last updated" date and, where appropriate, provide additional notice such as an email to Operators or a notice within the Services. Your continued use of the Services after an update takes effect means you accept the revised policy.

24. Contact us

If you have questions, requests, or complaints about this policy or our privacy practices, please contact us:

CampGuide Inc Attn: Privacy 8 The Green, STE B Dover, DE 19901 United States Email: support@campguide.app

If you are a Guest and your question concerns information held by a park you booked with, please contact that park directly, as it is responsible for deciding how your information is used.

Table of contents