parkseego Privacy Policy

Last updated: October 24, 2026

parkseego shows live theme-park wait times and alerts you when they change. It is made by AGES Foundry, LLC (“we”), a North Carolina company in the United States. This policy explains, in plain language, what we collect, why, and the choices you have. It covers the parkseego iPhone app, its Apple Watch app, the web app at app.parkseego.com, the website parkseego.com (and our older address parkwideapp.com), and the parkseego advisor portal for travel advisors.

The short version: we collect what we need to run your account, your favorites and plans, your alerts and your plan. We don’t sell your data, we don’t show ads, and we don’t track you across other apps or websites. Your location stays on your device.

Where park information comes from: Wait times come from public sources via ThemeParks.wiki and from parkseego users. The part that comes from users is the anonymous queue timings described below.

Using parkseego without an account

You can browse parks, live waits, ride details and the Crowd Calendar without an account. While you browse this way, the app asks our servers only for public park information. It doesn’t send us a name, an email address or saved items, because there are none. Like any app or website, our servers and network providers see your IP address when the app connects. We use it only to deliver the information and to limit abuse. In the web app, guest browsing uses Cloudflare Turnstile (below) to check that you’re a person, not a bot.

You need an account to save favorites, set alerts, plan trips, time a queue or buy parkseego Plus or Pro.

What we collect

Your account and how you sign in

You sign in with Apple, with Google, or with a code we email you, in the iPhone app or the web app. There is no parkseego password.

• Email address. We keep the email address you sign in with and use it to run your account and to contact you about it.
• Sign in with Apple. Apple gives us your email address, and your name the first time if you choose to share it. If you choose Hide My Email, we get a private relay address instead, and Apple forwards our emails to you.
• Google sign-in. Google gives us your email address, and your name and the address of your profile picture if your Google account has them.
• Your name. If Apple or Google gives us your name, our server keeps it with your account, and the app shows it in your account settings so you can see which account you’re signed in to. We don’t use it for anything else. To change or remove it, email us. It is deleted with your account.
• Email code. We email you a six-digit sign-in code. Using it shows that you can read that mailbox.
• Firebase Authentication. We use Firebase Authentication, a Google service, to check these sign-ins. Firebase keeps a record of your sign-in: an ID for you, your email address, the sign-in methods you’ve used, and the name and picture address Apple or Google gave it, if any. Our server stores your Firebase ID with your account. parkseego doesn’t show or use your picture.
• Firebase App Check. When you sign in on iPhone, the app asks Apple (App Attest, or DeviceCheck where App Attest isn’t available) to confirm that it’s a genuine copy of parkseego, and sends Apple’s answer to Firebase App Check, a Google service. Our server checks the result to help stop fake and automated sign-ins. It doesn’t include your name or email address.
• Our own sign-in tokens. After you sign in, our server gives your devices their own tokens, so Firebase isn’t involved again until you next sign in.
• Passwords from test versions. Early test versions of parkseego used a password. If you set one, we keep only a secure hash of it, never the password itself, and we delete it when we turn password sign-in off.

What you save in parkseego

• Favorites and alerts: the rides, parks and shows you favorite, the alerts you set (wait, ride status, park, weather and park-hours alerts) with their targets, and a history of the alerts we’ve sent you.
• Trips and plans: dates, parks, reservations, priorities, meal breaks, notes, and which stops you’ve done.
• Your party: trip-party members are optional. If you add people to a trip, you enter a name for each one, their age group (such as child or adult) and, if you like, their height, so parkseego can check ride height limits. A first name or nickname is enough; please don’t enter full names. We don’t ask for birthdates. This information is entered by you, the account holder, and is deleted with your account.
• Settings: your preferences in the app.

Queue timings

