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. When you choose to share a plan, that plan is mirrored to your private iCloud database via Apple’s CloudKit so invited family members can collaborate. Magic Pulse never holds a copy of your CloudKit data.
- 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.
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 a read-only live snapshot from our API or ThemeParks Wiki; no account is required. 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.
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.
Contact
Privacy questions can be sent through the support form. Choose topic: Privacy.
Contact support