Security and compliance checks are usually the last, and shortest, part of a car subscription software evaluation. They come after the vehicle demos, the pricing discussion and the implementation timeline, and they are often treated as something the vendor has handled and the buyer can confirm with a checkbox.
That order is backwards. A data breach in a subscription operation exposes subscriber identity documents, biometric checks, payment mandates, credit records and vehicle location data. Under data protection law, the operator is the data controller, so the liability sits with the operator, not the platform vendor. Car subscription software security compliance is the operator's responsibility, and understanding exactly what a platform has certified before you sign is not optional. This guide covers the standards that matter, what each one actually proves, and a checklist to use before you commit.
TL;DR
- Car subscription platforms hold several categories of particularly sensitive data: identity documents, biometric verification results, credit records, payment mandates, driving records and, in many cases, real-time vehicle location. Each carries specific regulatory obligations.
- UK GDPR and EU GDPR apply to operators processing the personal data of people in the UK or EU, including operators based elsewhere that offer subscriptions to them. Serious violations can be fined up to 4% of global annual turnover, or £17.5 million under UK GDPR (€20 million under EU GDPR), whichever is higher.
- ISO 27001 is the internationally recognised standard for information security management, and UK and EU enterprise buyers typically require it. US enterprise buyers typically ask for a SOC 2 Type II report.
- PCI DSS governs payment card data. Operators should confirm that card data is handled within the platform's or payment gateway's certified environment, not passed through their own systems.
- The right question is not "are you compliant?" but "what are your current certifications, when were they last audited, and by whom?" Vendor claims without documents are not compliance evidence.
The Four Compliance Pillars at a Glance
Why Does Security Compliance Matter for Car Subscription Platforms?
A car subscription platform builds up a concentrated profile of sensitive personal and financial data for every subscriber. From onboarding onwards, the platform holds or processes:
- Images of government-issued identity documents, such as a passport or driving licence
- Biometric verification data from liveness and facial comparison checks
- Driving licence records, including endorsements and disqualifications, accessed through the DVLA in the UK or state records in the US
- Credit reference data from the affordability or credit check
- Payment card or bank mandate details for recurring billing
- Real-time vehicle location data, if telematics integration is active
- Vehicle condition photographs from handover and return inspections
Some of these carry extra weight under data protection law. Biometric data used to identify a person is special category data under GDPR, which needs an additional legal condition, usually explicit consent. Information about motoring offences, such as licence endorsements, can count as criminal offence data, which also has stricter rules. Our guide to KYC and identity verification for car subscription covers how these checks fit into onboarding.
Under GDPR, the operator running the subscription programme is the data controller: the party that decides why and how personal data is processed. The platform vendor is usually a data processor, acting on the operator's instructions. That means a breach or compliance failure by the vendor is still a failure in the operator's own compliance. The fine, the regulatory investigation and the duty to notify subscribers all sit with the operator.
What Is GDPR's Role in Car Subscription Data Handling?
The UK General Data Protection Regulation and the EU GDPR both apply to car subscription operators processing the personal data of people in the UK and EU. Their reach is broad: an operator based outside the UK or EU that offers subscriptions to people there must still comply.
The GDPR obligations most relevant to car subscription platforms are:
- Lawful basis for processing: Every type of data the platform processes needs a lawful basis. The subscription contract itself relies on contractual necessity. Identity verification required for anti-money laundering purposes may rely on legal obligation. Telematics location data usually relies on consent or legitimate interests, with a documented balancing test. Biometric checks also need a special category condition. The lawful basis for each activity must be documented and available if the ICO in the UK, or the relevant EU supervisory authority, asks for it.
- Data minimisation: The platform should collect only the data the subscription service needs. A platform that asks for personal data beyond what is required for identity, payment and licence checks creates unnecessary regulatory exposure.
- Retention and deletion: Subscriber data must not be kept indefinitely. The platform should support configurable retention schedules that delete or anonymise data after a defined period once the subscription ends. Identity verification data, payment mandates and credit check results each have different appropriate retention periods.
- Data subject rights: Subscribers have rights to access, correct, erase and port their data. The platform should let the operator fulfil these requests without manual database work. A right-to-erasure request after a subscription ends must be handled without deleting records the operator needs for its own legal obligations, such as inspection records relevant to an insurance claim.
- Data Processing Agreement: The contract between operator and vendor must include a Data Processing Agreement (DPA) meeting the requirements of GDPR Article 28. An operator using a subscription platform without a signed DPA is outside GDPR requirements from day one.
What Does ISO 27001 Certification Mean for a Subscription Platform?
ISO 27001 is the international standard for information security management systems (ISMS). Certification means an accredited certification body has independently audited the organisation's security management against the standard and found it meets the requirements. Certificates need annual surveillance audits and full recertification every three years.
For a car subscription platform, ISO 27001 certification is evidence that the vendor has:
- Identified and systematically managed information security risks across the platform
- Implemented controls covering physical security, access control, encryption, incident management and business continuity
- Put ongoing monitoring and improvement of those controls in place
- Had those controls independently audited
ISO 27001 is the standard UK and EU enterprise buyers most often require. Dealer groups, OEM procurement teams and fleet operators will typically ask for the certificate and its scope before approving a vendor. Scope matters: a certificate covering only part of the vendor's business is not the same as one covering the whole subscription platform and its data processing.
The current version of the ISO 27001 standard, maintained by the International Organization for Standardization, is ISO/IEC 27001:2022. The transition period for certificates issued against the older 2013 version ended in October 2025, so a current certificate should reference the 2022 version. You can verify a vendor's status by asking for the certificate and checking that the issuing body is UKAS-accredited in the UK, or accredited by a member of the International Accreditation Forum (IAF) elsewhere.
What Is SOC 2 and Why Do Enterprise Buyers Ask for It?
SOC 2 is a framework developed by the American Institute of Certified Public Accountants (AICPA) for assessing how technology and SaaS companies manage customer data. It covers five Trust Services Criteria: security, availability, processing integrity, confidentiality and privacy. Security is mandatory; the others are included as relevant.
Unlike ISO 27001, SOC 2 is not a certification. It is an attestation report issued by a licensed CPA firm after an independent audit, and it comes in two types:
- SOC 2 Type I: Assesses whether security controls are designed appropriately at a single point in time.
- SOC 2 Type II: Assesses whether those controls actually operated effectively over a defined period, typically 6 to 12 months. This is the report US enterprise buyers expect. A Type I report on its own is weak evidence of operational security.
A car subscription platform selling to US fleet operators, OEMs or dealer groups whose parent companies apply US procurement standards will be asked for a SOC 2 Type II report in any serious vendor evaluation.
UK and EU buyers lean more on ISO 27001, which aligns well with GDPR Article 32's requirement for appropriate technical and organisational security measures. The two are not interchangeable. A vendor with ISO 27001 but no SOC 2 report may struggle with US enterprise buyers, and the reverse is true in the UK and EU. For platforms operating in both markets, holding both is increasingly the baseline.
How Should Payment Data Be Secured? PCI DSS Explained
The Payment Card Industry Data Security Standard (PCI DSS) governs how payment card data is captured, transmitted, stored and processed. Any system that touches cardholder data must comply, and compliance is validated either by a Qualified Security Assessor (QSA) audit or a Self-Assessment Questionnaire (SAQ), depending on transaction volume and how card data is handled.
For car subscription operators, the key principle is scope reduction: don't touch cardholder data if you can avoid it. A platform that routes card data through the operator's own systems, even briefly, makes the operator responsible for PCI DSS compliance on those systems. A platform that uses tokenisation, where the payment gateway captures card details directly and passes back only a non-sensitive token, dramatically reduces the operator's compliance scope. Our guide to car subscription billing software explains how this fits into recurring payments.
Ask platform vendors these specific questions:
- Does the platform capture card data on its own servers, or does the payment gateway capture it directly?
- What is the vendor's PCI DSS compliance level, and when was it last validated?
- Can the vendor provide its PCI DSS Attestation of Compliance (AoC)?
- Which payment gateways are supported, and are they all PCI DSS compliant?
A vendor who cannot answer these questions specifically should not be trusted with your subscribers' card data.
Compliance Checklist Before Signing a Car Subscription Software Contract
Use this checklist before committing to any car subscription platform vendor.
Data protection
- A signed Data Processing Agreement (DPA) meeting GDPR Article 28 is included in the contract or available as a standard addendum
- The vendor can state which countries subscriber data is stored in and transferred to, and what safeguards cover any international transfers
- The platform supports configurable data retention and deletion schedules
- The vendor has a documented process for supporting data subject requests within the statutory deadline (one month under UK GDPR, extendable in limited cases)
- The vendor commits to notifying you of a personal data breach without undue delay, ideally within 24 to 48 hours, so you can meet your own 72-hour deadline for reporting to the ICO
Information security
- The vendor holds current ISO/IEC 27001:2022 certification from a UKAS or IAF-accredited certification body (for UK and EU operations)
- The vendor has a recent SOC 2 Type II report from a licensed CPA firm (for US operations or US enterprise buyers)
- Certificates and reports are current: check issue dates and the audit cycle
- The certification scope covers the subscription platform and its data processing, not just the vendor's corporate IT
Payment security
- The platform uses tokenisation that keeps card data inside the payment gateway's environment
- The vendor can provide its PCI DSS Attestation of Compliance
- All supported payment gateways are PCI DSS compliant
- Failed payment handling and refunds never require staff to access full card details
Access controls and operational security
- Role-based access controls stop staff from seeing data beyond what their job requires
- All data in transit is encrypted (TLS 1.2 or higher)
- All data at rest is encrypted (AES-256 or equivalent)
- The vendor runs regular penetration tests through an independent third party
- Multi-factor authentication is required for administrative access
Contract and exit
- The contract states what happens to subscriber data when the contract ends
- Data portability obligations are defined, including format and timeframe
- The vendor discloses its sub-processors, meaning the third parties it shares data with
How the JRNY Platform Approaches Security and Compliance
The JRNY Platform is built for operators who hold sensitive subscriber data as a core part of their business, with data security designed into the platform architecture rather than added afterwards. Identity verification, booking, billing and fleet data sit on one platform, so access controls and retention rules apply consistently across the subscriber record.
For operators in the evaluation stage, the car subscription software page covers the platform's capabilities. Security and compliance documentation, including certification status and DPA terms, is available from the Tomorrow's Journey team as part of procurement. Book a demo to discuss the security requirements for your market and subscriber base.
Key Takeaways
- The operator is the data controller: Vendor compliance reduces risk but does not transfer the regulatory obligation. Fines, breach notifications and ICO investigations are the operator's responsibility.
- Ask for certificates, not claims: ISO 27001 certificates and SOC 2 reports are independently audited documents with dates. A vendor that says it "follows ISO 27001 principles" without a certificate is not ISO 27001 certified.
- PCI DSS scope reduction is the practical goal: Operators should avoid handling card data wherever possible. A platform that uses tokenisation correctly keeps you out of PCI DSS scope for cardholder data.
- GDPR compliance starts with the DPA: No signed DPA means no GDPR-compliant vendor relationship, whatever the vendor's marketing says about data protection.
- The checklist is a starting point: Large or complex deployments may need an independent security assessment of the vendor beyond what standard certifications cover.
FAQs: Car Subscription Software Security and Compliance
1. Does GDPR apply to car subscription businesses in the UK?
Yes. UK GDPR applies to any organisation processing the personal data of people in the UK. Car subscription operators handle identity documents, credit data, payment information and vehicle location data, all of which is personal data, so they must comply with UK GDPR. Operators processing the data of people in the EU must also comply with EU GDPR.
2. What is the difference between ISO 27001 and SOC 2?
ISO 27001 is an international certification for information security management systems, issued by an accredited certification body, and is the standard UK and EU enterprise buyers most often require. SOC 2 is a US attestation framework, developed by the AICPA, under which a licensed CPA firm reports on how a technology company manages customer data against the Trust Services Criteria. US enterprise buyers typically require a SOC 2 Type II report. For platforms operating in both markets, holding both is increasingly the baseline.
3. What should I check about a platform's PCI DSS compliance?
Ask for the vendor's Attestation of Compliance and confirm when it was last validated. Check whether card data passes through the vendor's systems or is captured directly by the payment gateway. A platform that uses tokenisation should never have access to full card numbers. If a vendor cannot clearly explain its tokenisation approach, treat that as a significant risk.
4. Is biometric identity verification data treated differently under GDPR?
Yes. Biometric data used to uniquely identify a person, such as the facial comparison in a digital ID check, is special category data under GDPR. Processing it needs both a lawful basis and an additional condition, usually explicit consent. Check that your platform's ID verification provider records that consent and applies a short, defined retention period to biometric data.
5. What happens to subscriber data when I switch platforms?
The contract should set out data portability terms: the format subscriber data will be provided in, the timeframe, and what happens to data the vendor still holds after export. Without contractual portability rights, an operator depends on the vendor's goodwill when switching. This is a standard negotiation point and should be agreed before signing.