• If you use the queue timer, the app sends us how long your wait took: the ride, when you joined and left the line, the wait the app or the sign showed, and how the timer ended.
• Sharing is on unless you turn it off. To stop sending timings, turn off Share wait timings in the app’s settings. Your timings then stay on your device.
• We store each timing without your account, device or location. To limit abuse and remove duplicates, each timing carries a code that links only your timings from the same day. The secret behind that code is deleted after 48 hours. After that, no one, including us, can tell whose timings they are.
• We combine timings from many guests to estimate how long lines really take. parkseego shows only these combined estimates, never anyone’s own timing.

Purchases

parkseego Plus and Pro can be bought in two places. Either way, we use the purchase record only to turn your plan’s features on and off, to answer your billing questions, and to keep the records the law requires. We never see or store your full card number.

• On the App Store. Apple handles payment. Apple sends us a record of the subscription: the plan, its transaction IDs, and when it renews, expires or is refunded. Cancellations and refunds go through Apple.
• On the web. Stripe handles payment on its own checkout page. We give Stripe your parkseego account ID and your email address, and the plan you chose. You give Stripe your card details and, where tax applies, your billing address directly. Stripe tells us the result, and we keep your Stripe customer ID, your subscription’s ID, plan and price, its status, the dates it started, renews, is canceled or ends, and whether it was refunded or disputed. We record which billing messages from Stripe we’ve processed, but not their contents. Stripe uses the information it collects under its own privacy policy, including to prevent fraud.

How many people use parkseego

• We count how many people use the app each day and week, using a one-way code that can’t be traced back to your account, and keep only the totals, to understand how parkseego is used.
• In the same way, we count how many people use each part of the app (such as park pages, the trip planner or alerts), each park, and each type of device (iPhone, Apple Watch or web) and app version, and how many people who joined in a given week come back.
• We also keep daily totals, such as how many accounts were created, which rides are most favorited, how many alerts were sent, how many subscriptions started or ended, and how many accounts were deleted.
• These totals contain no account ID, email address or anything else that identifies you, and they can’t be linked back to you. They aren’t shared or used for advertising.

Your devices

• A push notification token from Apple, so we can send your alerts to your iPhone. We use push notifications only for service messages, such as the alerts you set. We don’t send promotional or marketing push notifications. If we ever want to, we’ll ask for your separate permission first, and you’ll be able to turn them off at any time.
• If you turn on alerts in your browser in the web app, your browser gives us a push address and keys from its push service (such as Apple’s, Google’s or Mozilla’s), and we store them with your browser’s description (its “user agent”) so we can send your alerts there. We keep up to 10 browsers per account. Turning browser alerts off, signing out or deleting your account removes them.
• If you use the Apple Watch app, a random ID for that Watch installation, so it can read your waits.

What the web app keeps in your browser

The web app stores a few things in your browser’s local storage, on your device: the sign-in token that keeps you signed in, Firebase’s record of your sign-in, and conveniences such as your appearance setting, the park you last chose, plan drafts, messages you’ve dismissed and your queue timer history. The web app doesn’t set cookies, and it has no analytics or advertising code. Signing out removes the sign-in token; clearing your browser’s site data removes everything.

If a travel advisor adds you

Some travel advisors and agencies use our advisor portal to plan trips for their clients.

• What the advisor gives us. An advisor can add your name, your email address, notes about your party (such as ages, heights or dietary needs) and the trip they plan for you. The advisor’s business decides what to enter and is responsible for it. We store and use it only to run the portal for them and, if you accept, to show you their plan. To change or remove it, ask your advisor, or email us.
• The invite. We email you an invite for the advisor. It says who added you and links to this policy. Every email has a link to stop emails from that business.
• You decide. Nothing else from the advisor reaches you until you sign in to parkseego with that email address and accept the advisor in the app. You can decline, and you can remove an advisor later.
• When you accept, we connect your parkseego account to the advisor’s record of you. You then get the parkseego Plus or Pro pass your advisor included (for one year from when you accept), their contact card, and the trips they publish for you. When they publish or change a trip, we may send you a notification and an email summary. We also note which advisor brought you to parkseego, for our own records; it isn’t shared with anyone else.
• What the advisor sees: the name, email and trip they entered, the pass they gave you, and whether you’ve accepted. They never see your other parkseego data: your favorites, alerts, your own trips, queue timings, settings or purchases.
• If you copy the advisor’s trip into your own trips, the copy is yours, like any trip you save.
• Deleting your parkseego account removes the connection. The advisor’s own record of you stays with them; ask them to delete it, or email us and we’ll pass your request on.
• People who use the advisor portal: we keep their email address, name, business and role, the contact card they publish (which their clients see), and a record of the changes they make. Their business pays for passes by card through Stripe; we never see card numbers. The advisor’s business agrees to our Advisor Terms and Data Processing Agreement.

