Safety you can see, data you can trust
ParkGo is built on verification, visibility and strict data protection. Here's exactly how we keep travellers and hosts safe β and how we handle your information.
Safety on both sides
Verified people and verified moments
Trust isn't a badge β it's a set of checks that happen before, during and after every booking.
Two-sided verification
Both sides of every booking are verified. Hosts complete identity and address checks; travellers register real accounts; the terminal transfer is handled by a licensed operator.
ID-checked hosts
Every host passes a KYC identity check and a right-to-list declaration before a single space goes live.
Licensed & insured transfer operator
Your terminal transfer is provided by an independent, licensed and insured operator, integrated by API. Their operator, vehicle and driver compliance sits with them; ParkGo keeps the customer-facing trust β live location and a verified handover.
CCTV & live camera
Spaces can include CCTV, and travellers can watch a live in-app camera of their car with a LIVE badge and timestamp.
Verified handovers
Drop-off and collection are each confirmed with a one-time code, creating a timestamped, logged chain of custody.
Two-sided trust scoring
Travellers and hosts rate each other after every trip, and you can rate your transfer too. Scores keep the network honest and high quality.
ParkGo Limited holds Employers' Liability (Compulsory) Insurance (Β£5m).
The verified handover
A clear, logged chain of custody
The handover is the moment that matters most. ParkGo turns it into a confirmed, timestamped event so there's never any doubt about who had the car and when.
One-time codes
A unique code is confirmed by both parties at drop-off and collection.
Timestamped & logged
Each confirmation is recorded with a time, creating an auditable trail.
Live context
Live location and the in-app camera give everyone the same picture in real time.
One-time code
4K9PQ2
Confirmed by both parties Β· 14:32
- Host confirmed drop-off
- Driver confirmed pick-up
- Event written to audit log
Data protection
GDPR and ICO-aligned, by design
We treat your data as something we look after, not something we own. Our approach is built around UK GDPR principles and ICO guidance.
Minimal data
We collect only what a booking genuinely needs β and no more. Data minimisation is the default.
Lawful basis & consent
Every use of your data has a lawful basis. Where we rely on consent, it's specific, informed and easy to withdraw.
Defined retention
Personal data is kept only as long as needed, then deleted or anonymised on a defined retention schedule.
Data-subject requests
Access, correct, export or erase your data. We honour data-subject requests in line with UK GDPR.
Separated, encrypted KYC
Identity and bank documents are encrypted and stored separately from your everyday profile data.
Audit logging
Sensitive actions are recorded in an audit log so access can be reviewed and accounted for.
Least privilege & RLS
Strict access controls and row-level security mean people and services only ever see what they should.
Breach response
A defined incident process means we contain, assess and notify quickly if anything ever goes wrong.
Under the hood
Security baked into the platform
Good intentions aren't enough β protection has to be engineered in. These are the controls that sit behind every booking.
Encryption of sensitive data
Identity and payment-related documents are encrypted at rest and in transit.
Least privilege & row-level security
Access is restricted to the minimum needed, enforced at the data layer.
Audit logging
Sensitive operations are logged so access can be reviewed and accounted for.
Defined breach response
A clear incident process to contain, assess and notify without delay.
Have a question about safety or privacy?
We're happy to explain anything about how we verify people or handle your data. Get in touch and we'll point you to the detail.
Verification and re-verification run continuously, not just at sign-up.