Driv3 Privacy Statement

Driv3 Privacy Statement

020 Service Beheer B.V., trading as Driv3 · How Driv3 handles personal data
Version 1.0Adopted 10 October 2026Effective from 10 October 2026KvK 57750173
020 Service Beheer B.V., trading as Driv3 · Prins Mauritslaan 37, 1171 LP Badhoevedorp · KvK 57750173 · privacy@driv3.com
This Privacy Statement applies to the Driv3 platform, the Driv3 apps and driv3.com. It accompanies the General Terms and Conditions v1.0 and uses the same defined terms.

1. Who are we?

020 Service Beheer B.V., trading under the name Driv3, operates the digital platform for the distribution, administration and processing of rides within the transport industry (the "Platform").

020 Service Beheer B.V. · trade name Driv3 · Prins Mauritslaan 37, 1171 LP Badhoevedorp · Chamber of Commerce (KvK) 57750173 · privacy@driv3.com (privacy questions and requests) · info@driv3.com (other questions).

In this Privacy Statement, 020 Service Beheer B.V., trading under the name Driv3, is referred to as "Driv3", "we" or "us". Capitalised terms have the meaning given in the General Terms and Conditions of Driv3 (the "Terms").

This Privacy Statement explains which personal data we process, why we do so, on which legal basis, with whom we may share data, how long we retain data and which rights data subjects have.

Driv3 has not appointed a data protection officer; under the GDPR this is not mandatory for our processing activities. Privacy questions are handled by the management via privacy@driv3.com.

2. Our role under the GDPR

The allocation of roles under the GDPR is the same as in article 9.1 of the Terms.

Driv3 is an independent controller for:

  • account registration, account management, authentication and security of the Platform
  • onboarding, trial period, subscriptions, invoicing and collection
  • KYC/KYB, driving licence and authorisation verification, RDW and register checks
  • payment processing, Wallet, Treasury and card functionalities in cooperation with Stripe
  • fraud prevention, risk management, network integrity and incident handling
  • tax reporting (DAC7), CDT obligations and other legal obligations
  • support, product communication, marketing and improvement of the Platform

Driv3 is a processor for customer and passenger data and data of Drivers, dispatchers and employees that a Carrier, Community Holder or other business User enters into the Platform itself or has processed via the Platform. That User is the controller for such data. The data processing agreement of Driv3 (Annex 1 to the Terms) applies to this processing. Driv3 processes these data solely in accordance with the instructions of that User and for the purposes of the Platform, except where a legal obligation (such as CDT or DAC7) requires Driv3 itself to process them; for that processing Driv3 is the controller.

There is no joint controllership between Driv3 and Users, Carriers or Community Holders, unless expressly agreed in writing.

Stripe, financial partners, banking partners, verification partners and other third parties may, depending on the processing concerned, act as independent controller or as processor. Stripe is an independent controller for KYC/KYB and payment processing on the basis of the Stripe terms and the privacy statement of Stripe.

Users who export personal data from the Platform, store them outside the Platform, combine them with their own systems or use them for their own purposes are themselves the controller for such use, including lawfulness, security, retention periods and the duty to inform.

3. Which personal data do we process?

Depending on the use of the Platform, we may process, among other things, the following personal data.

3.1 Identification and contact data

  • name
  • address
  • e-mail address
  • telephone number
  • date of birth, where required for verification
  • language preference
  • contact preferences
  • communication data
  • user ID
  • customer or account number
  • representative data

3.2 Business and professional data

  • company name
  • trade name
  • Chamber of Commerce (KvK) number
  • VAT number
  • registered business address
  • business contact details
  • legal form
  • data of directors, representatives or ultimate beneficial owners, where required
  • licence data
  • driver card data
  • vehicle data
  • vehicle type
  • vehicle class
  • insurance data
  • inspection data
  • APK (periodic vehicle inspection) data
  • taxi inspections or periodic inspections
  • contract data
  • subscription data
  • trial period data
  • community roles
  • community memberships

3.3 Account and login information

  • username
  • account ID
  • roles and rights within the Platform
  • login history
  • IP address
  • device and browser data
  • session data
  • security settings
  • two-factor authentication data
  • technical log data
  • account status
  • verification status
  • subscription status
  • trial period status
  • payment status
  • cancellation date
  • activation and acceptance data