What we don’t collect

• Your location stays on your device. If you allow location on iPhone (“While Using the App”) or in your browser, parkseego uses it to show where you are on the park map and how far away rides are. The app and the web app don’t send your location to us. We’ll update this policy before that ever changes. When you sign in with Google, Google may use your IP address to estimate your general location (such as your city), to help prevent fraud.
• We don’t use advertising, advertising IDs or tracking. There are no analytics, crash-reporting or advertising tools in the iPhone app or the web app. The only third-party code in the iPhone app is for signing in (Firebase Authentication, Firebase App Check and Google Sign-In). The web app also loads Cloudflare Turnstile for guest browsing, and Apple’s MapKit JS on its map page.
• We don’t access your contacts, photos, camera, microphone or Health data.
• Plan reminders are scheduled on your device and don’t go through our servers.

How we use your information

We use it only to provide parkseego:

• to run your account and keep it secure, including rate limits that stop abuse;
• to show your favorites, plans and alerts on your devices;
• to send the alerts you asked for;
• to estimate real waits from queue timings;
• to count how many people use parkseego, as totals only;
• to check and manage your Plus or Pro plan, and to answer billing and refund requests;
• to run the advisor portal for travel advisors and their clients, as described above;
• to fix problems and keep the service running.

We don’t sell or rent your personal information, and we don’t share it for advertising.

Who else handles your data

We use a few service providers to run parkseego. They process data only to provide their service to us.

We may also disclose information if the law requires it, or to protect the safety of people or the service. If parkseego is sold or merged, your information would go to the new owner under this policy.

How long we keep it

• Your account and what you save are kept until you delete your account.
• Sign-in codes work for 10 minutes and are deleted within a day.
• Security records such as rate limits are kept as one-way hashes and deleted within a day or two.
• Sessions: a sign-in ends after 30 days without use, and when you sign out. The Apple Watch’s access lasts up to 14 days, and your iPhone renews it.
• Delivery records for weather and park-hours alerts are deleted after 30 days.
• Queue timings are kept for up to 13 months. They aren’t linked to your account, so they stay when you delete it.
• Web purchase records are deleted from our database with your account. Stripe keeps its own records of payments, and we keep the payment records that tax and accounting law require.
• Advisor records are kept until the advisor deletes them or asks us to. Addresses that used “Stop emails” are kept so we never email them for that business again.
• Our server logs leave out your email address and sign-in tokens. We keep logs only as long as we need them to run and secure the service.

Deleting your account

You can delete your account in the iPhone app (More › Account › Delete account) or in the web app (Account › Delete account).

When you delete your account we immediately delete your profile, favorites, plans and alerts from our live database. Copies may remain in our encrypted backups for up to 30 days, until those backups are deleted. Anonymous queue timings, which never contain your account or location, remain in aggregate statistics.

• This deletes your account and everything saved to it: favorites, alerts, trips, party members, settings, device tokens, browser push addresses and subscription records.
• It also deletes your Firebase sign-in record. If you use Sign in with Apple, the app asks you to confirm with Apple once more, so that we can tell Apple to revoke parkseego’s access to your Apple Account.
• It cancels a web subscription at Stripe right away. It doesn’t cancel an App Store subscription; cancel that in Settings › Apple Account › Subscriptions.
• You can also ask us to delete your account by emailing support@parkseego.com from the address you sign in with.

