Privacy Policy

Effective date: June 14, 2026

ParkBeast ("ParkBeast," "we," "us," or "our") provides ParkBeast Wait Times, a mobile app for viewing Walt Disney World wait times, attraction information, park hours, favorites, widgets, optional location-based sorting, and optional wait-time alerts.

This Privacy Policy explains what ParkBeast Wait Times handles and how it is used. The app does not require or offer a ParkBeast account and does not ask you to provide a name, email address, phone number, or payment-card information.

Information We Handle

Information You Provide

The app does not include account registration or general-purpose forms for submitting personal information. If you contact ParkBeast by email, we receive the information you include and use it to respond and provide support.

Preferences and App Data Stored on Your Device

The app may store appearance and feature preferences, default park, onboarding status, favorites, pinned attractions, alert settings and snapshots, notification and location toggles, and cached purchase-entitlement information. The app and its widget may use a shared local container to make favorite-attraction and wait-time information available to the widget.

Optional Location Information

If you allow location access, the app uses your device's approximate or precise location, as provided by iOS, to identify whether you appear to be inside a supported park and to sort nearby attractions. The app requests location only while in use and refreshes it periodically while location functionality is active.

Location access is optional. ParkBeast does not currently transmit or store your device's precise location in Firebase. The app may request attraction coordinates from ThemeParks.wiki so distance sorting can be calculated on your device.

Optional Alerts and Push Notifications

If you enable wait-time alerts or push notifications, the app and our Firebase backend may process a randomly generated installation ID; a Firebase Cloud Messaging token; bundle ID, app version, platform, and notification status; alert rules such as attraction, condition, target wait, cooldown, enabled and expiration settings; and alert state such as prior snapshots, last-triggered time, delivery status, retry state, invalid-token status, and timestamps.

The backend stores installation records and may also store individual alertSubscriptions records so it can evaluate only alerts affected by changed attraction data, retry transient delivery failures, disable one-time alerts after delivery, and deactivate alerts associated with an invalid notification token. Notifications are delivered using Firebase Cloud Messaging and Apple's push notification service.

Advertising and Privacy Choices

The free version of the app may display banner ads supplied by Google AdMob. Before requesting ads, the app uses Google's User Messaging Platform to determine whether a privacy message or consent choice is required in your region.

Depending on your region, choices, device settings, and Google's ad-serving mode, Google and participating advertising partners may collect or process information such as IP address, device and app identifiers, advertising data, coarse location inferred from IP address, ad interactions, app interactions, diagnostics, and fraud-prevention signals to select, deliver, measure, limit, and secure ads.

ParkBeast Wait Times does not request Apple's App Tracking Transparency permission and does not include an NSUserTrackingUsageDescription key. Without that permission, the app does not intentionally access the iOS advertising identifier for cross-app tracking. The app includes Apple's SKAdNetwork identifiers, which can support privacy-preserving ad attribution without making the advertising identifier available to ParkBeast.

Ads are configured with a maximum content rating of G. The app does not currently tell Google to treat every user as a child or as under the age of consent. Where Google determines it is required, a Privacy Choices control is available in Settings.

ParkBeast does not sell personal information for money. Advertising-partner processing may be considered targeted advertising, a "sale," or "sharing" under some privacy laws. Where applicable, you can use the in-app Privacy Choices control or contact us about available privacy rights.

Purchases and Subscriptions

The app offers a non-renewing 10-day pass and auto-renewing monthly and annual subscriptions through Apple's App Store. Apple processes your Apple Account, payment information, billing, cancellations, and refund requests. ParkBeast does not receive your full payment-card details or Apple Account password.

The app processes StoreKit product and transaction information needed to load plans, complete and verify purchases, restore purchases, and determine whether ads should be removed. This may include product identifier, transaction identifier, purchase date, expiration date, verification status, and refund or revocation status. The 10-day pass transaction identifier and calculated expiration date may be cached on your device.

Technical and Service Information

The app uses Firebase Core, Cloud Firestore, Cloud Functions, Cloud Messaging, App Check, and Hosting. Firebase and related infrastructure may process device, app, network, IP address, request-integrity, diagnostic, and service-log information needed to secure and operate those services.

ParkBeast Wait Times does not currently integrate Firebase Analytics, Google Analytics, Firebase Crashlytics, or a separate third-party behavioral analytics service.

How We Use Information

We use information to display app and widget content; provide location sorting; sync, evaluate, retry, and deliver alerts; load ads and honor available advertising choices; verify and restore Premium purchases; protect services from abuse; maintain and improve the app; and respond to support or privacy requests.

Third-Party Services

ParkBeast Wait Times uses Apple services, including the App Store, StoreKit, iOS location permissions, SKAdNetwork, and push delivery; Firebase Core, Cloud Firestore, Cloud Functions, Cloud Messaging, App Check, and Hosting; Google AdMob and Google's User Messaging Platform; and ThemeParks.wiki for park and attraction information.

These third parties process information under their own terms and privacy policies. Their practices may vary by service, region, consent choice, and device setting.

When Information Is Disclosed

Information may be disclosed to providers that operate app, advertising, purchase, notification, hosting, security, and backend functionality; at your direction or with consent; to comply with law; to protect rights, safety, and security; or in connection with a business transaction.

Data Retention

Device-stored preferences and cached data generally remain until you delete them, change the setting, or uninstall the app. Apple may retain purchase records under its own policies.

Location used for park detection and attraction sorting is held in app memory and is cleared when location functionality is turned off. ParkBeast does not currently store your precise device location in Firebase.

Firebase installation records used for notifications currently remain until ParkBeast deletes them. Individual alert-subscription records remain until the corresponding rule is removed, expires and is cleaned up, becomes invalid, or ParkBeast deletes it. Records may include installation and notification identifiers, alert rules, alert state, delivery and retry state, App Check status, and related timestamps.

Alerts configured to expire at the end of the day are ignored after expiration and are scheduled for cleanup after the end of the alert's creation day plus a three-hour grace period, with cleanup running at approximately 3:00 AM America/New_York. Related alert state and subscription records are removed or deactivated.

Alerts not configured for daily expiration remain until changed or removed. If Firebase reports an invalid token, the backend removes or nulls it, stores an invalidation timestamp and reason, and deactivates associated alert subscriptions. The installation record is not automatically deleted solely because its token becomes invalid.

Service providers may retain technical, advertising, transaction, security, and log information under their own retention policies.

Your Choices and Rights

You can use the app without a ParkBeast account; decline or disable location and notifications; review advertising privacy choices when available; purchase, restore, manage, or cancel products through Apple; delete favorites, pins, and alerts; uninstall the app; or contact us to request access to or deletion of backend notification data associated with your installation.

Because the app does not use ParkBeast accounts, we may need information from your device or support correspondence to identify the relevant installation. Depending on where you live, you may have additional rights to know, access, correct, delete, or restrict processing, or to opt out of targeted advertising, sale, or sharing.

Children's Privacy

ParkBeast Wait Times is intended for a general audience and is not directed to children under 13. We do not knowingly collect personal information from children under 13. The app's ads use a general-audience setting with a maximum content rating of G; the app is not configured as a child-directed service.

Security

We use reasonable safeguards, including Apple transaction verification, Firebase App Check, access rules, and platform transport encryption. No transmission or storage method is completely secure.

International Processing

The app is primarily intended for users in the United States. Information may be processed in the United States or other locations where Apple, Google, Firebase, or other providers operate.

Changes to This Policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the effective date and may provide additional notice where appropriate.

Contact Us

ParkBeast
contact@parkbeast.com