3.4 Ride data

  • pick-up and destination location
  • time of ride
  • ride status
  • ride price
  • tariff data
  • vehicle type
  • vehicle class
  • service level
  • payment method
  • passenger information to the extent necessary
  • client or Business Customer
  • Community Holder, where applicable
  • assigned Driver or Carrier
  • ride notes
  • route data
  • dispatch data
  • invoicing and administrative data
  • Account Rides
  • approval status of Account Rides
  • payment status of Account Rides
  • payout status
  • mutual forwarding fee
  • network fee
  • complaints or incidents relating to rides

3.5 Location data

For dispatch, ride execution, ETA, safety and CDT registration, we process the location of the Driver's device. This takes place only during the period in which the Driver is logged in as available in the app or is performing a ride. Outside that period, the Platform does not record any location. The Driver enables location access for the Driv3 app on the device themselves and may disable it at any time; without location access, dispatch and ride functionalities do not work.

Location data is used for:

  • execution of rides and dispatch
  • ETA, route and status information
  • safety of Driver and Passenger
  • operational coordination within a Carrier or Community
  • communication with Passengers, clients, dispatchers, Carriers or Community Holders
  • ride administration, evidence and handling of disagreements
  • incident investigation and fraud prevention
  • legal obligations, including CDT registration

While location-based functionalities are in use, the current location and availability of the Driver or the vehicle are visible to Users with the role or rights assigned for that purpose (dispatchers and administrators of the Driver's own Carrier, the Community Holder for community rides) and, to the extent relevant to the ride, to the client and the Passenger. GPS records, timestamps and route data are linked to the Ride Order during a ride and may be consulted afterwards for ride administration, control, safety, handling of disagreements and fraud prevention.

Legal basis: performance of the contract (Article 6(1)(b) GDPR) and the legitimate interest of Driv3, Carriers and Passengers in safe, verifiable and efficient ride execution (Article 6(1)(f) GDPR); for CDT registration, the legal obligation (Article 6(1)(c) GDPR). For Drivers employed by a Carrier, the Carrier is the controller for the processing of their location data and the Carrier informs its Drivers of this before first use; Driv3 provides a standard text for this purpose (see section 15).

Retention period: see section 8. The raw location trail is deleted after 12 months; the record linked to a Ride Order (start and end location, timestamps, route) remains part of the ride record.

3.6 Financial data and payment data

We may process financial data, including:

  • payment and transaction data
  • Stripe Connected Account data
  • Stripe Financial Account data
  • Financial Account IBAN
  • wallet balances
  • Wallet data
  • available balance
  • reserved balance
  • pending balance
  • top-up data
  • provisional balance increases
  • withdrawals
  • payouts
  • subscription costs
  • network fee
  • mutual forwarding fee
  • Stripe Costs
  • credit card costs
  • iDEAL or Wero costs
  • Tap to Pay transactions
  • QR Payments
  • Payment Link payments
  • card payments
  • Issuing Card / Debit Card data
  • card spend
  • spending controls
  • card limits
  • card status
  • chargebacks
  • disputes
  • refunds
  • corrections
  • negative balances
  • reserves
  • balance holds
  • mutual payments
  • Account Rides
  • tips or gratuities
  • bank account data
  • invoice data
  • tax data
  • audit trail and transaction history

3.7 KYC/KYB, compliance and verification data

For onboarding, verification, financial functionalities, Stripe Connect, Stripe Treasury, Stripe Financial Accounts, card functionalities and legal obligations, we may process, among other things:

  • identification data
  • verification status
  • business verification data
  • UBO data
  • director or representative data
  • bank account verification
  • sanctions and compliance checks
  • risk signals
  • fraud prevention data
  • results of KYC/KYB processes
  • data requested by Stripe, Driv3 or verification partners
  • data required for restricting, blocking or activating financial functionalities

To the extent identity documents or data derived from them are processed, this takes place only to the extent necessary for verification, compliance, legal obligations or requirements of Stripe or financial partners.

3.8 Driving licence, authorisation and register data

For driving licence and authorisation verification, we may process, among other things:

  • driving licence data
  • driving licence categories
  • validity date
  • driver card data
  • authorisation status
  • RDW data
  • data from linked registers
  • verification results
  • inspection data
  • vehicle data
  • licence data
  • approval or rejection status

This data may be processed for safety, compliance, fraud prevention, access management, ride functionalities, community access, legal obligations and protection of the Platform.

3.9 Community data

If Users create, manage or participate in Communities, we may process, among other things:

  • community name
  • Community Holder
  • community members
  • community roles and rights
  • admissions
  • removals
  • Community Rules
  • quality requirements
  • vehicle requirements
  • dress codes
  • service levels
  • community settings
  • community rides
  • community messages or notifications
  • community-related complaints
  • community-related payments
  • community participation fees, where available
  • Community Statistics

Community Statistics may relate, among other things, to ride volume, peak hours, average ride prices, availability, acceptance, operational performance or other data.

Community Statistics may be displayed individually, in aggregated, anonymised or limited form, depending on functionality, settings, role, rights, privacy, commercial sensitivity, legislation and technical possibilities.

3.10 Passenger and customer data

The Platform may process personal data of Passengers, Business Customers and clients, including:

  • name
  • contact details
  • pick-up and destination location
  • ride data
  • payment data
  • invoice data
  • remarks on rides
  • business customer information
  • complaints
  • support requests
  • communication data
  • preferences for ride execution, where necessary

Carriers remain themselves responsible for personal data of Passengers, customers and clients that they process, export or use outside the Platform.

3.11 Support, communication and incident data

We may process data from:

  • e-mails
  • chats
  • WhatsApp messages, where used
  • support tickets
  • telephone calls or call notes
  • complaints
  • incident reports
  • technical reports
  • feedback
  • internal notes relating to support, compliance or disagreements
  • reports concerning fraud, misuse, customer relations or community disagreements

3.12 Marketing, communication and preference data

We may process data for communication and marketing, including:

  • e-mail address
  • telephone number
  • name
  • company name
  • communication status
  • preferences
  • consent or opt-out
  • interaction with e-mails or messages
  • product interest
  • participation in promotions, campaigns or updates

Operational messages about rides, payments, verification, account status, safety, changes or legal matters may be necessary for the provision of the services. Marketing communications and commercial product updates may require separate consent or an opt-out option, depending on the applicable rules.

3.13 Technical, cookie and analytical data

We may process technical data for the security, monitoring, improvement and stability of the Platform, including:

  • IP address
  • device ID
  • browser type
  • operating system
  • log data
  • error messages
  • usage statistics
  • performance data
  • security logs
  • cookie or tracking data
  • SDK data
  • local storage
  • analytical data

If consent is required for certain cookies, analytical technologies or marketing technologies, we request separate consent for this. Further information may be included in a separate cookie statement.

3.14 Source of data

We receive most data directly from the User upon registration, onboarding and use of the Platform. In addition, we receive data from:

  • Stripe and verification partners: outcome and status of KYC/KYB, sanctions and risk checks, payment and transaction data
  • RDW and linked registers: driving licence, driver card, vehicle and inspection data
  • Chamber of Commerce (KvK): registration and representation data
  • Carriers, Community Holders and clients: data of their Drivers, employees, customers and Passengers that they enter into the Platform
  • Passengers and Business Customers: through bookings, payments, Payment Links and support requests

3.15 Mandatory data

The provision of identification, business, bank, driving licence, licence and KYC/KYB data is a contractual and, for KYC/KYB and CDT, legal obligation. Without this data, an account cannot be activated, or cannot be fully activated, and ride functionalities, Wallet, payouts and card functionalities are not available (articles 3.7 and 8.1 of the Terms). All other data, such as marketing preferences, is optional.

4. Purposes of processing

We process personal data solely for legitimate, clear and necessary purposes.

Personal data is processed for:

4.1 Service provision and account management

  • creating and managing accounts
  • onboarding of Users
  • managing the trial period
  • managing subscriptions
  • assigning roles and permissions
  • authentication and secure access
  • management of user profiles
  • communication about the Platform
  • recording acceptance of terms
  • management of account status and verification status

4.2 Ride processing and operational services

  • registering, planning, forwarding and performing rides
  • dispatch
  • route and status information
  • GPS location functionalities
  • communication between the Users involved
  • communication with Passengers or clients
  • ride administration
  • invoicing
  • Account Rides
  • community rides
  • complaint and disagreement handling

4.3 Payment processing and financial administration

  • processing payments
  • facilitating Stripe Connect
  • facilitating Stripe Treasury
  • facilitating Stripe Financial Accounts
  • processing the Financial Account IBAN
  • displaying wallet balances
  • processing top-ups
  • processing provisional balance increases
  • processing withdrawals and payouts
  • processing subscription costs
  • processing the network fee
  • processing the mutual forwarding fee
  • reserving balance
  • processing balance holds
  • processing mutual payments
  • processing Tap to Pay
  • processing QR payments
  • processing Payment Links
  • processing card payments
  • processing Issuing Cards / Debit Cards and card spend
  • processing tips and gratuities
  • charging on and setting off Stripe Costs
  • processing chargebacks, disputes and refunds
  • processing negative balances
  • financial reporting
  • audit trail and administration

4.4 KYC/KYB, verification, compliance and risk management

  • identification and verification of Users
  • business verification
  • driving licence and authorisation verification
  • RDW checks or checks via linked registers
  • bank account verification
  • meeting the requirements of Stripe, financial partners and legislation
  • sanctions screening
  • fraud prevention
  • abuse detection
  • risk assessment
  • monitoring of unusual transactions
  • protection of Driv3, Users, Passengers, Stripe and financial partners
  • restricting, blocking or activating functionalities

4.5 Community functionalities

  • creating and managing Communities
  • processing community membership
  • processing community roles and permissions
  • displaying or applying Community Rules
  • admission to and removal from Communities
  • communication within or about Communities
  • processing community rides
  • processing community settings
  • displaying community dashboards
  • displaying Community Statistics
  • processing community-related payments, where available
  • support for community management

4.6 Security and incident handling

  • security of the Platform
  • detection of abuse
  • investigation of incidents
  • prevention of fraud
  • protection of accounts
  • prevention of unauthorised access
  • logging and monitoring
  • handling of security reports
  • investigation of suspicious transactions
  • investigation of account compromise
  • protection of the network

For the investigation of suspected fraud or abuse, Driv3 may, to the extent necessary and lawful, process relevant ride data, ride statuses, cancellations, no-show reports, transactions, timestamps and location data.

4.7 Legal obligations

  • tax administration
  • DAC7 reporting
  • CDT obligations
  • retention obligations
  • reporting to competent authorities
  • compliance with court orders
  • compliance with supervisory obligations
  • identification or reporting obligations
  • other legal obligations

To the extent required and supported by the applicable CDT connection, statutorily prescribed ride and registration data, including location data where applicable, may be processed and provided to the ILT or other competent bodies.

4.8 Support and communication

  • answering questions
  • handling complaints
  • resolving technical problems
  • informing about changes
  • sending operational notifications
  • communication about rides
  • communication about payments
  • communication about verification
  • communication about subscriptions
  • communication about wallet balances
  • communication about account status
  • support with community questions

4.9 Marketing and product communication

  • sending product updates
  • informing about new features
  • informing about offers or promotions
  • sending newsletters
  • improving onboarding
  • inviting feedback
  • measuring interest in products or features
  • customer relationship management

For marketing communication that requires consent or an opt-out option, we apply the rules applicable to it.

4.10 Improvement of the Platform

  • analysis of usage
  • improvement of functionalities
  • improvement of security
  • improvement of support
  • error analysis
  • product development
  • optimisation of operational processes
  • improvement of dashboards
  • improvement of community functionalities
  • improvement of financial functionalities
  • improvement of AI support

Personal data is not sold to third parties.

5. Legal bases

We process personal data only where a valid legal basis exists for doing so.

5.1 Performance of the contract

Many processing operations are necessary for the performance of the contract with Users, including:

  • account management
  • onboarding
  • trial period
  • subscriptions
  • ride processing
  • dispatch
  • GPS functionalities
  • payment processing
  • Wallet functionalities
  • Stripe Connect
  • Stripe Treasury
  • Stripe Financial Accounts
  • Financial Account IBAN
  • top-ups
  • payouts
  • mutual payments
  • card functionalities
  • community functionalities
  • support
  • administration
  • invoicing

5.2 Legal obligation

Some processing operations are necessary to comply with legal obligations, including:

  • tax retention obligations
  • DAC7
  • CDT
  • identification or reporting obligations
  • obligations towards supervisory or competent authorities
  • statutory record-keeping obligations
  • legal obligations relating to transport, tax, safety or compliance

5.3 Legitimate interest

We process personal data on the basis of legitimate interest for, among other things:

  • security of the Platform
  • fraud prevention
  • risk management
  • abuse detection
  • network integrity
  • disagreement handling
  • protection of Driv3, Users and Passengers
  • protection of Stripe and financial partners
  • system stability
  • improvement of services
  • product development
  • internal administration
  • evidentiary position in disagreements
  • support for community management
  • analysis of operational performance
  • business communication with Users

Where processing is based on legitimate interest, we weigh our interest against the privacy interests of data subjects.

5.4 Consent

We request consent separately, and only where required: for non-essential cookies and similar technologies, for marketing communication to persons who are not yet customers, and for optional functionalities that fall outside the performance of the contract. Consent may be withdrawn at any time via the settings in the Platform, the unsubscribe link or privacy@driv3.com. Withdrawal does not affect processing that lawfully took place before withdrawal.

5.5 Marketing and product communication

We may inform existing business Users, on the basis of our legitimate interest, about similar products, features and updates of Driv3 (article 11.7 of the Dutch Telecommunications Act). Every message contains an opt-out option; opting out is free of charge and is processed immediately. We send marketing to persons who are not customers only with prior consent. Operational messages about rides, payments, verification, account status, security and changes to terms are not marketing and cannot be switched off.

5.6 Overview per purpose

Purpose Legal basis (Article 6(1) GDPR) Retention period
Account, onboarding, subscription, authentication b – performance of the contract 2 years after termination of the account
Ride processing, dispatch, ETA, communication relating to rides b – performance of the contract 7 years (ride record, tax)
Location data during availability or a ride b and f – contract and legitimate interest; c for CDT Raw trail 12 months; ride-linked registration 7 years
Payments, Wallet, Treasury, cards, settlement b – performance of the contract; c – tax retention obligation 7 years
KYC/KYB, sanctions and risk checks c – legal obligation; b – Stripe requirements 5 years after the end of the relationship
Driving licence, permit and vehicle verification b – contract; f – safety and compliance As long as the account is active + 2 years
Fraud prevention, security, network integrity f – legitimate interest Logs 12 months; incident files 5 years after closure
DAC7 reporting and CDT registration c – legal obligation 7 years, or the statutorily prescribed period
Community functionalities and statistics b – performance of the contract; f – community management As long as membership lasts + 2 years
Support and communication b and f 2 years after closure of the request
Marketing to existing customers f – legitimate interest (with opt-out) Until opt-out or 2 years of inactivity
Marketing to non-customers, non-essential cookies a – consent Until withdrawal; proof of consent 2 years thereafter
Improvement of the Platform, AI support f – legitimate interest Aggregated or pseudonymised; identifiable data 12 months

Where we rely on legitimate interest, we have weighed our interest against the privacy interests of data subjects. Data subjects may object to these processing operations (section 13).

6. Sharing of personal data

We share personal data only where necessary for the performance of our services, legal obligations, payment processing, financial functionalities, compliance, security, support, community functionalities or other legitimate purposes.

Personal data may be shared with:

6.1 Stripe and financial parties

  • Stripe
  • Stripe-affiliated entities
  • Stripe’s financial partners
  • Stripe’s banking partners
  • payment partners
  • payment networks
  • card networks
  • external banks
  • parties required for Stripe Connect, Treasury, Financial Accounts, Financial Account IBAN, Wallet functionalities, top-ups, payouts, withdrawals, chargebacks, disputes, refunds, KYC/KYB, card functionalities, mutual payments or compliance

6.2 Technical service providers

  • hosting providers
  • cloud providers
  • data centres
  • software suppliers
  • monitoring services
  • security suppliers
  • database and infrastructure suppliers
  • communication services
  • support software
  • analytics and logging tools
  • map and routing providers
  • API providers
  • app stores

6.3 Verification, compliance and fraud prevention partners

  • KYC/KYB service providers
  • identity verification providers
  • RDW or linked registers
  • driving licence and authorisation verification partners
  • fraud prevention services
  • sanctions screening providers
  • risk assessment services
  • compliance providers

6.4 Government bodies and statutory reporting

  • Dutch Tax and Customs Administration (Belastingdienst)
  • tax authorities
  • supervisory authorities
  • law enforcement agencies
  • judicial authorities
  • parties involved in DAC7
  • parties involved in CDT
  • RDW or other registers, where necessary
  • other competent authorities where legally required

6.5 Professional advisers

Where necessary, data may be shared with:

  • lawyers
  • accountants
  • tax advisers
  • auditors
  • collection agencies
  • insurers
  • other professional advisers

6.6 Users among themselves

To the extent necessary for ride performance, dispatch, subcontracting, invoicing, the mutual forwarding fee, support, community functionalities or disagreement handling, certain data may be visible between the Users involved.

This may include, among other things:

  • name
  • company name
  • contact details
  • ride information
  • vehicle or driver information
  • fare information
  • location data
  • status information
  • community membership
  • community role
  • necessary invoice or payment information

Users who receive data of other Users or their customers via the Platform are required under article 17 of the Terms to use such data solely for the ride concerned, to keep it confidential and to delete it after completion.

6.7 Community Holders

To the extent necessary for community management, data may be visible to Community Holders, such as:

  • name
  • company name
  • role within the Community
  • ride information within the Community
  • participation or membership status
  • vehicle type
  • service level
  • relevant operational status
  • complaints or reports relating to the Community
  • Community Statistics, where available and permitted

Driv3 may determine whether data is displayed individually, in aggregated form, anonymised or in limited form.

We conclude a data processing agreement with processors in accordance with Article 28 GDPR. An up-to-date overview of our principal processors and sub-processors is available on request via privacy@driv3.com. Where a third party acts as an independent controller, that party’s own privacy terms additionally apply.

7. International transfers

Personal data are in principle processed within the European Economic Area (EEA). Our hosting and database environment is located in the EEA.

Some service providers process data (partly) outside the EEA. The most important is Stripe: Stripe Payments Europe, Ltd. (Ireland) may share data with Stripe, Inc. in the United States. This transfer takes place on the basis of the EU-US Data Privacy Framework and, additionally, the standard contractual clauses of the European Commission. For other suppliers (such as support, communication or AI services) we apply the same safeguards: an adequacy decision, standard contractual clauses with supplementary measures, or another valid transfer mechanism under Chapter V of the GDPR.

A copy of the safeguards applied can be requested via privacy@driv3.com.

8. Retention periods

We do not retain personal data longer than necessary for the purpose for which they were collected. The following periods apply, unless a statutory retention obligation, an ongoing disagreement, a fraud investigation or an instruction from a competent authority requires longer retention.

Data category Retention period Basis
Account data, roles, settings, acceptance logs 2 years after termination of the account Settlement of affairs, proof of acceptance (Terms, article 1.4)
Subscription, trial period and payment status data 7 years Statutory tax retention obligation (article 52 of the Dutch General Tax Act (AWR))
Ride data, Ride Orders, Account Rides, invoices 7 years Statutory tax retention obligation; CDT
Financial data: Wallet, Stripe transactions, payouts, set-offs, chargebacks 7 years Statutory tax retention obligation; DAC7
Location data: raw trail 12 months Handling of disagreements, fraud investigation
Location data: registration linked to a Ride Order 7 years as part of the ride record CDT, tax, evidence
KYC/KYB, sanctions and compliance data 5 years after the end of the relationship Stripe requirements; anti-money laundering legislation
Driving licence, driver card, permit, vehicle and inspection data As long as the account is active, thereafter 2 years Safety, compliance, evidence
Community data, memberships, statistics As long as the membership lasts, thereafter 2 years Community management, disagreements
Support, communication and complaint data 2 years after closure Quality, handling of disagreements
Technical logs, security logs, IP addresses 12 months Security, incident investigation
Fraud, abuse and incident files 5 years after closure of the file Protection of the Platform, Users, Stripe
Marketing data and preferences Until unsubscription or 2 years after the last interaction; proof of unsubscription 2 years Communication, evidence
Cookies and analytical data In accordance with the cookie settings; a maximum of 13 months Consent

After expiry of the retention period, data are deleted or anonymised. Deletion takes place automatically and periodically; back-ups are overwritten within 90 days thereafter.

9. Security

We take appropriate technical and organisational measures to protect personal data against loss, misuse, unauthorised access, alteration or disclosure.

These measures may include, among others:

  • access management
  • role-based authorisations
  • logging
  • monitoring
  • encryption where appropriate
  • secure connections
  • back-ups
  • incident procedures
  • restriction of access to financial data
  • restriction of access to KYC/KYB data
  • restriction of access to location data
  • restriction of access to community data
  • securing of accounts
  • internal procedures for handling personal data
  • agreements with suppliers

Although we take appropriate measures, no system can guarantee complete security. Users are themselves responsible for the secure use of their account, devices, passwords and access credentials.

10. AI support

The Platform may make use of AI-assisted systems for assistance, analysis, classification, summarisation, support, ticket prioritisation, onboarding assistance, fraud prevention, risk detection, operational signalling or improvement of services.

AI systems may, for example, be used for:

  • assistance with customer queries
  • analysis of support requests
  • prioritising tickets
  • supporting onboarding
  • recognising patterns
  • summarisation of conversations
  • signalling of risks
  • fraud prevention
  • operational signalling
  • improvement of documentation and support quality
  • assistance with internal assessment

AI systems do not take binding termination decisions without human review.

If a decision has significant consequences for a User, such as a prolonged block, termination or structural restriction of access, human review will take place insofar as legally required or reasonably appropriate.

We aim not to process more personal data in AI systems than is necessary for the purpose concerned.

We use AI services from external suppliers under a data processing agreement. Personal data that we submit to these services are not used to train the models of those suppliers. The suppliers concerned are listed in our overview of processors (section 6).

11. Automated decision-making and profiling

Driv3 may use automated systems for security, fraud prevention, risk management, transaction monitoring, account status, balance limits, top-up limits, provisional balance increases, reserves, card limits, community signals, onboarding status and compliance checks.

These systems work with a risk score based on transaction history, verification status, balance, previous chargebacks or reversals, deviations from the normal usage pattern and signals from Stripe. The possible consequence is a temporary restriction: a lower top-up or card limit, the non-provision or later provision of a provisional balance increase, a reserve or a temporary block of a functionality. A definitive termination or prolonged block is always reviewed by a member of staff.

These systems may give signals or temporarily restrict certain functionalities, for example in the event of:

  • suspicious transactions
  • deviating usage
  • negative balances
  • failed top-ups
  • increased chargeback risk
  • unusual card usage
  • incomplete KYC/KYB
  • compliance warnings
  • security risks
  • fraud risk
  • unusual community activity

Insofar as there is a solely automated decision with legal effects or similarly significant effects, the data subject has the rights that the GDPR provides for this, including the right to human intervention, to express his or her point of view and to contest the decision.

12. Cookies and similar technologies

The Platform and the website driv3.com use cookies, SDKs, local storage and similar technologies in three categories:

  • Necessary: login and session management, security, language selection and preferences, error detection. No consent is required for this; the retention period is a maximum of 12 months.
  • Analytical: usage statistics and performance, in order to improve the Platform. We request consent for this, unless the measurement is anonymised and has no consequences for the privacy of the visitor.
  • Marketing: only with consent and only on the website, not in the app.

On the first visit to the website we request consent via a cookie banner. The current overview of the cookies used, their purpose, retention period and the third parties involved can be found in the cookie settings on the website, where consent can also be adjusted or withdrawn. Cookies can additionally be deleted or blocked via the browser.

13. Rights of data subjects

Data subjects have, within the limits of the GDPR, the following rights:

  • access to the personal data we process about them
  • rectification of inaccurate or incomplete data
  • erasure ("right to be forgotten")
  • restriction of processing
  • portability of data they have provided themselves
  • objection to processing based on legitimate interest and to direct marketing
  • withdrawal of consent, where the processing is based on consent
  • not to be subject to solely automated decisions with legal effects, and the right to human intervention
  • to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens) (autoriteitpersoonsgegevens.nl)

