MouseMinds

Privacy Policy

Last updated: October 26, 2026

This policy applies to the iOS and Android versions of MouseMinds. We built the app to be useful without asking for more data than we need, and we do not sell personal information or use advertising SDKs in the current release.

Information We Collect

MouseMinds does not require you to create a general app account for most features.

  • Local app data: favorites, filters, saved reminders, trip plans, and similar preferences are stored on your device. On iPhone, saved Plus work, including What-If Planner scenarios, Best Days Finder results, Split & Meet Up plans and member names, Pace Your Day preferences, and Smart Day Score history, is also stored locally unless you choose to share it.
  • Location on iOS: if you choose the Closest sorting option, the app may request location access to rank nearby parks on your device. We do not store your location on our servers.
  • Disney sign-in for dining tracking: if you use the Dining Reservation Tracker, Disney sign-in happens through Disney's own login flow. We do not see or store your Disney password. Session cookies may be stored on your device so the feature can keep you signed in.
  • Optional remote alerts: if you enable cloud-backed alerts, we may store an app-specific technical installation ID, push notification token, notification authorization status, app version/build, and your alert settings in Firebase so alerts can be delivered. Existing cloud alerts use a technical Firebase Authentication identity without asking you to create a named account; this is separate from the Ride Combo Alerts verification described below.
  • Android reminders: the current Android app uses local notifications for reminders and does not upload a push token for those local alerts.

How We Use Information

We use the information above only to provide the app's features, including wait times, crowd forecasts, show schedules, menus, weather, news, podcast playback, dining tools, park sorting, and alerts you choose to enable.

Ride Combo Alerts and MouseMinds Plus Verification

When you enable Ride Combo Alerts on iPhone, our server stores a randomly generated, app-specific installation identifier, the attractions and conditions you choose to monitor, notification delivery records, and a record verifying that your installation is eligible for MouseMinds Plus or permanent Founder Access.

This information is used to verify access to premium features, monitor your selected ride conditions, and deliver requested notifications. It also helps protect the service and avoid sending the same opportunity repeatedly.

The installation identifier is derived from the identifier of a key generated through Apple’s App Attest service. It is not a hardware serial number or advertising identifier. It is a pseudonymous identifier: it lets the server recognize the same app installation, so we do not describe these records as fully anonymous.

The alert service does not ask for or attach your name or email address, and you do not need to create a general MouseMinds account. We do not sell this information or use it for advertising or tracking across other companies’ apps or websites. If you contact us for help, we receive the contact details and information you choose to send.

  • Access verification records: Apple’s signed app-acquisition and subscription information, together with App Attest, lets the server check whether an installation has current Plus access or permanent Founder Access. The server keeps verification results, necessary Apple acquisition or subscription identifiers, and technical security records. The Combo application database does not retain the raw signed Apple transaction payloads.
  • Combo alert definitions: the server receives ride and park identifiers, the selected order, start and end times, starting and meeting-point attraction identifiers, optional wait limits, and a time buffer. It checks these conditions against park data. Personal names, group details, labels for your commitments, and your location coordinates are not part of this upload.
  • Notification delivery records: the server keeps the push token needed to reach your device and technical records of alert opportunities and delivery attempts. Push tokens and original subscription transaction identifiers are encrypted in the application records. A delivery attempt is not a guarantee that a notification reaches your phone.

Most other Plus and Founder functionality is recognized locally on your iPhone using Apple’s verified purchase information. Apple handles subscription payments; MouseMinds does not receive your payment card details or Apple Account password. Founder Access is based on Apple’s verified original acquisition date before the 5.0 launch cutoff and does not require a subscription. A verified acquisition date may be cached securely on the device to help recover access, and that secure cache can survive an ordinary reinstall.

Third-Party Services

MouseMinds uses third-party services and content sources to power the app:

  • Queue-Times.com for live wait times and crowd forecasts
  • AllEars.net for Walt Disney World restaurant menu information
  • Apple WeatherKit on iOS and Open-Meteo on Android for weather data
  • ThemeParks Wiki for live show schedules and published park hours
  • Google News RSS for theme park news
  • Libsyn for the podcast feed
  • Disney services for dining reservation features
  • Firebase services, including Firestore, Cloud Functions, Hosting and technical authentication for existing cloud alerts, plus platform push services such as Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM)
  • Apple’s App Store, StoreKit, App Store Server API and App Attest for purchases, Plus or Founder verification, and app security

These services have their own privacy policies. When you tap an external link, you leave MouseMinds and open that provider directly.

Data Sharing and Storage

We do not sell your data or use it for advertising.

We share only the limited technical data needed to provide the features you request, such as remote alert delivery or content loading from the services above. Most app preferences and saved items stay on your device. Deleting the app removes its ordinary local app data from that device, but it does not send a request to delete server records. Secure Keychain items, such as a verified acquisition cache or device verification key identifier, may survive an ordinary reinstall. Device backups, if enabled, follow your platform’s backup settings.

Service providers may process network and request details, such as IP addresses and request times, when delivering or securing content and notifications. External services may also use their own cookies or identifiers under their own policies. We do not use these records to build an advertising profile or track you across other companies’ apps and websites.

Storage, Retention and Deletion Choices

Ride Combo Alerts stop being evaluated when their time window or park day ends. The server also stops evaluation and delivery when it cannot verify eligible Plus or Founder access. These are access and delivery rules, not confirmation that stored records have been deleted.

  • Installation, access and push-routing records: the software initially assigns expiry times of about 48 hours. Creating alerts for future dates or verifying access again can extend those times. An alert can extend the related records until at least 24 hours after its deadline; they are not limited to 48 hours overall.
  • Combo definitions and delivery records: the software assigns expiry times 24 hours after the relevant alert deadline. Records used to avoid duplicate notifications can remain associated with the latest relevant window.
  • Pausing and deleting: a server-confirmed pause stops evaluation but keeps the saved definition. A server-confirmed delete removes that alert’s definition and evaluation record; it does not erase all installation, access, routing or delivery records. A change saved only on your phone is not confirmation of a server deletion. If a server request cannot be completed, remaining server evaluation ends under the alert’s expiry and eligibility rules.
  • Uninstalling: removing MouseMinds does not automatically delete server-side records or cancel an App Store subscription. Manage subscriptions through Apple’s App Store settings.

An expiry timestamp is not a guaranteed deletion time. Automatic expiry-based deletion is not currently configured in the production Firestore database checked for this update. Records can therefore remain after their expiry timestamps until removed through an applicable deletion operation or administrative cleanup. Service-provider logs and any backups may have separate retention processes; we do not promise an immediate or fixed deletion time for those copies.

To ask about or request deletion of stored information, email mousemindspodcast@gmail.com. Tell us which feature is involved and provide any alert identifiers you can access so we can try to locate and verify the relevant records. Because these records are pseudonymous, your name or email address alone may not identify them. Never send your Apple or Disney password or payment card information.

Children's Privacy

MouseMinds does not knowingly collect personal information from children under 13.

Changes to This Policy

We may update this policy from time to time. If we do, we will post the updated version on this page with a new date.

Contact Us

If you have questions about this privacy policy, email us at mousemindspodcast@gmail.com.

You can also visit our public support page at mouseminds-alerts.web.app/support/.