Privacy policy

Data we collect

• Account data. When you create an account we store your email address and authentication details through our auth provider, plus a display name and any profile details you add, including an optional profile photo or banner. User-selected profile images are sanitized and held for automated or manual moderation before publication.
• Content you create. Your collection, park history, trip plans (itineraries, flights, dining), blog comments, game progress, achievements, and other entries you save in the app. ParkBound pass purchase details, visit notes, discount logs, and collected magnets are saved to your ParkBound account and cached on your device for offline use. Race and reminder entries and dietary restrictions or allergy selections remain on your device unless you choose to share an export. Android cloud backup and device transfer are disabled for this app data.
• Subscription status. If you subscribe to ParkBound+, the purchase is processed by the app store you subscribe on. We use RevenueCat to manage subscription status and receive transaction identifiers — never your full payment details.
• Push tokens. If you turn on notifications in the mobile app, we store a device push token to deliver them. Turning notifications off in your device settings stops delivery.
• Usage and interaction data. ParkBound records aggregate blog view counts and, for signed-in users, an account-linked record of which ParkBound app and platform was used, first and last use, and an open count. That limited presence record supports cross-app operations and aggregate adoption reporting, is visible only to authorized staff, and is deleted after 180 days without another use or when the account is deleted. ParkBound Collections sends its presence and other optional account-linked product analytics only when you opt in; withdrawing that choice deletes the optional analytics history. If you accept website analytics, we also collect masked page views, clicks, pointer movement, and scroll depth to build aggregate interaction heatmaps. We disable session recordings and mask page text, inputs, and element attributes. Ad partners may separately process ad impressions and interactions as described below.
• Device and log data. Standard technical data your device sends when you use the service, such as IP address, browser type, and error logs, used for security and reliability.
• Service-region check. Our hosting provider derives a coarse country code from the request IP address. We use that request-time result to decide whether new account registration or web checkout is available. ParkBound does not request precise location for this check or add the country result to your account.
• Giveaway data. When you enter a ParkBound giveaway, we store the email address needed to record the entry, prevent duplicates, conduct the drawing, and contact a potential winner. A standalone web entry does not add you to a marketing list.
• Calendar data.If you choose Add to Calendar, ParkBound uses the calendar permission on that device to create or update the trip events you confirm. Android reads the available calendar list to select a writable calendar. iOS reads existing entries in ParkBound's dedicated calendar for the target date range so a later export can update those entries instead of duplicating them. Neither app reads unrelated event contents or sends calendar identifiers or event contents to ParkBound servers. Your selected calendar provider may separately sync the events under its own settings.

How we use it

• Provide, maintain, and sync your account and collection across devices.
• Operate features you use, such as trip planning and comments.
• Understand aggregate usage so we can improve the product.
• Keep the service secure and prevent abuse.
• Communicate with you about your account and important service changes.
• Administer giveaways, enforce entry limits, draw a winner, and deliver the prize.
• Personalize ParkBound Collections recommendations using collection and activity signals.
• Personalize ParkBound Pulse articles using your follows, wishlist, favorites, upcoming trips, and whether an article connects to your collection.

Third parties

We share data only with service providers that help us run ParkBound, under their respective terms:

• Supabase — hosts our database and handles account authentication and storage.
• Vercel Analytics — provides privacy-friendly, cookieless usage analytics only when a signed-in standard-age account accepts analytics.
• Vercel hosting — serves the website and provides the request-time coarse country code used for service availability and abuse prevention.
• PostHog — builds aggregate website interaction heatmaps from masked click, pointer, and scroll data only after a signed-in standard-age account accepts analytics. Session recording is disabled.
• RevenueCat — manages ParkBound+ subscription status across platforms. Its web checkout uses a Stripe-backed payment form; ParkBound does not receive your full card number.
• AWS Rekognition — moderates user-selected images for safety.
• Google Gemini — processes images when you initiate an AI scan and, after you explicitly consent, processes your request when you choose trip research or Build My Trip. Before ParkBound sends trip data, it names Google Gemini and lists the fields involved. Those fields can include the trip name, dates, destinations, party size, stays, travel plans, budget, wishlist, saved notes, and the prompt you type. Declining keeps the trip usable without AI, and consent can be withdrawn in settings.
• Google Maps Platform and Google Search — provide place and current travel information used in trip drafts. ParkBound shows supporting sources with the draft when they are available. Google processes information under its Privacy Policy.
• Open-Meteo — provides destination geocoding and forecast data used for weather-aware trip and packing suggestions.
• Stay22 — receives the destination, dates, guest and room counts, currency, and filters you submit when you request live accommodation results. ParkBound does not send the trip name, notes, or your account identifier in that search request.
• Apple APNs and StoreKit — deliver notifications and process purchases.
• Google Firebase and Google Play Billing — provide Android push delivery, installations needed for that delivery, and purchase processing. Optional Firebase analytics/crash collection stays off until an eligible user opts in where offered.
• Meta App Events — optional Collections analytics only after an eligible user opts in.
• Google AdSense and Google AdMob — serve ads to eligible free-tier users on editorial blog articles and in our apps (see Advertising below).