Requests may be submitted via privacy@driv3.com or via the account settings in the Platform. We respond within one month of receipt. In the case of complex or numerous requests, we may extend this period by two months; we will inform the requester of this within the first month. Handling is free of charge, unless a request is manifestly unfounded or excessive.

To prevent misuse, we verify the identity of the requester, preferably via the logged-in account or the e-mail address known to us. We do not request a copy of an identity document, unless verification is not possible in any other way; in that case the passport photo, citizen service number (BSN) and document number may be redacted.

Some data cannot be erased immediately if we are required to retain it on the basis of legislation, tax obligations, DAC7, CDT, Stripe requirements, an ongoing disagreement, a fraud investigation or a payment dispute. In that case we will inform the requester which data is retained and why.

Requests from Passengers, Drivers or customers of a Carrier concerning data for which the Carrier is the controller (section 2) are forwarded by us to that Carrier and supported by us on the basis of the data processing agreement.

14. Data of passengers and business customers

The Platform may process personal data of Passengers, Business Customers and clients insofar as necessary for ride performance, administration, invoicing, communication, safety, disagreement handling, payment or legal obligations.

This may include, among other things:

  • name
  • contact details
  • pick-up and destination location
  • ride data
  • payment or invoice data
  • Tap to Pay, QR or Payment Link data
  • notes on rides
  • business customer information
  • complaints or support requests
  • account ride data
  • communication data

