The Minimal-Data Approach to Driving Test Swaps

Deriving the minimum

To match two learners you must know what each has and what each wants. What they have: a test at a centre, on a date, at a time. What they want: a preferred date range and acceptable centres. Everything else — names, licences, references — contributes nothing to the match, so a minimal-data platform doesn't collect it.

Minimisation as protection

• Breach-proof by absence: a database of test dates and centre names contains nothing a fraudster can monetise.
• Scam-proof by design: with no credential fields in the product, there's nothing for a bad actor to phish out of other users.
• Compliance by default: UK GDPR's data-minimisation duty is met structurally, not by policy promise.

Where the sensitive step lives

The single moment requiring identity — changing the booking — is delegated to the one party who should hold it: DVSA, on their official phone line, verifying each learner against their own records. The platform never becomes a honeypot because the honey never enters the platform.