We are not affiliated with, endorsed by, or sponsored by The Walt Disney Company or any theme-park operator.

Advertising

• Eligible free accounts may see Google AdSense ads on individual editorial blog articles after accepting website advertising, and Google AdMob ads in the ParkBound apps. Anonymous website visitors and ParkBound+ subscribers do not see ads.
• The ParkBound Collections website does not display Google AdSense ads. Account, catalog, search, planning, policy, archive, and marketing pages do not load the AdSense script.
• Where offered, Google’s consent choices determine whether ad personalization is allowed. On iOS, Apple’s App Tracking Transparency choice separately controls whether an app may permit cross-company tracking and access the advertising identifier.
• When the applicable choices permit it, Google may use cookies or device identifiers to select and measure ads under Google’s partner policy. If a choice does not authorize the requested processing, Google may use an eligible limited or non-personalized mode, or the apps make no ad request. Free accounts may still see ads where an eligible mode is available.
• Google’s mobile ads SDK may process device identifiers, ad interactions, diagnostics, IP-derived coarse location, and advertising data. The apps obtain any required regional consent before requesting ads and request Apple tracking permission before cross-company tracking; unresolved consent disables ad requests.

Age protections

Both ParkBound apps require a one-time 13+ age-band selection before starting accounts, online content, ads, analytics, notifications, or other network features. Users under 13 receive a useful local-only Explorer Mode. In ParkBound Collections, users aged 13–15 in configured guardian-consent regions remain in Explorer Mode unless and until ParkBound offers an independently verified parent or guardian consent channel. ParkBound Story classifies that range as teen access and keeps advertising and tracking disabled. We store an age band, not a birth date or exact age.

Your rights

You can delete your account or create a personal-data export from the app’s settings. Collections exports combine the shared server record with documented device-local preferences and scan drafts; the iOS export also includes pending offline operations. Depending on the law that applies, you may also ask for access, correction, erasure, restriction, portability, or an objection to particular processing. You may withdraw a consent choice at any time without affecting processing that was lawful before withdrawal, and you may complain to your local privacy regulator. To make a request, email support@parkboundapps.com. We may need to verify your identity. Where the GDPR applies, we ordinarily respond within one month, subject to its permitted extensions. You can accept or decline analytics and ads from the consent banner, and change that choice at any time — Manage privacy preferences. The stored choice identifies the applicable notice and vendor configuration and is cleared when the signed-in account changes.

Grounds for processing

Where applicable law requires a legal basis, we use contract or your requested steps for account and product features; consent for optional analytics, advertising purposes, and other processing that is expressly optional; legitimate interests for proportionate security, fraud prevention, service reliability, and content moderation; and legal obligation where the law requires processing. Public-profile publication is optional and can be reversed in profile settings. We do not use recommendations or automated image moderation to make decisions with legal or similarly significant effects about you.

International processing

ParkBound Apps LLC operates from the United States. Public pages may be viewed elsewhere, but new web accounts and checkout are currently offered only in the United States and Canada. Service providers may process data in the United States and other locations stated in their terms. Before regularly offering accounts in a jurisdiction that requires a transfer safeguard or local representative, we will put the required arrangement in place and identify it in this notice. This policy is not itself a data-transfer mechanism.

Retention and deletion

Account records and private content are retained while your account remains active and are removed through the in-app deletion flow. Public catalog contributions that other collectors rely on may be retained only in de-identified form with account attribution removed. Moderation and security records are retained only while needed to investigate abuse, meet legal obligations, or protect the service. Temporary export files are replaced on the next export and cleared during account sign-out or deletion; the operating system may also clear temporary storage. Standalone giveaway email addresses, names, and recorded IP addresses are deleted automatically within 30 days after an administrator records that all winners are confirmed, unless we must retain a limited record for fraud prevention, tax, legal, or recordkeeping obligations. Account-linked app and platform presence rows are deleted after 180 days without another recorded use.

Contact

Questions about privacy? Email support@parkboundapps.com.