RideWright Privacy Policy

Effective date: November 4, 2026

RideWright is an iPhone app, backed by our server, that plans the order of your rides at the four Walt Disney World theme parks. This policy explains what it and this website collect, where that goes and how long it is kept. "We" and "us" means Kevin Alvarez, who makes RideWright.

RideWright is not affiliated with, endorsed by, or sponsored by Disney.

The short version

• No account. There is no sign-in. The app never asks for your name, email, phone number, contacts, photos, age or payment details.
• No ads or tracking. The app has no analytics, advertising or crash-reporting code, its own or anyone else's, and doesn't use your advertising identifier. We don't sell your information or share it for advertising.
• A random ID. The app creates a random ID for your phone. Our server saves every plan you build under it.
• Location only if you allow it. It is read only while the app is on screen, and goes to our server only when it is recent and you are in or right next to the park. Your coordinates are not saved, on your phone or on our server.
• Apple runs the map. Apple supplies the map for the area you look at, which can show roughly where you are, even outside the park. When the Map tab shows a plan, your location in the park also goes to Apple for walking routes.
• Saved plans are currently kept with no time limit, and there is no delete button yet. You can ask us to delete them.

Your random ID

The first time you open the app, it creates a random ID. It is not your Apple ID, your advertising identifier or anything from your phone's hardware. It stays until you delete the app. Reinstalling creates a new one, but restoring a backup onto a new iPhone keeps the old one. The app doesn't show the ID, and you can't reset it.

The app sends the ID with every request, and our server stores it with each plan. It doesn't say who you are, but it ties your plans together, so we treat it as personal information.

Location

• Permission. The app asks for "While Using the App" access when you first open the Map tab, and again later only if you chose Allow Once. It never asks for "Always" and never uses location in the background.
• When it's read. Once allowed, whenever the app is on screen, on any tab. It stops when you switch away or lock your phone. Readings less accurate than about 100 meters are ignored, so with Precise Location off, RideWright doesn't use your location for plans or routes.
• On your phone. Your latest location is held only while the app is running and is never saved.
• To our server. When you build or update a plan, or when the app re-plans on its own after a new alert or once the plan is more than 30 minutes old (which can happen every few minutes while it is open), the app includes your location only if it is no more than about 10 minutes old and you are in or right next to the park: within 500 to 750 meters of its center, depending on the park. This circle is a little bigger than the park, so it can include places just outside it, such as a parking lot or a hotel next door. From farther away, nothing is sent.
• On our server. The server uses your location only as the starting point of today's plan during park hours, then throws the coordinates away: they are not saved in our database or written to our logs. But the saved plan's ride order and times depend on where you stood, and its walking time to the first ride shows roughly how far you were from that ride. The plan saved on your phone keeps the same times.

To change this, go to iOS Settings > RideWright > Location. Without location, plans start from the park entrance or the last ride you marked done.

On your phone

The app keeps, in its own private storage:

• For each park: the day, the rides you picked and marked done, your latest plan (without your location) and the ID our server gave it, the alerts you received, the latest wait times and the attraction list, plus when the plan was updated, the wait times fetched and each alert received.
• Your random ID, your chosen park, whether notifications are on, and a server address if you changed it.

Like other app data, this is included in iCloud and computer backups.

On a new park day, the app clears the done list, plan, alerts and wait times for the park you open, and keeps your picks. Parks you don't reopen keep the previous day's data. Picks never expire. Clear on the Rides tab removes your picks, done rides and plan; Clear on the Alerts tab removes alerts. Everything else goes only when you delete the app.

On our server

Every time the app builds or updates a plan (each Done, Undo, Re-plan, refresh, Pick or Unpick on the map, and re-plan after an alert or once the plan is more than 30 minutes old), our server saves a new copy. Each holds your random ID, the park and date, the rides you picked and marked done, the plan we sent back (order, times, estimated waits, walking times, crowd level and notes), and when it was created and last changed. The server also records your random ID, that it is an iPhone, and when you first and most recently built a plan. Together this is a history of which rides you planned and did, and roughly when, linked to your random ID. You can't get a plan without it being saved.

• Why we keep it: to check our wait-time forecasts against the waits actually posted, and to improve the planner. We don't use saved plans to profile you or for advertising.
• How long: right now, with no time limit. Nothing deletes it automatically.

Other requests are not saved in our database:

• Attraction list and live waits send only the park, your random ID and the standard details below.
• Alert checks run each time you open or return to the app and every 5 minutes while it stays open, if you have a plan with rides left, and when you tap Check now or pull down on the Alerts tab. They send the rides you haven't done yet and, if the app saw them in the last hour, the last wait times. No location is sent.

Hosting, logs and IP addresses

Our server and database are hosted by Render in its Virginia region, in the United States. If you use RideWright from another country, your phone sends your information directly to our server in the US, because that is needed to give you the plans you ask for.

Every request carries standard details added by iOS: your IP address, language settings, and the app and iOS versions.

For each request, our server's logs record the time, the kind of request, which part of our service it asked for (this shows the park), the server address used, the network address it came from (which may be your IP address), whether it worked, how long it took, and an error message if it failed. They don't record what the app sent, your random ID or your location.