Carriers are themselves responsible for personal data of Passengers and customers that they process, export or use outside the Platform.

Driv3 processes passenger and customer data within the Platform for the purposes described in this Privacy Statement.

Driv3 makes a standard privacy text available that Carriers can show to their Passengers and Business Customers, for example in a booking confirmation or on their website. Passengers can exercise their rights with the Carrier that accepted the ride or via privacy@driv3.com.

15. Data of drivers and employees of users

If a Carrier, business, Community Holder or other User enters data of Drivers, dispatchers, employees or representatives into the Platform, that User must ensure that these persons have been properly informed about the processing of their personal data.

The User concerned remains responsible for the accuracy of the data entered by it, for having an appropriate legal basis for entering or using this data and for any processing of its own outside the Platform.

Driv3 makes a standard information text for Drivers and employees available for this purpose, which the Carrier can show during onboarding. This text describes in any event the processing of location data (section 3.5), driving licence and authorisation verification and the visibility of data within Communities.

Driv3 may process data of Drivers and employees for:

  • account management
  • ride performance
  • dispatch
  • planning
  • roles and permissions
  • verification
  • driving licence and authorisation verification
  • GPS functionalities
  • safety
  • communication
  • payment or administrative processing
  • community functionalities
  • compliance
  • support
  • disagreement handling

