Legal

Privacy Policy.

Last updated: April 28, 2026

The short version.

Park Alerts is built so we can deliver wait-time pings and showtime reminders without learning much about you. There is no account, no email, no password, no advertising. Specifically:

We never ask for your name, email, or phone number.
We don't track your location — the closest-park feature is on-device only and is optional.
No advertising, no advertising IDs, no third-party trackers, no behavioral profiling.
We don't sell, rent, or trade data. There's almost none to trade.
Anonymous usage analytics run through TelemetryDeck (Austria-based, GDPR-by-design, no personal data).
Wait-time and schedule data come from ThemeParks.wiki, a public theme-park API. Outbound only — we send a park ID, never user data.
We do store an Apple notification token and the list of rides you've set alerts on — that's how the pings actually fire.

Overview

Park Alerts ("the app") is a free iOS app that delivers wait-time pings and showtime reminders for the four Walt Disney World theme parks. The app is published by Macintology, an independent studio. We are not affiliated with The Walt Disney Company or any park operator.

This policy describes what data the app handles, where it goes, and what your choices are. It applies to the iOS app and the small backend that delivers wait-time push notifications. There is no Park Alerts website account.

What we collect

The app and its backend handle a deliberately small amount of data. Here is the complete list:

From your device, when you enable an alert

Notification token

An Apple Push Notification service token (an opaque string assigned by Apple to your install) so the backend can deliver the push when a queue drops.

Alert configuration

For each ride or character you set an alert on: the entity ID, the wait-time threshold you chose, and a timestamp. Stored in a DynamoDB table keyed by entity and notification token.

Platform metadata

A short flag indicating iOS and whether the build is sandbox or production, so the backend routes the push correctly.

On your device only (never sent to our backend)

Show reminders

Lead time and showtime, scheduled directly with iOS's notification system. The backend never sees these.

Last selected park

So the app opens to the park you were last looking at.

Cached park data

Wait-time histories, schedules, and the daily recap, kept locally so the app works fast and works briefly offline.

Anonymous usage analytics (TelemetryDeck)

The app sends anonymized usage signals to TelemetryDeck, an Austria-based, GDPR-by-design analytics service. Signals are limited to product events such as Alert.Created, Alert.Fired, Reminder.Created, and App.Launched, plus a small set of non-identifying parameters (e.g. which park, which alert source — "browse" vs. "suggestion") and platform metadata (iOS version, app version, locale).

TelemetryDeck does not see your name, email, IP address, advertising ID, or any other personal identifier. Signals are tied to a non-reversible per-app, per-device hash that TelemetryDeck computes on-device before sending — we cannot use it to identify you, and TelemetryDeck cannot use it to identify you across apps. Their privacy approach is documented at telemetrydeck.com/privacy.

How the data is used

The data we do collect is used for one purpose: to deliver the alerts and reminders you asked for.

Notification token + alert configuration — to send you a push when the queue you're watching crosses your threshold.
Cached wait times on the device — to render the in-app charts and the daily recap.
Operational logs — to keep the service running, debug crashes, and detect abuse.

We do not profile users, build advertising audiences, or sell anything to anyone.

We use a small, deliberate set of third parties. None of them receive a user identity from us — they receive at most a notification token and an entity ID.

Apple — App Store delivery and Apple Push Notification service.
TelemetryDeck (Austria, EU) — anonymous usage analytics. Receives product event signals and a per-app per-device hash; never receives a name, email, IP address, or advertising ID. GDPR-by-design.
ThemeParks.wiki — public theme-park data API. Our backend fetches wait-time and schedule data from this source.

We do not use advertising, attribution, or session-replay services. The only analytics third party is TelemetryDeck, described above.

Notifications & alerts

Two kinds of notifications are sent:

Wait-time alerts are sent from our backend through Apple Push Notification service. Setting one stores your notification token, the entity ID, and the threshold on our backend so the push can fire when the queue drops. Removing the alert deletes the record immediately.
Show reminders are scheduled locally on your device

You can disable notifications at any time in iOS Settings → Park Alerts → Notifications. You can remove individual alerts in the app with a swipe.

Location data

Park Alerts does not require your location, and your location is never sent to our backend or to any third party.

The app offers an optional "closest park" feature that uses iOS's coarse location to surface the nearest WDW park when you enter the resort. It runs entirely on-device — the comparison happens on your phone, the result is "which of four park buttons should be selected," and that result never leaves the device. iOS will ask for location permission the first time; you can decline (the app works fine without it) or revoke it later in iOS Settings.

Retention & deletion

Active wait-time alerts are deleted from our backend the moment you remove them in the app, and automatically expire (TTL) when the alert fires or after a configurable maximum age — whichever comes first.
Show reminders are stored on your device only and are gone the moment you delete them or uninstall the app.
Operational logs (request metadata) roll off after 30 days.
TelemetryDeck signals are retained per TelemetryDeck's own retention policy. Because signals are not tied to a personal identifier, there is no per-user record to delete; aggregate counts cannot be reversed back to you.
Uninstalling the app invalidates your notification token at Apple. Any remaining server-side records associated with that token become inert and are aged out.