Privacy Policy & Terms of Use
What we collect, what we never do with it, and the terms you're agreeing to by using park.day.
park.day is a personal project, not a data business. We collect only what we need to run the service, we do not sell your information to anyone, and we do not use it for advertising.
What We Collect
When you create an account we collect the following information. All of it is stored in a private database and is used only to operate the service.
- Name and email address — required to identify your account and send you service notifications.
- Password — stored as a one-way hash (bcrypt). We never store or transmit your password in plain text. Passwords are checked against the Have I Been Pwned database at registration and change time using k‑anonymity — only the first 5 characters of a SHA‑1 hash are transmitted, never your actual password.
- Profile avatar — optional. You may upload a photo or generate a bot avatar. Uploaded images are stored on our servers.
- OAuth provider IDs — if you sign in with Google, Apple, or Microsoft we store the opaque account identifier returned by that provider. We do not store provider access tokens beyond what is needed to complete sign-in. If you sign in with a Microsoft work or school account, we also store your organization’s Microsoft tenant identifier — a non-secret ID that tells us which organization you belong to — so that we can offer verified employees of the theme parks we cover access to features intended for them. We do not receive your Microsoft password.
- Session data — a secure session token tied to your account, along with your IP address and browser User-Agent string at session creation. This is how you stay logged in and how the Sessions page shows you what devices are active.
- Two-factor authentication data — if you enable 2FA, we store your TOTP secret and hashed backup codes. If you register passkeys (Face ID, Touch ID, or hardware keys), we store the WebAuthn public key and associated metadata.
You do not need an account to browse wait times, dining availability, ticket prices, or resort rates. Account creation is only required for the alerts and notifications features.
Location
The live map and walking-directions features can use your device’s location, but only if you grant permission when your browser asks. Here is exactly what happens with it:
- Your position and compass heading are used in your browser to show where you are on the map.
- When you request walking directions, your current coordinates are sent to our own routing server (which we host — not a third party) to compute the route. They are used only for that request and are not stored or linked to your account.
- A flag is saved in your browser’s local storage so the map remembers that you turned location on. Your coordinates themselves are never written to storage.
We do not keep a history of your location, and we never share location data with anyone. You can revoke location permission at any time in your browser or device settings.
How We Use Your Data
- To authenticate you and keep your account secure.
- To deliver alerts and notifications for attractions, dining slots, or resort availability you have set up.
- To send you email — alert notifications you have set up (delivered through Resend, our email provider) and transactional messages such as password resets and security notices.
- To detect and prevent abuse, including automated sign-up bots (via Cloudflare Turnstile CAPTCHA verification on the sign-in, sign-up, and password-reset forms).
- To understand how the site is used in aggregate and to find and fix errors, using the analytics described in the next section.
We do not use your data for advertising or any commercial purpose, and we do not sell, rent, or share your personal information with third parties, except for the service providers described below.
Analytics & Error Reporting
We use PostHog (hosted in the United States) for basic product analytics and error tracking, so we can tell which features are used and fix things when they break. In the interest of full transparency, here is what it captures:
- Page views — which pages on park.day you visit and when you leave them.
- Errors — crash and error reports, which may include the error message and the page you were on, so we can reproduce and fix bugs.
- Feature events — a small number of specific events, such as a map falling back to a simpler renderer or a location/notification permission being denied. These never include your coordinates.
- Who you are, if signed in — analytics events from signed-in users are linked to your account ID, name, and email so we can investigate problems you report. If you are not signed in, events are not tied to a person profile.
What we deliberately do not do: no session recording (we cannot replay your screen), no surveys, no advertising or cross-site tracking, and no sharing or selling of analytics data to anyone. Analytics exist so the site works well, not to monetize you.
Third-Party Services
The following third-party services process some of your data as part of operating the site. Each is governed by its own privacy policy.
- Google OAuth — if you choose to sign in with Google, your browser communicates with Google’s servers to authenticate you. Google may process your email address and account identifiers per their own privacy policy.
- Apple ID — same as above for Sign in with Apple.
- Microsoft — if you choose to sign in with Microsoft, your browser communicates with Microsoft’s servers to authenticate you. Microsoft may process your email address, account identifiers, and organization per their own privacy policy.
- Cloudflare Turnstile — the CAPTCHA widget on the sign-in, sign-up, and password-reset forms sends a challenge token to Cloudflare to verify that you are human. No personal account data is shared; Cloudflare may collect browser signals per their privacy policy.
- Have I Been Pwned — when you set a password, the first 5 characters of a hash of your password are sent to the HIBP k‑anonymity API to check whether it appears in a known breach. Your full password and password hash are never sent.
- PostHog — receives the analytics and error events described in the “Analytics & Error Reporting” section above, including your account ID, name, and email if you are signed in.
- Resend — delivers our email. Resend processes your email address and the contents of the messages we send you (for example, which resort or restaurant an alert is about).
- Cloudflare R2 — stores uploaded profile avatars. Avatars are served from a public URL, so do not upload an image you would not want to be publicly reachable.
Cookies & Local Storage
Here is everything park.day stores in your browser:
- Session cookie — keeps you signed in. Essential.
- PostHog identifier — a first-party cookie and local-storage entry holding a random device ID so the analytics described above can count you once rather than as a new visitor on every page. It is never used for advertising and is not readable by other websites.
- Local UI preferences — local-storage entries for things like your dining party size, your preferred wait-times view, whether you enabled the location feature, and whether you dismissed the notification prompt. These never leave your browser.
We do not use advertising cookies, cross-site tracking cookies, or any third-party tracking. Nothing stored in your browser follows you to other sites.
Push Notifications
If you grant permission for browser push notifications, your browser’s push service (operated by your browser vendor — e.g. Google FCM for Chrome or Apple’s APNs gateway for Safari) is used to deliver notifications to your device. We store a push subscription endpoint URL tied to your account. You can revoke push permission at any time in your browser settings.
Data Retention & Deletion
Your account data is retained for as long as your account exists. Session records expire automatically after their expiry date. You can revoke individual sessions at any time from the Security settings.
While your account exists we also keep a log of the alert notifications we have sent you (so you can see what fired and we can debug delivery problems). This log is deleted along with your account.
You can permanently delete your account from the Profile page. Deletion removes your name, email, avatar (including the stored image file), credentials, sessions, linked providers, 2FA data, all alert preferences and saved alert searches, push notification subscriptions, and notification history, and we request deletion of your analytics profile and events from PostHog. This action is irreversible.
You can also email us at any time to request a copy of the data we hold about you, or to have it corrected or deleted.
Children’s Privacy
park.day is not directed at children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has created an account, please contact us and we will delete it promptly.
Changes to This Policy
If we materially change how we collect or use your data, we will update the date above and, for significant changes, notify signed-in users by email. Continued use of the service after a change is posted constitutes acceptance of the updated policy.
Terms of Use
By using park.day you agree to these terms. They are short and written in plain English. Also see our Disclaimers & Legal Notice for data accuracy, trademark, and liability disclaimers.
Permitted Use
park.day is provided for personal, non-commercial informational use only. You may use it to plan theme park visits, track wait times, monitor dining availability, or set up personal alerts. That’s exactly what it is for.
Prohibited Uses
You may not:
- Scrape, crawl, or systematically download data from park.day by automated means, including but not limited to bots, scripts, browser automation tools, or data harvesting services.
- Use park.day or the data it provides to build a competing product or service, to resell data, or for any commercial purpose without our express written consent.
- Attempt to reverse-engineer, bypass, or interfere with the site’s APIs, authentication, rate limits, or infrastructure.
- Create multiple accounts to circumvent feature limits or for abuse purposes.
- Impersonate any person or entity, or submit false information when creating an account.
Your Account
You are responsible for keeping your login credentials confidential and for all activity that occurs under your account. If you believe your account has been compromised, change your password immediately and revoke active sessions from the Security settings.
Accounts are for personal use. You may not share your account with others or transfer it to another person.
Service Availability & Modifications
park.day is a personal project provided as-is and at no charge. We make no guarantees of uptime, feature availability, or continuity. We may modify, suspend, or discontinue any part of the service — including alert features, specific data feeds, or account functionality — at any time without notice.
We may also terminate or suspend your account at our discretion if we believe you have violated these terms.
Governing Law
These terms are governed by the laws of the United States. Any disputes arising from your use of park.day shall be resolved through good-faith discussion first. If you have a concern, please reach out to us before taking any formal action.
Contact
Questions, privacy requests, or concerns? Email us at [email protected]. We’re a small team and we read everything.
This page covers the privacy policy and terms of use for park.day. It does not constitute legal advice. For data accuracy and trademark disclaimers, see our Disclaimers & Legal Notice.