16. Data within communities

If a User participates in a Community, certain data may be visible to the Community Holder or other community members involved, depending on the functionality, settings, roles and permissions.

This may include, among other things:

  • name
  • business name
  • role within the Community
  • participation status
  • ride data within the Community
  • vehicle type
  • service level
  • availability
  • status information
  • relevant complaints or reports
  • Community Statistics

The Community Holder is itself responsible for its own Community Rules, its own communication and personal data that it processes, exports or uses outside the Platform.

Driv3 may restrict, aggregate, anonymise or withhold Community Statistics where this is necessary for reasons of privacy, commercial sensitivity, legislation, technical limitations or other reasonable grounds.

Community Holders and community members who see data of others through the community are bound by confidentiality under article 17 of the Terms.

17. Minors

The Platform is not intended for use by minors as professional Users.

We do not knowingly process personal data of minors as Users of the Platform, unless this is necessary for a specific ride, passenger situation or legal obligation and the processing takes place lawfully.

18. Amendments

We may amend this Privacy Statement where necessary due to:

  • changes to the Platform
  • introduction or modification of Stripe Connect
  • introduction or modification of Stripe Treasury
  • introduction or modification of Stripe Financial Accounts
  • new Wallet functionalities
  • new payment methods
  • new card functionalities
  • new community functionalities
  • new AI functionalities
  • new verification or RDW functionalities
  • new legal obligations
  • product development
  • security
  • compliance
  • operational changes

The most recent version is always available via the Platform.

In the case of material amendments, we may inform Users by e-mail, platform notification or another appropriate means.

We retain earlier versions of this Privacy Statement, and they are available on request via privacy@driv3.com.

19. Contact

For questions about this Privacy Statement, the processing of personal data or the exercise of rights:

020 Service Beheer B.V. · trading as Driv3 · Prins Mauritslaan 37, 1171 LP Badhoevedorp · Chamber of Commerce (KvK) 57750173 · privacy@driv3.com

Data subjects also have the right to lodge a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens), Postbus 93374, 2509 AJ Den Haag, autoriteitpersoonsgegevens.nl.

20. Version and language

This is version 1.0 of the Driv3 Privacy Statement, adopted on 10 October 2026 and effective from that date. The current version can always be consulted via the Platform and via driv3.com.

This Privacy Statement has been drawn up in Dutch. Driv3 may make translations available. In the event of a difference in interpretation or a conflict between the Dutch text and a translation, the Dutch text prevails.

↑
© 2026 020 Service Beheer B.V. (Driv3) · Version 1.0 · This is a translation. The Dutch text prevails over any translation (section 20).