Privacy
Last updated 11 October 2026
This notice explains how Parkstack handles personal information for its own website and operator service. A park's guest website has a separate privacy page naming that park.
Who is responsible
PARKSTACK LTD, company number 17483563, is the controller for operator accounts, enquiries and its own business administration. Its registered office is 128 City Road, London, United Kingdom, EC1V 2NX. When a guest buys a ticket or contacts a park, that park is normally the controller and Parkstack processes the information for it. Privacy questions can be sent to hello@parkstack.net.
Information we use
- Operator names, work email addresses, account security records, park memberships and support messages.
- Email addresses submitted with consent for an update when new park registration reopens.
- Park website content, configuration, audit history, subscription, invoice and entitlement records.
- Guest order contact details, tickets, visit dates and refund records on behalf of the relevant park.
- Technical security information such as request addresses, timestamps and error records.
Parkstack does not store full card numbers. Stripe handles card details.
Why we use it
We use information for these purposes, each on the legal basis shown. Providing operator accounts, the console and billing: our contract with the park operator. Keeping financial, tax and company records: legal obligation. Keeping the service secure, preventing abuse and fraud, supporting users and improving reliability: our legitimate interests in running a secure, working service for the parks that rely on it, which we balance against the expectations of the people whose information it is. Sending updates to people who joined the updates list: consent, which can be withdrawn at any time.
Service providers and international processing
These suppliers process information for Parkstack. They receive only the information needed for their service.
| Supplier | What it does | Where |
|---|---|---|
| Railway | Runs the Parkstack application servers | Amsterdam, Netherlands |
| Neon | Hosts the database | London, UK |
| Cloudflare | Delivers websites, stores photos and files, keeps encrypted database backups (in the EU), and checks sign-up forms for bots | Worldwide network, nearest to each visitor |
| Resend | Sends email: tickets, account and security messages | Ireland |
| Stripe | Takes card payments and Parkstack subscriptions | Ireland and the United States |
| Anthropic | Answers questions in the console's help assistant: staff questions and what it looks up to answer them (the park's settings, website content, ticket and website totals, and staff names and roles), never guest details. Kept up to 30 days | United States |
Where information is processed outside the UK, we rely on a UK adequacy decision or appropriate contractual safeguards. We tell parks before adding a supplier that will process their guests' information. Operators can ask for the relevant safeguard information.
How long we keep it
Account and park records are kept while the service is active and for a limited period afterwards for support, disputes and legal duties. A login that no longer belongs to any park is deleted 30 days later. Contact details from incomplete ticket checkouts are removed after 30 days. Direct guest contact details for paid orders are removed 24 months after the purchase and any booked visit. Original order and payment references may be kept for up to seven years for financial records and disputes. Parkstack may keep de-identified ticket counts, dates and financial totals after that for long-term comparisons. Raw first-party analytics are limited to anonymous, tab-scoped identifiers and deleted after three days. Daily totals and aggregated page, attraction and search counts that are no longer linked to a visitor or session identifier may be kept for long-term seasonal and year-on-year comparisons. Security and incident records are kept only as long as needed to investigate and protect the service. An address submitted for registration updates is kept until we send that update or the person asks us to remove it. Encrypted backups of the database are kept for up to 35 days, so information removed from the service can remain in a backup until that backup is deleted. Photos and files a park deletes are kept privately for 30 days so they can be brought back, unless the park removes them for good sooner; they are not shown on any website during that time.
Downloads by park operators
Routine sales downloads contain daily totals and no guest details. A park owner can separately download an order-reconciliation file containing order numbers and email addresses. Parkstack records these downloads. The park is responsible for keeping any downloaded copy secure, limiting access and deleting it when it is no longer needed.
Your rights
Depending on the circumstances, you may ask for access, correction, deletion, restriction, portability or an objection to use of your information. You may withdraw consent where processing relies on it. Contact the park first about a guest order, or contact Parkstack using the address above. If you have a login, you can download a copy of your information and delete your login yourself from Settings → Your account. You may also complain to the UK Information Commissioner's Office at ico.org.uk.
Storage on your device
The operator console uses strictly necessary cookies for sign-in and security. Guest sites use first-party, tab-scoped identifiers for anonymous analytics rather than a persistent cross-session visitor identifier. Every guest site provides an analytics switch on its privacy page. The switch stores only the visitor's choice, and turning analytics off also discards events still waiting to be sent.