Privacy

Who runs the site?

ThemeParkie is a project by Tim Broddin. For privacy questions, email [email protected].

Technical data and cookies

The hosting infrastructure processes normal request data, such as an IP address, time, requested URL and browser information, to deliver pages, investigate failures and prevent abuse. ThemeParkie otherwise uses only essential session and security cookies, including XSRF-TOKEN and laravel-session. These are not used for advertising or profiling.

Your light or dark theme preference is stored locally in your browser. You can remove it by clearing this site's data in your browser.

Aggregated statistics

ThemeParkie uses Rybbit through stats.titans.sh to understand aggregated visitor statistics. Rybbit works without cookies and recognises a visit through an anonymous session identifier, so no profiles are built across sites. The site continues to work fully when you block this request. Rybbit is not loaded when your browser sends Global Privacy Control.

Read more in Rybbit's privacy policy.

Location and maps

Only with your permission, the park list uses your location in the browser to calculate distances and sort parks. ThemeParkie does not store those coordinates. Park and attraction maps are supplied through Apple MapKit; your browser then connects directly to Apple and Apple's privacy policy also applies.

Purpose, legal basis and retention

Essential technical processing is used to deliver the requested site securely. Security logs and aggregated statistics are processed on the basis of a legitimate interest in keeping ThemeParkie reliable and improving it. Data is not retained longer than necessary for those purposes and is not sold or used for advertising.

Notifications (web push)

When you enable an alert for an attraction, we store the push endpoint supplied by your browser, its encryption keys, your browser type and your chosen threshold. This is separate from your name or email address: an alert is anonymous unless you were signed in when you enabled it.

An alert expires automatically at the end of the park day and is removed shortly afterwards. If you withdraw notification permission in your browser, we also remove the endpoint on the next delivery attempt. Push endpoints without active alerts are removed after ninety days.

The iPhone and Android app

The app works without an account and contains no advertising or analytics code. When you allow notifications, it registers the push token Expo provides for your device with our server, together with your chosen language and, if you picked one, your home park. The app sends this token with its requests so it can show your alerts. When you set an alert for an attraction, we store that attraction and your threshold with the token.

Notifications are delivered through Expo and then through Apple Push Notification service or Google's Firebase Cloud Messaging. An alert expires at the end of the park day. When you remove the app, the token stops working and we delete it, with its alerts, at the next delivery attempt. Tokens without active alerts are removed after ninety days.

Only with your permission, the app uses your location on your device to sort parks by distance and to show where you are on the park map. Your location is not sent to our server. Maps come from Apple Maps on iPhone and Google Maps on Android; the map loads directly from Apple or Google, and their privacy policies also apply.

Questions about your data

Would you like to know what data we hold about you, have something corrected or removed, or ask another privacy question? Email [email protected]. and we will work out what is needed.