Privacy Policy

Overview

Magic Pulse (“we”, “our”) provides live theme park planning information. This policy describes what data is involved in the iOS app, the Apple Watch app, the optional Magic Pulse API, and this website.

Data used in the iOS app

• Location (optional): Used to suggest nearby parks and to deliver location-based alerts you enable. We do not sell your location.
• Notifications: Used only for alerts you opt into, including drop alerts, Lightning Lane price alerts, day-plan reminders, park-opening alerts, and severe-weather notifications. You can turn them off individually or globally in Settings.
• On-device preferences: Watchlist, thresholds, display settings, and similar preferences are stored on your device.
• iCloud settings sync: If you’re signed in to iCloud, certain preferences sync across your own iPhones and iPads via Apple’s Key-Value Store. The data is stored in your private iCloud account; we never see it. You can disable iCloud Drive for Magic Pulse to opt out.
• Day plans: Plans are stored locally in Core Data and may sync through Apple’s CloudKit when you are signed in to iCloud and it is available for the app. If you choose to share a plan, invited participants can access the shared content according to Apple’s sharing controls. Routine plan sync does not send a separate copy of your CloudKit database to Magic Pulse servers. Without iCloud, plans stay on the device.
• On-device history (forecasts): Wait-time history used for trends and on-device forecasts stays on your device unless you use the optional API path below.
• Optional Magic Pulse API: If you or the default configuration use our servers, the app may send requests authenticated with Apple’s App Attest and an app API key. We process park snapshots and aggregated wait history to power forecasts, Lightning Lane price history, and crowd insights. For requested alerts and background data freshness, the API may store an APNs device token, a random installation identifier, the selected park identifier, alert preferences, time zone, locale, and app/build version. Silent background refreshes do not display an alert. Live Activity update tokens are stored separately and only while an activity is expected to remain active. Disabling both Background App Refresh and notifications removes the ordinary APNs subscription. Invalid APNs tokens are removed when Apple rejects them. We do not use this information to build an advertising profile.
• Advertising (free tier): The free tier may show banner ads through Google AdMob. Depending on the user’s region and choices, Google’s SDK may process an IP address to estimate general location, diagnostics and performance data, app- or developer-bounded device identifiers, advertising data, and interactions with the app or ads. Magic Pulse requests the applicable consent status before requesting an ad, serves only non-personalized ads, disables Google’s publisher first-party identifier, and does not request permission for cross-app tracking. In-app privacy options are available when Google requires them. See Google’s Privacy Policy. Magic Pulse Pro removes the in-app banner.
• Diagnostics: Lightweight app events may be logged locally on your device for product improvement and are not uploaded by default.
• Optional configuration reporting: In app versions that offer Share configuration status, that preference is off by default. When you enable it and the service requests reporting for an applicable configuration, the app sends an authenticated receipt with a random installation identifier, configuration revision, and app version. The API stores a keyed hash of the installation identity with revision and timing information to summarize configuration adoption. Inactive receipt records expire after 30 days; this is separate from anonymous website counters.
• Optional park announcements: In app versions that offer Park announcements, this separate notification preference is off by default. Announcements require that preference, the app’s main notification switch, and system permission; selected notification parks and quiet hours apply. The API stores the opt-in with the notification subscription. An offline preference change reaches the server only after connectivity returns; iOS notification settings control whether the device can display notifications.

Apple Watch app

The Apple Watch companion is read-only. It receives a snapshot of your selected park’s name, hours, crowd level, and top watchlist ride wait from the iPhone via Apple’s WatchConnectivity framework. No data leaves the watch independently: there’s no network connection, no separate account, and no analytics.

Data we do not sell

We do not sell your personal information. Magic Pulse configures its advertising SDK for non-personalized ads and does not enable cross-app tracking.

Third-party services

• Wait times and park operating data: ThemeParks Wiki and related public park data.
• Weather: Apple Weather via WeatherKit in the app.
• Settings sync and shared day plans: Apple iCloud Key-Value Store and CloudKit.
• Purchases: Apple App Store subscriptions and one-time purchases.
• Ads: Google AdMob on the free tier.
• Website form delivery: Formspree after Magic Pulse validates and relays an accepted submission.

This website

The marketing site may load read-only wait snapshots from our API or ThemeParks Wiki, and published service notices from our API. Those requests include the selected park and, for notices, the publicly listed app version and English locale; they do not send app authentication or configuration-reporting receipts. The chosen preview park is remembered in browser local storage, not a cookie. Hosting and data providers receive normal connection information, such as your IP address, when serving a request. Fonts are self-hosted, and the site does not use advertising cookies or cross-site trackers.

Anonymous measurement: The site can count App Store button clicks, park-preview changes, screenshot-gallery navigation, feature-guide opens, status checks, support-form starts, completed support requests by topic, and completed Android waitlist signups. It stores only an allowlisted event name, a short context such as button location or selected park, the calendar day, and a total. The measurement table has no visitor ID, device ID, cookie, email, form message, or IP address. Browser Do Not Track and Global Privacy Control signals disable client-side events. Aggregate counters are automatically removed after about 18 months.

Forms: The support form and Android waitlist first pass through the Magic Pulse website service for field validation, a signed form challenge, and rate limiting. The relay keeps a network-based rate-limit bucket briefly in memory and does not add it to the submission. Technical support details are optional and include only what you type; the page does not collect device logs or fingerprint your device. Accepted fields are sent to Formspree for delivery, and a random support reference is added. Magic Pulse does not write names, emails, messages, or technical details to its website analytics database. Android waitlist emails are used only for meaningful Android testing or availability updates.

Children

Magic Pulse is not directed at children under 13. We do not knowingly collect personal information from children.

Your choices

You can limit location and notifications in iOS Settings. When Google requires an advertising privacy-options form for your region or prior choice, it appears in Magic Pulse under Settings > Privacy & Data. You can also use Apple’s privacy controls in iOS Settings. California residents may have additional rights under the CPRA; contact us via the support form and we will respond as required.

Where offered, turn off Share configuration status in the app’s refresh and data preferences to stop new configuration receipts, or Park announcements in notification preferences to stop requested announcements. These options do not sign you up for website measurement or change your saved plans. Clear this website’s browser storage to remove its remembered preview park.

International users

If you use the app or site from outside the United States, data may be processed in the U.S. or where our service providers operate.

Retention

Server-side wait samples and snapshots are kept only as long as needed to operate the service and improve reliability, including automatic pruning of old history. Alert subscriptions remain while notifications are enabled and the APNs token remains valid. A background-only APNs subscription expires after 45 days without contact, and Live Activity update tokens expire after 12 hours. Disabling both Background App Refresh and notifications removes the ordinary APNs subscription. Anonymous website event totals are kept for up to 18 months. Support emails or form submissions are retained only as needed to respond and meet legal obligations. Android waitlist addresses are retained until the list’s purpose ends or you ask us to remove your address.

Policy updates

We may update this policy; the date at the top shows the current version. Material changes will be reflected here and, where appropriate, in the app.