Render carries all traffic between the app and our server, so it sees your IP address and everything the app sends, including your location when sent. Its own systems may also record your IP address and the standard details, and it uses other companies to carry and host traffic (see Render's list of sub-processors). Render does this for us as our service provider, under its Terms of Service and Data Processing Addendum. Render keeps our server logs for 7 days, and its backups of our database for up to 7 days.

Render also hosts this website, ridewright.app. The website has no cookies, analytics, ads or forms, and loads nothing from other sites. Render receives your IP address and the details your browser sends with each page request, and its systems may record them. Render keeps any such records under its own retention rules.

We sometimes copy the database to our own computer for maintenance, such as before an upgrade, and delete those copies within 14 days.

Apple services

• Map. Apple supplies the map for the area you view, including wherever Show my location takes it.
• Walking routes. When the Map tab shows a plan, the app asks Apple for a walking route to your next stop. It starts from your current location if that is recent and in the park, or else from the start of your plan (which may be where you stood when the plan was updated). A new request goes out each time you move about 25 meters, so Apple receives your location directly from your phone as you walk.
• Walking directions. This button on a ride opens the Apple Maps app with the ride as the destination. Apple Maps then uses its own location permission.
• Notifications. Alerts appear as notifications created on your phone. The app asks permission only when you turn on Notify me. There are no push notifications and we receive no notification token.
• Crash reports. If you turned on Share with App Developers in iOS (Settings > Privacy & Security > Analytics & Improvements), Apple may share crash reports and usage statistics with us. We use these only to find and fix problems.

Apple's privacy policy (apple.com/privacy) covers how Apple handles this.

Where our data comes from

Our server gets wait times, park hours, weather and holidays from Queue-Times.com, themeparks.wiki, the US National Weather Service and Nager.Date, and attraction locations were copied from OpenStreetMap. Our server contacts these services itself, and they receive nothing about you. The "Powered by Queue-Times.com" link opens their website only if you tap it.

Who receives your information

Only Render (our host, and the companies it uses), Apple (as described above), any server you set in Settings and, if you email us, the companies that deliver and store our email. We disclose information to authorities only when the law requires it, and only what we actually hold; we don't keep your coordinates. If RideWright is transferred to a new owner, they must follow this policy for the information we pass on.

For developers: using a different server

Settings lets you change the server address. The same random ID, your picks, done rides and in-park location then go to that server instead, starting as soon as you tap Done, and it supplies the alert text and the "Powered by" link. We don't run those servers, and this policy doesn't cover them. For an address on your local network, iOS asks whether RideWright may use your local network, and a plain "http" address is not encrypted.

Your choices

• Location: iOS Settings > RideWright > Location. Choose Never, or turn off Precise Location.
• Notifications: turn off Notify me, or use iOS Settings.
• On your phone: use the Clear buttons, or delete the app to remove all its data. Earlier backups may still hold a copy. Clear doesn't delete the copies already on our server.
• On our server: deleting the app does not delete your saved plans. Reinstalling gives you a new ID, so new plans aren't linked to old ones. There is no delete option in the app yet. To ask us to delete your data, email privacy@ridewright.app with the parks, dates and rides you planned. After we delete it, copies can remain in Render's backups for up to 7 days, and in any maintenance copy until that copy is deleted.

Your rights

Wherever you live, you can ask what information we hold about you and ask us to delete it. Because the app doesn't show your random ID, we can't tell for sure which saved plans are yours. So we can't send you a copy of saved plans or correct them, since plans matched only by park, date and rides might be someone else's. We can delete plans that match what you tell us closely enough that they are unlikely to be anyone else's.

Depending on where you live (for example California, the EU, the UK or Canada), you may also have the right to object to or limit how we use your information, to get a copy in a reusable format, and to withdraw consent (for location, in iOS Settings). You can also complain to your data protection authority. We will respond as the law that applies to you requires, within the limits above, and we won't treat you differently for using these rights.

Legal bases (EEA, UK and Switzerland)

• Location: your consent, through the iOS permission. You can withdraw it any time in iOS Settings; this doesn't affect use before then.
• Random ID, picks, done rides and saved plans: needed to give you the plans you ask for, and our legitimate interest in checking our forecasts and improving the planner.
• Server logs: our legitimate interest in running and securing the service.
• Website requests: our legitimate interest in serving and securing this website.
• Emails you send us: our legitimate interest in answering you, and any legal duty to handle your request.

Children

RideWright is a general-audience travel app. It is not directed to children under 13 and doesn't ask anyone for a name, email or age. If we learn that we have collected personal information from a child under 13, we will delete it. Parents can contact us at privacy@ridewright.app; telling us the parks, dates and rides helps us find it.

Security

The app talks to our server over an encrypted (HTTPS) connection. Our database accepts connections only from our own services on Render and from computers we specifically allow for maintenance. There are no accounts or passwords to steal. No system is completely secure, and we can't guarantee the security of your information.

Changes to this policy

We will post any new version at ridewright.app/privacy with a new effective date. If a change meaningfully affects how your information is used, such as adding push notifications, we will say so before it takes effect, in the app's App Store update notes or in the app.

Contact

Questions or requests: Kevin Alvarez, privacy@ridewright.app. If you email us, we use your email address and message only to answer you, and keep them only as long as we need to handle your request.