THE PARK ACCESS FIELD GUIDE
Privacy and your feedback
What this website stores, why it does so, and how to ask for removal.
Updated 11 November 2026. Theme Park Access is an independent project operated by its site owner. Contact the owner using the privacy enquiry form.
Browsing and planning
The park finder, access path comparison, care filters and trip brief run in your browser. Your planning choices are not submitted to us. Saved parks use local storage on your device; remove a park from your shortlist or clear this site’s browser storage to remove them. A page-helpfulness vote uses session storage to avoid asking again during the same browser session.
Simple usage counts
We use Cloudflare Web Analytics, which counts page views without cookies and without building a profile of you, and we count helpful / not-helpful votes by page and day. We do not use advertising cookies or Google Analytics.
To reduce repeated form submissions, the server creates short-lived hashes from an IP address and an hourly window, using the same abuse-protection mechanism across forms. Raw IP addresses are not stored in our database. These records expire after two hours.
Visit-match answers
If you choose to answer “Did this match your visit?”, we add your choice to a daily count for that park and your selected topic. We use these counts privately to decide which guides to check again. We do not publish visit-match results in this first phase. Please answer only about your own visit; “I have not visited” is counted separately and is not treated as a visit report.
The count table contains the UTC date, park, topic, answer and total only. It does not contain your name, email, medical details, visit date or a copy of an individual response. Daily buckets are removed from our active database within 400 days by hourly cleanup, with earlier cleanup when the service is used. We use the same short-lived IP-hash abuse protection described above. Visit-match rate-limit records expire at the next UTC hour and are removed by hourly cleanup, within the existing two-hour window. Raw IP addresses are not stored in our database. Our hosting provider also processes requests to deliver and protect the site.
“Tell us privately what was different” opens the existing private feedback form. That form has its own notice and retention rules below. Your visit-match answer does not send a written review or sign you up for contact. The visit-match form does not set a cookie, local-storage identifier or session-storage identifier.
When you send feedback
We store your chosen topic, the park, your message, the page you came from, the submission time and a reference code. We do not ask for your name or email address, and we never contact individuals. Please do not send names, medical details, children’s details, booking references or other sensitive information. There are no file uploads.
Messages are stored in the site’s Cloudflare database and are visible only to the site owner and the AI-assisted workflow (Anthropic’s Claude) used to review them. AI helps categorise messages and check corrections against official park sources.
Public answers
Useful questions and corrections are answered on the public questions and answers page. We reword every question in our own words and remove anything that could identify you; your message itself is never published or quoted. Messages that are spam, abusive or too personal to publish are not answered.
Retention and control
Messages are retained for up to 180 days, then deleted. Published answers remain on the site because they are our own words and contain nothing that identifies you. Aggregate daily vote counts are retained for up to 400 days.
To ask about or remove your message, use the privacy enquiry form and include the reference code you were given. We will delete the message and confirm the deletion on the questions page by reference only.
Partner links
Our pages set no advertising or affiliate cookies, and we do not pass your details to partners. When you click a link marked Ad, you leave our site; the partner, or the affiliate network that tracks the referral, may set cookies on its own site so it can credit us. Their privacy policies apply from that point. Since 11 November 2026, each Ad link also carries the name of the page it sits on (for example, alton) so that the network can tell us which page a booking came from; the network also shows it to the partner, and may add it to the web address of the partner’s page. It names our page, never you. Our analytics stay as described above: Cloudflare Web Analytics, no Google Analytics.
Other sites
Official park links take you to other organisations with their own privacy policies. You do not need to sign in to read the guide or send feedback.
