Privacy policy
Last updated: July 2026
Who we are
The data controller for Parkwise is Parkwise, of United Kingdom (postal address available on request via hello@parkwise-app.com). Contact: hello@parkwise-app.com.
Parkwise operates the mobile app and website at parkwise-app.com. This notice explains how we use personal data under UK GDPR.
What we collect
Account data — email, username, optional profile photo, language and privacy preferences.
Location data — device location for nearby parking, destination search, contribution validation and optional background nearby-parking alerts (device-local geofencing when you grant “Always” location).
Contribution data — availability reports, verifications, issue reports, sign photos, new location submissions and related coordinates when you contribute.
Purchase data — store receipts and entitlement records when you buy access via Apple App Store or Google Play (we do not receive your full payment card details).
Support and safety — support messages, user reports, block lists and moderation records.
Website waitlist — email and platform choice if you join the launch waitlist.
Anonymous website usage — when you browse parkwise-app.com we keep daily aggregate counts of page visits and useful on-page actions (for example opening a car park card, selecting a map pin, requesting directions, or clicking an App Store / waitlist button). Each count stores only the UTC date, a normalised page path, an action type, and where needed a non-personal entity id (such as a parking location id) or placement label. We do not use cookies for this, do not store your IP address for it, do not create anonymous IDs or session IDs, and cannot identify you or reconstruct your journey from these counts. This helps us understand which pages and parking locations drivers find useful. Waitlist emails are stored separately for the waitlist itself and are never written into these aggregate counters.
Analytics (optional) — Google Analytics 4 loads only after you choose “Accept analytics” on the cookie banner; in the app, Firebase Analytics loads only if you opt in under Settings → Privacy.
How we use data and lawful bases
| Purpose | Typical data | Lawful basis |
|---|---|---|
| Provide the app and your account | Account, preferences, access entitlements | Contract |
| Show parking and validate contributions | Location, contribution records | Contract; legitimate interests (map quality) |
| Destination search | Search text, location bias (see below) | Contract; legitimate interests (minimised transfer) |
| Community features (leaderboards, public profiles) | Username, points, optional avatar | Consent (opt-in visibility) |
| Fraud prevention and abuse | Reports, blocks, logs | Legitimate interests |
| Anonymous website usage statistics | Page path, UTC date, action type, optional non-personal entity/placement (aggregated counts only) | Legitimate interests (understand popular content and useful actions) |
| Product analytics (optional) | App/screen events (non-essential) | Consent |
| Waitlist communication | Consent | |
| Legal and tax records for purchases | Transaction references | Legal obligation / contract |
Destination search and third-party geocoding
When you search for a destination in the app, your query and a precise location bias (latitude/longitude to improve local results) are sent to Photon (Komoot) — an OpenStreetMap-based autocomplete service. Some searches may also use your device's platform geocoder (Apple/Google). We do not sell this data. Queries are sent only to perform the search you request. See our legitimate-interests assessment for A-015 in internal compliance records.
Recipients and processors
- Supabase — database, authentication, storage (EEA/US — Standard Contractual Clauses where applicable)
- Apple App Store / Google Play — distribution and in-app purchase validation
- Firebase / Google Analytics — optional app analytics (consent only)
- Vercel — website hosting
- Resend — transactional email (waitlist, support)
- Expo / EAS — app build and delivery
- Mapbox — map tiles and static map images on the website
- Photon (Komoot) — destination autocomplete
A full register is maintained in our internal processor documentation. We require processors to protect data under Article 28 UK GDPR terms where applicable.
International transfers
Some providers process data in the United States or other countries outside the UK. Where required, we rely on UK adequacy regulations, Standard Contractual Clauses, or equivalent safeguards. You may request more information about transfers by contacting us.
Retention
- Account and profile data — until deletion, then removed within 30 days
- Contribution coordinates attached to you — up to 90 days after validation, then deleted or aggregated
- Availability reports — display relevance 60 minutes; raw records up to 90 days
- Store purchase records — up to 6 years where required for accounting/disputes
- Anonymous website page counts — aggregated by path and day; retained up to 14 months, then deleted or rolled up
- Support and moderation — typically 24 months after closure
- Waitlist — until launch + 6 months, or until you withdraw consent
Your rights
You may access, rectify, erase, restrict, object (where applicable) and port your data, and withdraw consent for optional processing. Delete your account in Settings → Delete Account or use our web deletion form. We respond within one month. You may complain to the ICO (ico.org.uk).
Cookies and analytics
Anonymous page counts do not use cookies or similar storage on your device. They run server-side when you load a public page and are separate from the optional analytics below.
Non-essential website analytics load only after cookie consent. The mobile app keeps Firebase Analytics off by default until you opt in. Dev builds and Testing Mode are excluded. We do not use advertising cookies.
Community safety
See our community standards for reporting, blocking and moderation response times.
Changes
We update this page when our practices change. Material changes will be highlighted in the app where appropriate.