Parkwise is operated as a sole trader in the United Kingdom by Joe Reynolds (tryparkwise@gmail.com). Parkwise is the data controller for personal data collected through this website and the Parkwise iOS app.
If you have any questions about this policy or how we handle your data, email us at tryparkwise@gmail.com.
The table below sets out every category of personal data Parkwise collects, the purpose, our legal basis under UK/EU GDPR, and how long we keep it.
| Data | Purpose | Legal basis (UK/EU GDPR) | Retention |
|---|---|---|---|
| Name | Greeting you and personalising your trip (from Sign in with Apple or Google, or the name you type in Profile) | Contract performance (Art. 6(1)(b)) | Until account deleted |
| Email address | Signing in via Firebase Auth (Sign in with Apple or Google) | Contract performance (Art. 6(1)(b)) | Until account deleted |
| User ID (Firebase UID) | Linking your trip, plans and subscription across sessions and devices; also used as your RevenueCat ID | Contract performance (Art. 6(1)(b)) | Until account deleted |
| Trip data (dates, parks, party size by age group, plans, favourites, tickets you add) | Building and syncing your itinerary | Contract performance (Art. 6(1)(b)) | Until account deleted or trip reset |
| Parker AI chats and AI plan requests | Answering your questions and building day plans: sent to our server, which forwards them to Anthropic with your trip details (dates, parks, party size by age group) | Contract performance (Art. 6(1)(b)) | Not stored by Parkwise. We keep only counts (date, type, tokens used) to enforce fair-use limits; see Anthropic's retention policy |
| AI usage counts | Fair-use limits on AI features | Legitimate interest (Art. 6(1)(f)) | Reset monthly; deleted on account deletion |
| Coarse location | Suggesting the park you're at and in-park features | Contract performance (Art. 6(1)(b)) | Processed on your device only; never stored by Parkwise |
| Purchase history (subscription status) | Granting Parkwise Pro via RevenueCat | Contract performance (Art. 6(1)(b)) | Until account deleted (the RevenueCat record is deleted too) |
| Crash reports and device diagnostics | Fixing crashes (Firebase Crashlytics): crash stack, app version, iOS version, device model, free memory and disk, an install ID. Not linked to your identity | Legitimate interest (Art. 6(1)(f)) | 90 days (Crashlytics default) |
| Product interaction events | Understanding which features help (Firebase Analytics), see below. Fixed values only, an install ID, no advertising ID, not linked to your identity | Legitimate interest (Art. 6(1)(f)) | 14 months (Firebase default), aggregated |
| Feedback you send | Answering and improving the app (message, optional screenshot, app version, device model) | Legitimate interest (Art. 6(1)(f)) | Until resolved, then up to 12 months |
| Early access email (website sign-up) | Telling you when Parkwise launches | Consent (Art. 6(1)(a)) | Until you unsubscribe or ask us to delete it |
The app sends eight events, with fixed values only (never free text, names or locations): set-up completed (dated, undated or skipped), quick start used, paywall viewed (which screen), purchase completed (monthly, annual or other), Parker message sent, AI plan built, Today Mode opened, and trip completed. Firebase also sends its standard events (first open, session start, app update). We don't set a user ID in Analytics or Crashlytics, we don't use the advertising identifier, and nothing is used for advertising or shared with data brokers.
To stop other apps and scripts misusing our servers, the app uses Firebase App Check with Apple's App Attest. It proves a request comes from a genuine copy of Parkwise. It doesn't identify you and isn't used for tracking.
This website loads fonts from Google Fonts (fonts.googleapis.com), which may transmit your IP address to Google's servers in the United States. No advertising cookies, tracking pixels, or analytics scripts are used on this website.
We use a single first-party localStorage key (pw_cookie_consent) to remember your cookie consent choice. This is not a tracking cookie.
Parkwise uses the following sub-processors, each of which may receive your personal data as part of operating the service:
Firebase Auth manages sign-in. Firestore stores trip and usage data. Cloud Functions run Parker, AI plans and account deletion. Firebase Analytics receives the usage events above and Crashlytics receives crash reports, in release builds, without a user ID. App Check verifies requests come from the genuine app.
Google LLC, USA. Transfers to the US are covered by the EU-US Data Privacy Framework and Google's Data Processing Addendum.
Google Privacy Policy
Parker chats and AI plan requests are sent from the app to our server (Firebase Cloud Functions), which adds the trip details needed (dates, parks, party size by age group) and forwards them to Anthropic's API over HTTPS. Messages may contain personal information you choose to share. Anthropic processes this data as a sub-processor and doesn't use it to train its models.
Anthropic PBC, USA. Transfers to the US are made under standard contractual clauses.
Anthropic Privacy Policy
RevenueCat manages in-app purchase validation and Pro entitlements. It receives your Apple purchase receipts and subscription status, linked to your Parkwise user ID so Pro works on all your devices.
RevenueCat, Inc., USA. RevenueCat Privacy Policy
Park maps are drawn with Mapbox. Loading map tiles sends Mapbox your IP address and basic device information. Your position on the map is shown on your device.
Mapbox telemetry is off by default in Parkwise. You can choose to turn it on from the map's “i” (attribution) menu, and turn it off again there at any time. If you turn it on, Mapbox's SDK sends de-identified map usage data and, if you've given Parkwise location permission, your device's location to Mapbox for analytics. Mapbox says it doesn't link this to your identity or use it for advertising.
Mapbox, Inc., USA. Mapbox Privacy Policy
Live wait time and park schedule data is fetched from api.themeparks.wiki. No personal data is transmitted to this service; it is a read-only public API.
Weather forecasts for park locations are fetched from wttr.in. No personal data is transmitted.
Parkwise is based in the UK. Our third-party processors (Firebase, Anthropic, RevenueCat, Mapbox) are located in the United States. Transfers of personal data from the UK or EEA to the US are made under the UK International Data Transfer Agreement (IDTA) or EU Standard Contractual Clauses (SCCs), as applicable to each processor.
All data transmitted between the app, our server and our processors is encrypted in transit using TLS. Firestore data is encrypted at rest by Google. Database rules let each signed-in user read and write only their own data, and our AI service keys are held on the server, never in the app. We do not store payment card numbers: all payment processing is handled by Apple via StoreKit and RevenueCat.
Parkwise is not directed at children under 13. We do not knowingly collect personal data from children under 13. If you believe a child under 13 has provided us with personal data, please contact us at tryparkwise@gmail.com and we will delete it promptly.
Under UK GDPR and, where applicable, EU GDPR, you have the following rights:
To exercise any of these rights, email tryparkwise@gmail.com. We will respond within 30 days. You also have the right to lodge a complaint with the Information Commissioner's Office (ICO) in the UK at ico.org.uk, or your local supervisory authority if you are in the EEA.
You can delete your Parkwise account at any time in the app: Profile → Delete Account. Deletion runs on our server and removes:
If you signed in with Apple, the app first asks you to confirm with Apple once more so we can revoke Parkwise's Sign in with Apple token, which removes the connection from your Apple ID. An active App Store subscription is managed by Apple: cancel it in Settings → Apple ID → Subscriptions. Crash reports and usage events aren't linked to your identity, so they expire on the schedule above. To also remove your email from our early access list, email tryparkwise@gmail.com.
We may update this Privacy Policy from time to time. When we make material changes we will update the "Effective date" at the top of this page. Continued use of the app or website after changes are posted constitutes acceptance of the updated policy. We recommend checking this page periodically.
For any privacy questions or to exercise your rights, contact:
Joe Reynolds
Parkwise, Sole trader, United Kingdom
tryparkwise@gmail.com