Version 6
Date: 21 July 2026
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.
020 Service Beheer B.V.
Trade name: Driv3
Address: Prins Mauritslaan 37 2A.06
Postal code and city: 1171LP Badhoevedorp
Chamber of Commerce: 57750173
Email: info@driv3.com
In this privacy policy, 020 Service Beheer B.V., trading under the name Driv3, is referred to as “Driv3”, “we”, “us” or “the Platform”.
This privacy policy explains which personal data we process, why we do so, with whom we may share data, how long we retain data and which rights data subjects have.
Driv3 has not currently appointed a data protection officer, unless stated otherwise at a later date via the Platform or this privacy policy.
2. Our role under the GDPR
Driv3 is an independent controller for personal data processed in the context of the use of the Platform, unless expressly agreed otherwise or unless the nature of a specific data flow requires otherwise.
We process personal data for, among other things:
· account registration and account management;
· user onboarding;
· trial periods and subscriptions;
· ride administration;
· dispatch and operational processing;
· GPS and location functionalities;
· payment processing via Stripe Connect;
· use of Stripe Treasury;
· use of Stripe Financial Accounts;
· wallet functionalities;
· balance display;
· Financial Account IBAN;
· top-ups;
· provisional balance increases;
· refunds and payouts to external bank accounts;
· reserves and balance holds;
· subscription costs;
· network fee;
· mutual forwarding fee;
· Stripe costs;
· passenger payments;
· Tap to Pay;
· QR payments;
· Payment Links;
· card payments;
· Issuing Cards / Debit Cards;
· card spend;
· mutual payments;
· account rides;
· community functionalities;
· community membership;
· community rules;
· community statistics;
· KYC/KYB and verification;
· driving licence and authorisation verification;
· RDW checks or checks through connected registers;
· safety and incident handling;
· fraud prevention;
· risk management;
· compliance;
· support;
· marketing and product communication;
· AI support;
· dispute handling;
· compliance with legal obligations, including DAC7 and CDT.
Carriers, community holders and other users may be independent controllers for personal data that they process, export, store or use outside the Platform.
Users who enter personal data of drivers, employees, passengers, business customers, clients or other data subjects into the Platform remain responsible for the accuracy of that data and for their own information obligations towards those persons, insofar as that responsibility rests with them under the GDPR or other applicable law.
There is no joint controllership between Driv3 and users, carriers or community holders, unless expressly agreed in writing.
For specific data flows, the division of roles between Driv3, users, carriers, community holders, Stripe or other parties may differ. If and insofar as Driv3 acts as a processor within the meaning of the GDPR in a specific data flow, separate processor terms or a data processing agreement may apply.
Stripe, financial partners, banking partners, verification partners and other third parties may, depending on the relevant processing, act as independent controllers or as processors. Processing by these parties may also be subject to their own privacy policies and terms.
If business users, carriers or community holders export personal data from the Platform, store it outside the Platform, combine it with their own systems or use it for their own purposes, they are responsible for the lawfulness, security, retention periods, information obligations and further processing of that data.
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 details
· name;
· address;
· email address;
· telephone number;
· date of birth, if required for verification;
· language preference;
· contact preferences;
· communication data;
· user ID;
· customer or account number;
· representative details.
3.2 Business and professional data
· company name;
· trade name;
· Chamber of Commerce number;
· VAT number;
· business address;
· business contact details;
· legal form;
· data of directors, representatives or ultimate beneficial owners, if required;
· licence data;
· driver card data;
· vehicle data;
· vehicle type;
· vehicle class;
· insurance data;
· inspection data;
· 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
· pickup and destination location;
· ride time;
· ride status;
· ride price;
· tariff data;
· vehicle type;
· vehicle class;
· service level;
· payment method;
· passenger information insofar as necessary;
· client or corporate customer;
· community holder, if applicable;
· assigned driver or carrier;
· ride notes;
· route data;
· dispatch data;
· invoice and administration 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
We may process location data, including GPS data, during active rides, operational processes, dispatch, community functionalities or other functionalities for which location data is necessary.
Location data are processed only for, among other things:
· performance of rides;
· dispatch;
· ETA and route information;
· safety;
· operational coordination;
· route and status information;
· communication with passengers, clients, dispatchers, carriers or community holders;
· evidence;
· dispute handling;
· incident investigation;
· fraud prevention;
· legal obligations;
· service improvement.
GPS location data may, insofar as necessary for the operation of the Platform, be shared with involved drivers, carriers, dispatchers, clients, community holders, passengers or support staff.
We do not process location data for longer than necessary for the relevant purpose, unless longer retention is required due to legal obligations, administration, disputes, fraud investigation, safety incidents or evidentiary purposes.
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;
· refunds to external bank accounts;
· 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 details;
· 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 to restrict, block or activate financial functionalities.
Insofar as identity documents or data from such documents are processed, this is done only insofar as 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;
· expiry date;
· driver card data;
· authorisation status;
· RDW data;
· data from connected registers;
· verification results;
· inspection data;
· vehicle data;
· licence data;
· approval or rejection status.
These 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, if available;
· community statistics.
Community statistics may relate to ride volume, peak hours, average ride prices, availability, acceptance, operational performance or other data.
Community statistics may be displayed individually, aggregated, anonymised or limited, depending on functionality, settings, role, rights, privacy, commercial sensitivity, law 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;
· pickup and destination location;
· ride data;
· payment data;
· invoice data;
· ride notes;
· business customer information;
· complaints;
· support requests;
· communication data;
· ride performance preferences, if necessary.
Carriers remain 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:
· emails;
· chats;
· WhatsApp messages, if used;
· support tickets;
· telephone calls or call notes;
· complaints;
· incident reports;
· technical reports;
· feedback;
· internal notes relating to support, compliance or disputes;
· reports about fraud, misuse, customer relationships or community disputes.
3.12 Marketing, communication and preference data
We may process data for communication and marketing, including:
· email address;
· telephone number;
· name;
· company name;
· communication status;
· preferences;
· consent or unsubscribe status;
· interaction with emails 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 service. Marketing communication 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 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. More information may be included in a separate cookie policy.
4. Purposes of processing
We process personal data only for legitimate, clear and necessary purposes.
Personal data are processed for:
4.1 Service provision and account management
· creating and managing accounts;
· user onboarding;
· managing the trial period;
· managing subscriptions;
· assigning roles and rights;
· authentication and secure access;
· managing user profiles;
· communication about the Platform;
· recording acceptance of terms;
· managing 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 involved users;
· communication with passengers or clients;
· ride administration;
· invoicing;
· account rides;
· community rides;
· complaint and dispute handling.
4.3 Payment processing and financial administration
· processing payments;
· facilitating Stripe Connect;
· facilitating Stripe Treasury;
· facilitating Stripe Financial Accounts;
· processing Financial Account IBAN;
· displaying wallet balances;
· processing top-ups;
· processing provisional balance increases;
· processing refunds to external bank accounts and payouts;
· processing subscription costs;
· processing network fee;
· processing 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;
· passing on and settling 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 through connected registers;
· bank account verification;
· compliance with requirements of Stripe, financial partners and law;
· sanctions screening;
· fraud prevention;
· misuse detection;
· risk assessment;
· monitoring 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 rights;
· displaying or applying community rules;
· admission and removal within Communities;
· communication within or about Communities;
· processing community rides;
· processing community settings;
· displaying community dashboards;
· displaying community statistics;
· processing community-related payments, if available;
· supporting community management.
4.6 Safety and incident handling
· security of the Platform;
· detection of misuse;
· investigation of incidents;
· prevention of fraud;
· protection of accounts;
· prevention of unauthorised access;
· logging and monitoring;
· handling security reports;
· investigation of suspicious transactions;
· investigation of account compromise;
· protection of the network.
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.
4.8 Support and communication
· answering questions;
· handling complaints;
· solving 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 for community questions.
4.9 Marketing and product communication
· sending product updates;
· informing about new functions;
· informing about offers or promotions;
· sending newsletters;
· improving onboarding;
· inviting feedback;
· measuring interest in products or functions;
· customer relationship management.
For marketing communication for which consent or an opt-out option is required, we apply the relevant rules.
4.10 Improvement of the Platform
· usage analysis;
· improvement of functionalities;
· improvement of safety;
· 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 are not sold to third parties.
5. Legal bases
We process personal data only where there is a valid legal basis.
5.1 Performance of the agreement
Many processing activities are necessary for the performance of the agreement 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 activities are necessary to comply with legal obligations, including:
· tax retention obligations;
· DAC7;
· CDT;
· identification or reporting obligations;
· obligations towards regulators or competent authorities;
· statutory administration 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;
· misuse detection;
· network integrity;
· dispute 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 disputes;
· community management support;
· analysis of operational performance;
· business communication with users.
When processing on the basis of legitimate interest, we balance our interest against the privacy interests of data subjects.
5.4 Consent
If consent is required, for example for certain cookies, marketing communication, optional analytical technologies or certain location functionalities, we request this separately.
Consent may be withdrawn at any time. Withdrawal does not affect processing that lawfully took place before withdrawal.
6. Sharing personal data
We share personal data only if necessary for the performance of our services, legal obligations, payment processing, financial functionalities, compliance, safety, 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, refunds to external bank accounts, 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 route providers;
· API providers;
· app stores.
6.3 Verification, compliance and fraud prevention partners
· KYC/KYB service providers;
· identity verification providers;
· RDW or connected registers;
· driving licence and authorisation verification partners;
· fraud prevention services;
· sanctions screening providers;
· risk assessment services;
· compliance providers.
6.4 Government authorities and statutory reporting
· Dutch Tax Authority;
· tax authorities;
· regulators;
· investigative authorities;
· courts;
· parties involved in DAC7;
· parties involved in CDT;
· RDW or other registers, if necessary;
· other competent authorities if legally required.
6.5 Professional advisers
If necessary, data may be shared with:
· lawyers;
· accountants;
· tax advisers;
· auditors;
· debt collection parties;
· insurers;
· other professional advisers.
6.6 Users among themselves
Insofar as necessary for ride performance, dispatch, subcontracting, invoicing, mutual forwarding fee, support, community functionalities or dispute handling, certain data may be visible between involved users.
This may include:
· name;
· company name;
· contact details;
· ride information;
· vehicle or driver information;
· tariff information;
· location data;
· status information;
· community membership;
· community role;
· necessary invoice or payment information.
6.7 Community holders
Insofar as 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 connected to the Community;
· community statistics, insofar as available and permitted.
Driv3 may determine whether data are displayed individually, aggregated, anonymised or limited.
Where required, appropriate contractual arrangements are made with processors. If a third party acts as an independent controller, that party may have its own privacy terms and responsibilities.
7. International transfers
Personal data may be processed within and outside the European Economic Area.
If personal data are processed outside the European Economic Area, this will take place only where appropriate safeguards exist in accordance with the GDPR.
These safeguards may include:
· standard contractual clauses;
· adequacy decisions;
· additional technical and organisational measures;
· other valid transfer mechanisms under the GDPR.
Service providers such as Stripe, cloud providers, technical suppliers, support services or analytics providers may use international group companies or subprocessors. We take reasonable measures to ensure that international transfers take place lawfully.
8. Retention periods
We do not retain personal data longer than necessary for the purposes for which they were collected, unless a longer retention period is legally required or justified.
8.1 Account data
Account data are retained for as long as the account is active and thereafter for as long as necessary for administration, disputes, compliance, tax obligations, fraud investigation, legal obligations or evidentiary purposes.
8.2 Subscription and trial period data
Data relating to trial periods, subscriptions, payment status, cancellations, invoices and payment arrears are retained for as long as necessary for performance of the agreement, administration, invoicing, disputes, tax obligations and evidence.
8.3 Ride data
Ride data are retained for as long as necessary for ride administration, invoicing, complaints, disputes, account rides, tax obligations, CDT, DAC7, safety and statutory retention obligations.
8.4 Financial data
Financial data, including payment data, wallet data, Stripe Connect data, Treasury data, Financial Account data, Financial Account IBAN, top-ups, payouts, provisional balance increases, reserves, Stripe costs, network fees, mutual forwarding fees, mutual payments, card spend, chargebacks, disputes, refunds and corrections, are retained for as long as necessary for financial administration, tax reporting, audit trails, compliance, disputes, risk management and legal obligations.
8.5 Tax and administrative data
Tax and administrative data are retained in accordance with the statutory retention obligation, in principle for a maximum of 7 years, unless law, disputes, audits, compliance obligations or other legitimate reasons require a longer retention period.
8.6 KYC/KYB and compliance data
KYC/KYB, verification and compliance data are retained for as long as necessary for onboarding, verification, legal obligations, Stripe requirements, fraud prevention, risk management, disputes or compliance.
8.7 Driving licence, authorisation and register data
Driving licence, authorisation, RDW, register, inspection and verification data are retained for as long as necessary for safety, compliance, access management, ride functionalities, legal obligations, disputes, fraud prevention or evidence.
8.8 Location data
Location data are not retained for longer than necessary for ride performance, dispatch, ETA, safety, dispute handling, administration, fraud investigation, evidence or legal obligations.
8.9 Community data
Community data, including community membership, community roles, community settings, community rides, community statistics and community-related reports, are retained for as long as necessary for community functionalities, administration, disputes, safety, network integrity, compliance or legal obligations.
8.10 Support and communication data
Support and communication data are retained for as long as necessary for support, quality control, dispute handling, evidence, safety or service improvement.
8.11 Marketing data
Marketing data are retained for as long as necessary for communication, customer relationship management, proof of consent or unsubscribe status, product updates and commercial communication, unless the data subject unsubscribes or objects and there is no other legal basis for retention.
8.12 Fraud prevention and incident data
Data relating to fraud, misuse, incidents, security or disputes may be retained longer if necessary for the protection of Driv3, users, passengers, Stripe, financial partners or the network.
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:
· access control;
· role-based authorisations;
· logging;
· monitoring;
· encryption where appropriate;
· secure connections;
· backups;
· 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;
· account security;
· internal procedures for handling personal data;
· arrangements with suppliers.
Although we take appropriate measures, no system can guarantee complete security. Users are responsible for secure use of their account, devices, passwords and access credentials.
10. AI support
The Platform may use AI-assisted systems for support, analysis, classification, summarisation, support, ticket priority, onboarding support, fraud prevention, risk detection, operational signalling or service improvement.
AI systems may be used, for example, for:
· support with customer questions;
· analysis of support requests;
· prioritising tickets;
· supporting onboarding;
· recognising patterns;
· summarising conversations;
· signalling risks;
· fraud prevention;
· operational signalling;
· improving documentation and support quality;
· supporting internal assessment.
AI systems do not make binding termination decisions without human review.
If a decision has significant consequences for a user, such as a long-term block, termination or structural limitation 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 necessary for the relevant purpose.
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 may generate signals or temporarily limit certain functionalities, for example in case of:
· suspicious transactions;
· unusual use;
· negative balances;
· failed top-ups;
· increased chargeback risk;
· unusual card use;
· 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 provided by the GDPR, including the right to human intervention, to express their point of view and to contest the decision.
12. Cookies and comparable technologies
The Platform and website may use cookies, SDKs, pixels, local storage or comparable technologies.
These technologies may be used for:
· necessary operation of the Platform;
· security;
· login and session management;
· preferences;
· analytics;
· debugging;
· improvement of functionalities;
· marketing, if applicable and permitted.
For non-essential cookies or comparable technologies for which consent is required, we request consent via a cookie banner or comparable method.
Users can adjust cookie settings via the available settings or through their browser.
More information may be included in a separate cookie policy.
13. Rights of data subjects
Data subjects have, within the limits of the GDPR, the following rights:
· right of access;
· right to rectification;
· right to erasure;
· right to restriction of processing;
· right to data portability;
· right to object;
· right to withdraw consent, if processing is based on consent;
· right not to be subject to certain solely automated decisions;
· right to lodge a complaint with the Dutch Data Protection Authority.
Requests may be submitted via:
We may request additional information to verify the identity of the requester.
Some data cannot be deleted immediately if we are required to retain them under law, tax obligations, DAC7, CDT, compliance obligations, Stripe requirements, disputes, fraud investigation, security, payment disputes, chargebacks, refunds, disputes or other legitimate grounds.
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, dispute handling, payment or legal obligations.
This may include:
· name;
· contact details;
· pickup and destination location;
· ride data;
· payment or invoice data;
· Tap to Pay, QR or Payment Link data;
· ride notes;
· business customer information;
· complaints or support requests;
· account ride data;
· communication data.
Carriers are 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 policy.
15. Data of drivers and employees of users
If a carrier, company, community holder or other user enters data of drivers, dispatchers, employees or representatives into the Platform, that user must ensure that these persons are properly informed about the processing of their personal data.
The relevant user remains responsible for the accuracy of the data entered by that user, for having an appropriate legal basis for entering or using such data and for any own processing outside the Platform.
Driv3 may process data of drivers and employees for:
· account management;
· ride performance;
· dispatch;
· planning;
· roles and rights;
· verification;
· driving licence and authorisation verification;
· GPS functionalities;
· safety;
· communication;
· payment or administrative processing;
· community functionalities;
· compliance;
· support;
· dispute handling.
16. Data within Communities
If a user participates in a Community, certain data may be visible to the community holder or other involved community members, depending on the functionality, settings, roles and rights.
This may include:
· name;
· company 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 responsible for its own community rules, own communication and personal data that it processes, exports or uses outside the Platform.
Driv3 may limit, aggregate, anonymise or not display community statistics if necessary due to privacy, commercial sensitivity, law, technical limitations or other reasonable grounds.
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. Changes
We may amend this privacy policy if necessary due to:
· changes to the Platform;
· introduction or change of Stripe Connect;
· introduction or change of Stripe Treasury;
· introduction or change 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 current version is always available via the Platform.
In case of material changes, we may inform users by email, platform notification or another appropriate method.
19. Contact
For questions about this privacy policy or the processing of personal data, please contact:
020 Service Beheer B.V.
Trade name: Driv3
Address: Prins Mauritslaan 37 2A.06
Postal code and city: 1171LP Badhoevedorp
Chamber of Commerce: 57750173
Email: info@driv3.com
Data subjects also have the right to lodge a complaint with the Dutch Data Protection Authority.