You can stop parkseego’s access to your Apple Account at any time in Settings › Apple Account › Sign in with Apple. That doesn’t delete your parkseego account.

Your choices and rights

• Notifications and location: turn them on or off at any time in iPhone Settings › parkseego, or in your browser’s site settings.
• Access, correction and deletion: you can see and change most of your data in the app. Email us for a copy of your data, a correction, or deletion, and we’ll respond within 30 days.
• Depending on where you live, you may have further rights over your personal information. You can ask about or use any of them by emailing us, and we won’t treat you differently for doing so. We don’t sell your personal information, and we don’t share it for advertising.

Children

parkseego accounts are for people 13 and over, and parkseego isn’t directed to children under 13. We don’t knowingly collect personal information from children under 13. Families can use parkseego on a parent’s account.

A parent can add a child to a trip’s party with a first name or nickname, an age group and, optionally, a height, so parkseego can check ride limits. The parent enters this information, it belongs to the parent’s account, and it is deleted with that account. If you think a child under 13 has created an account, email us and we’ll delete it.

Security

We use encryption in transit (HTTPS), keep your sign-in on your iPhone in Apple’s Keychain, store our sign-in tokens only as secure hashes on our servers, and limit who can access production systems. No system is perfectly secure, so please keep the Apple, Google or email account you sign in with secure.

Our website

parkseego.com (and parkwideapp.com) collects only what its beta and launch-updates list needs, and simple records of how its pages are used. It has no ads, no third-party analytics and sets no cookies.

• Page views: when you open one of the site’s main pages (the home page, /passholder, /first-trip, /planning or /frequent-visitors), the page records that it was viewed: its path, the time, a random visitor ID, the version of the site, and where you came from (below).
• Passholder page: on /passholder, the page also records, with the same details, when you tap a button to join the beta and when you tap the link to TestFlight.
• Where you came from: the page notes the campaign tags in the link you followed (utm_source, utm_medium, utm_campaign, utm_content and utm_term, and a partner or referral tag), the domain of the site that linked to you, the page you arrived on, and the time. It keeps these for your first visit and for your latest visit from a tagged or outside link, with a random visitor ID, in your browser’s local storage, and sends them with page views and with your signup, so we can tell which links bring people to parkseego. The visitor ID isn’t linked to you unless you join the list. Clearing your browser’s site data removes them.
• When you join: your email address, what you signed up for (the iPhone beta, launch updates or the passholder beta), when you signed up, and where you came from. If you sign up again with the same email for something else, we add that choice to your signup. We use your email only to tell you about parkseego, for example when you can try it or when it’s on the App Store. Joining doesn’t send you an email.
• Optional survey: after you join, you can tell us when your next park visit is, how often you visit theme parks, and which parks are your favorites. Your answers are stored with your signup. Questions you skip aren’t stored, and skipping the survey doesn’t affect your signup.
• Bot protection: the signup form uses Cloudflare Turnstile to check that a person, not a bot, is signing up. Cloudflare processes details about your browser and connection to do this. We send your IP address to Cloudflare for that check and use it to limit repeated signups and page-view records. We don’t store it with your signup or page views; a one-way hash of it is kept for up to a day to enforce the limits.
• How long we keep it: we keep your email, your signup and your survey answers until you ask us to remove them, or until we close the list. To remove them, email support@parkseego.com from the address you signed up with. Page views and the passholder page’s records don’t contain your email; once your signup is removed, they can’t be linked to you.
• Shared ride pages (links that start with parkseego.com/r/ or parkwideapp.com/r/) show one ride’s live wait and record no page view.

Changes to this policy

When we change this policy, we’ll update the date at the top. For significant changes, we’ll tell you in the app or by email before they take effect.

Contact

AGES Foundry, LLC
Raleigh, North Carolina, United States

Email: support@parkseego.com