Driv3 General Terms and Conditions
- Applicability, acceptance and definitions
- Platform role and autonomy
- Stripe Connect, Treasury, Financial Accounts and payment processing
- Ride structure, forwarding and rates
- Subscriptions, network fee, mutual forwarding fee, Stripe costs, reserves and set-off
- Liability, indemnity and security
- Suspension and termination
- Licences, insurance, inspections and verification
- Data protection and privacy
- Business customer relationships, account rides and invoicing
- Intellectual property, software, GPS, dashboards, communities and financial functionalities
- Anti-circumvention and network integrity
- Amendment of terms
- Tax reporting (DAC7)
- Central Taxi Transport Database (CDT)
- Force majeure
- Confidentiality
- Final provisions
These Terms apply to any use of the Driv3 platform by Carriers, Drivers, Community Holders and other business Users. Read them in full before activating an account.
1. Applicability, acceptance and definitions
1.1 Driv3
These Terms are used by 020 Service Beheer B.V., trading under the name Driv3, with its registered office at Prins Mauritslaan 37, 1171 LP Badhoevedorp, registered in the Trade Register of the Chamber of Commerce (KvK) under number 57750173, reachable via info@driv3.com (hereinafter: "Driv3").
1.2 Applicability
These Terms apply to every use of the Platform, including registration, onboarding, trial use, account activation, ride processing, community use, payment processing, Wallet functionalities, Stripe Connect, Stripe Treasury, Stripe Financial Accounts, subscriptions, network fees and other services of Driv3.
1.3 Acceptance
By registering, accepting digitally, ticking a declaration of agreement, starting onboarding, using the Platform, activating an account, using financial functionalities or continuing to use the Platform after an amendment of these Terms, the User accepts these Terms.
If a User does not agree to these Terms, the User may not use the Platform.
1.4 Proof of acceptance
Driv3 may record proof of acceptance, including date, time, account ID, user ID, IP address, e-mail address, device data, version of the Terms and method of acceptance.
1.5 Representation
If a User acts on behalf of a business, Carrier, Community, client or other legal entity, that User declares to be authorised to bind that party to these Terms.
1.6 Definitions
In these Terms, the following capitalised terms have the meaning set out after them. Terms in the singular also include the plural and vice versa. "In writing" also includes by e-mail or via a functionality in the Platform intended for that purpose.
- Platform
- the digital infrastructure operated by 020 Service Beheer B.V., trading under the name Driv3, for the distribution, administration and processing of rides within the transport industry, including software, portals, Wallet display, dispatch functionality, payment functionality, financial account functionality, community functionalities and other supporting services.
- Driv3
- 020 Service Beheer B.V., trading under the name Driv3, being the operator of the Platform.
- Carrier
- any natural person or legal entity that offers, performs, receives, forwards or administratively processes transport services via the Platform.
- Driver
- natural person who performs a ride, independently or under the responsibility of a Carrier.
- User
- any Carrier, Driver, business, contractor, dispatcher, admin, employee, Community Holder or other natural person or legal entity that uses the Platform.
- Passenger
- end customer for whom a ride is performed.
- Business Customer
- Business Customer of a Carrier, including businesses, hotels, institutions, organisations or other business clients.
- Ride Order
- a transport request registered, received, planned, forwarded, accepted or performed via the Platform.
- Direct Ride
- a ride in which the performing Carrier enters into the transport agreement directly with the Passenger or client.
- Regular Customer / Subcontracting Ride
- a ride performed for a regular customer or client of another Carrier, where the original Carrier remains the contracting party towards its customer and the performing Carrier acts as an independent subcontractor.
- Account Ride
- a ride performed on account, by invoice or on deferred payment, where payment, approval and payout may depend on the relevant Carrier, client, Business Customer, contractual arrangements, payment term and administrative processing.
- Stripe
- Stripe Payments Europe, Ltd., Stripe Technology Europe, Ltd., Stripe, Inc., entities affiliated with Stripe, Stripe’s financial partners, banking partners, payment partners and/or other service providers engaged by Stripe, insofar as applicable to the functionalities used.
- Stripe Connect
- the payment infrastructure of Stripe with which individual Connected Accounts can be created, managed and linked to the Platform.
- Stripe Connected Account
- the account of a User created or managed by Stripe within the Stripe Connect environment, including a Custom Connected Account, which is used for onboarding, verification, payment processing, access to Stripe functionalities, compliance checks and any link with Treasury functionalities.
- Custom Connected Account
- a Stripe Connected Account in which the Platform fulfils a technical and administrative role in onboarding, data collection, user interface, support and risk management, insofar as permitted and required by Stripe.
- Stripe Treasury
- the financial infrastructure offered or facilitated by Stripe with which, if available and approved, Financial Accounts, balances, top-ups, transfers, reserves, payouts, money movement, card functionalities and related financial functionalities can be used.
- Stripe Financial Account
- the additional financial account functionality which, if available in the relevant country and after approval by Stripe, can be linked to a Stripe Connected Account of a User and with which balances can be held, received, transferred, reserved, set off or paid out via Stripe Treasury or comparable Stripe functionality.
- Financial Account IBAN
- an IBAN, account number or comparable payment identifier that may be made available by Stripe or a financial partner in connection with a Stripe Financial Account. A Financial Account IBAN is not issued by Driv3 itself.
- Wallet
- the display within the Platform of balances, transactions, reserves, subscription costs, network fees, mutual forwarding fees, Stripe costs, corrections, payouts and other financial movements relating to the Stripe Connected Account and/or the Stripe Financial Account of the User. The Wallet is a technical and administrative user interface and not an independent bank account or payment account of Driv3.
- Balance
- the amount shown within the Wallet, the Stripe Connected Account, the Stripe Financial Account or a related administrative display as available, reserved, pending, blocked, processed or settled.
- Available Balance
- the part of the balance that, according to the data of Stripe and the Platform available at that time, is not reserved, blocked, pending, contested or subject to compliance, risk or technical restrictions.
- Reserved Balance
- the part of the balance that is temporarily or structurally reserved, blocked or made unavailable for, among other things, subscription costs, network fees, mutual forwarding fees, Stripe costs, chargebacks, refunds, disputes, reversals, negative balances, corrections, fraud prevention, risk management, network integrity or other obligations.
- Top-up
- the adding of funds to a Stripe Financial Account, Wallet or comparable financial functionality via Stripe, for example from an external bank account, iDEAL, Wero or another payment method supported by Stripe.
- Provisional Balance Increase
- a conditional and revocable credit or making available of balance permitted by Driv3 on the basis of a payment confirmation, authorisation, webhook, status notification or other technical signal, before the underlying funds have been definitively received, settled or released by Stripe, a bank, payment method or financial partner.
- Withdrawal / Payout
- the transfer of funds from a Stripe Financial Account, Wallet or other Stripe functionality to an external bank account or other destination supported by Stripe.
- Settlement
- the processing, settlement and making available of funds by Stripe, banks, payment methods, card networks, financial partners or other parties involved.
- Subscription
- the periodic agreement for access to the Platform, certain functionalities, modules or services of Driv3.
- Trial Period
- the period during which a User can temporarily use or explore the Platform before the paid subscription commences, under the conditions and restrictions determined by Driv3.
- Subscription Costs
- the fixed or periodic fee owed by the User for access to the Platform, as shown in the Platform, offer, price list, agreement or other communication of Driv3.
- Mutual Forwarding Fee
- the fee that Users may agree among themselves when forwarding, organising, making available or performing rides. If Users refer to this in practice as commission, this is understood within these Terms as mutual forwarding fee.
- Network Fee
- the fee that Driv3 charges on the mutual forwarding fee for facilitating the network, administration, dispatch, wallet, payment and settlement functionality around ride forwarding. The network fee is calculated exclusively on the mutual forwarding fee and not on the full ride amount.
- Stripe Costs
- all costs, commissions, transaction costs, payment method costs, credit card costs, iDEAL costs, Wero costs, dispute fees, chargeback costs, refund costs, Connect costs, Treasury costs, Financial Account costs, payout costs, transfer costs, card costs, compliance costs, currency costs, product costs or other costs that Stripe or a third party charges in connection with the use of the Platform, Stripe or financial functionalities.
- Chargeback
- a reversal or contestation of a payment by a cardholder, Passenger, bank, card issuer, payment method, card network or other party.
- Dispute
- a contestation, disagreement or investigation relating to a payment, transaction, chargeback, refund, payout or other financial movement.
- Refund
- a full or partial repayment to a Passenger, customer, client, User or other payer.
- Tap to Pay
- a payment functionality with which a Passenger or customer can pay contactlessly via a suitable device.
- QR Payment
- a payment that is initiated via a QR code or comparable payment code.
- Payment Link
- a payment link with which a Passenger, customer or client can make a payment.
- Issuing Card / Debit Card
- a physical or virtual card that may be made available to a User via Stripe, Stripe Issuing, Stripe Treasury, a Stripe Financial Account or comparable financial functionality, insofar as supported and approved by Stripe.
- Card Spend
- a payment, withdrawal, reserve or other transaction with an Issuing Card / Debit Card.
- Dashboard
- a digital environment within the Platform in which Users can view information on, among other things, rides, balances, payments, statistics, Community, performance, settings, notifications and administration.
- Community
- a group within the Platform managed by a User, Carrier, taxi company, business or organisation in which rides, Drivers, Carriers, clients, conditions, quality requirements and operational arrangements can be organised.
- Community Holder
- the User who creates, manages or has managed a Community and is responsible for admission, removal, Community Rules, quality requirements, communication, customer relations and mutual arrangements within that Community.
- Community Rules
- the rules, conditions, quality requirements, rules of conduct, dress codes, vehicle requirements, service levels, admission criteria or other arrangements established by a Community Holder that apply within a Community.
- Community Statistics
- data, dashboards or analyses regarding a Community, such as ride volume, peak hours, average ride price, availability, performance or other operational data, insofar as made available by Driv3.
- Mutual Payment
- a payment, bank transfer or transfer between Users via Wallet, Stripe Financial Account or other available financial functionality.
- Tip / Gratuity
- a voluntary additional amount given by a Passenger, customer or client on top of the ride price or payment and intended for the performing Driver, unless expressly indicated otherwise or otherwise required by law or contract.
- Driving Licence and Authorisation Verification
- the checking of driving licence data, driver data, permits, authorisations or other relevant data via RDW, linked registers, verification partners or documentation supplied by the User.
- KYC / KYB
- Know Your Customer and Know Your Business processes, including identification, verification, business checks, compliance checks, sanctions screening, risk assessment and other checks required by Stripe, Driv3, financial partners or legislation.
- CDT
- the Central Taxi Transport Database (Centrale Database Taxivervoer) as referred to in the Passenger Transport Act 2000 (Wet personenvervoer 2000) and the Passenger Transport Decree 2000 (Besluit personenvervoer 2000), including successor or comparable statutory registration systems for taxi transport.
- DAC7
- Directive (EU) 2021/514 on the automatic exchange of information by platform operators, implemented in the Netherlands in the Act implementing the EU Directive on the exchange of information in the digital platform economy (Wet implementatie EU-richtlijn gegevensuitwisseling digitale platformeconomie), including successor regulations.
- Confidential Information
- all non-public information that a User obtains via or in connection with the Platform, as further described in article 17.1.
- Terms
- these Terms of Driv3, including the definitions and any annexes.
2. Platform role and autonomy
2.1 Infrastructure function
The Platform exclusively facilitates a technological, administrative and financial infrastructure for supply and demand within the transport industry.
The Platform:
- does not itself perform passenger transport
- is not a party to transport agreements between Passengers, Business Customers, Carriers or Drivers
- is not an employer of Drivers
- does not act as main contractor of transport services
- does not guarantee any minimum turnover, ride volume, occupancy rate, income or profit
- does not independently determine whether a User must accept rides
- does not oblige Users to use the Platform exclusively
- is not responsible for internal Community Rules, community arrangements or community disagreements
2.2 Independence
Carriers and Drivers operate as independent entrepreneurs or under their own employer responsibility.
Carriers independently determine:
- their availability
- their rates
- their customers
- their region
- their working methods
- their internal organisation
- the manner in which they perform their services
- their participation in Communities
- their acceptance of Account Rides or rides from certain clients
The Platform does not oblige Users to accept Ride Orders and does not apply any minimum purchase obligation.
Roles within the Platform do not qualify as a legal hierarchy and do not create a relationship of authority within the meaning of employment law.
2.3 No transport guarantee
Driv3 does not guarantee that a User will receive rides, be able to forward rides, be able to perform rides or be able to generate income via the Platform. Any examples, simulations, dashboards, statistics or projections are indicative and do not constitute a guarantee.
2.4 No exclusivity
Joining the Platform does not create an exclusive relationship. Users remain free to operate outside the Platform, subject to the provisions on anti-circumvention, network integrity, customer relations, confidential information and the correct settlement of obligations arising via the Platform.
2.5 Business use
The Platform is intended exclusively for professional and business use by Carriers, Drivers, businesses, contractors, Community Holders and other business Users within the transport industry.
By registering for or using the Platform, the User declares to be acting in the course of a profession, business or independent activity and not as a consumer.
Insofar as a User would nevertheless qualify as a consumer, mandatory consumer rights remain unaffected, but this does not give rise to any right to use the Platform in breach of these Terms, Stripe terms, verification requirements or safety and compliance requirements.
3. Stripe Connect, Treasury, Financial Accounts and payment processing
3.1 Stripe infrastructure
The Platform uses Stripe Connect, Stripe Treasury and related Stripe functionalities for, among other things, payment processing, onboarding, verification, balance display, Wallet functionality, reserves, settlements and set-offs, top-ups, payouts, transfers, corrections, Tap to Pay, QR Payments, Payment Links, card payments, Issuing Cards / Debit Cards, card spend and other financial functionalities.
Driv3 may technically integrate Stripe functionalities into the Platform and may, through the available Stripe functionalities, give instructions, apply reserves, carry out set-offs or process financial mutations to the extent permitted by Stripe, the User and applicable legislation.
The underlying financial infrastructure is provided by Stripe and/or by financial partners, banking partners, payment partners or other third parties engaged by Stripe.
Costs charged by Stripe to Driv3 or to the Platform account in connection with use by a User may be passed on, invoiced, reserved or set off by Driv3 against the User concerned in accordance with Article 5.
3.2 Stripe Connected Account as base layer
A Stripe Connected Account, including a Custom Connected Account, may be created for every User.
The Stripe Connected Account forms the basis for:
- onboarding
- KYC/KYB
- verification
- account status
- payment processing
- access to Stripe functionalities
- compliance checks
- linking with any Treasury functionalities
- linking with a Stripe Financial Account where available and approved
- linking with card functionalities where available and approved
The User is obliged to provide all information required for creating, activating, maintaining and using the Stripe Connected Account.
3.3 Stripe Financial Account / Treasury as additional layer
Where available in the relevant country, for the relevant type of User and after approval by Stripe, a Stripe Financial Account or comparable Treasury functionality may be linked to a User's Stripe Connected Account.
The Stripe Financial Account forms an additional financial layer on top of the Stripe Connected Account.
Through this functionality, to the extent supported by Stripe and activated by Driv3, among other things:
- balances may be held
- amounts may be received
- top-ups may be carried out
- amounts may be withdrawn to an external bank account
- amounts may be transferred
- amounts may be reserved
- subscription costs may be set off
- network fees may be set off
- mutual forwarding fees may be set off
- Stripe costs may be set off
- corrections may be processed
- chargebacks, refunds or disputes may be processed
- Issuing Cards / Debit Cards and card spend may be processed
- mutual payments may be facilitated
- other financial functionalities may be offered, where available
3.4 Stored value and balance
The User acknowledges that a functional balance or stored value may exist through Stripe Treasury and/or a Stripe Financial Account.
This balance is, however, not held by Driv3 itself in its own bank account on behalf of the User, but within the financial infrastructure offered or facilitated by Stripe.
Balances visible within the Wallet or through a Stripe Financial Account do not constitute a credit with Driv3 itself and do not qualify as a payment account, bank account, deposit or electronic money issued by Driv3.
3.5 Driv3 not a financial institution
Driv3 acts exclusively as a technical, administrative and contractual platform layer.
Driv3:
- is not a bank
- is not a credit institution
- is not an independent payment service provider
- is not an electronic money institution
- does not itself issue electronic money
- does not itself hold client funds in its own bank account for Users
- does not itself offer deposits
- does not itself grant credit in the sense of an independent credit product
- does not guarantee the availability of Stripe functionalities
- does not guarantee approval by Stripe or financial partners
To the extent that financial functionalities are used through the Platform, these are provided, processed or facilitated through Stripe, Stripe Treasury, Stripe Connect, Stripe Financial Accounts and/or financial partners engaged by Stripe.
3.6 Stripe terms and approval
Use of Stripe Connect, Stripe Treasury, Stripe Financial Accounts, Wallet functionalities, top-ups, withdrawals, transfers, reserves, payouts, card functionalities, Tap to Pay, QR Payments, Payment Links and related financial functionalities depends on:
- approval by Stripe
- applicable Stripe terms
- KYC/KYB
- compliance checks
- sanctions checks
- risk assessments
- availability per country
- technical availability
- status of the Stripe Connected Account
- status of the Stripe Financial Account
- applicable laws and regulations
Stripe may refuse, restrict, suspend, block or terminate access or require additional information. Driv3 is not liable for decisions, restrictions, delays or measures of Stripe, financial partners, banking partners, payment partners, supervisory authorities or competent authorities.
3.7 Mandatory KYC/KYB
Every User who wishes to use Stripe Connect, Treasury, Financial Accounts, Wallet functionalities, top-ups, withdrawals, card functionalities, mutual payments or other financial functionalities must fully and correctly complete the KYC/KYB procedure required by Stripe, Driv3 or applicable legislation.
The User warrants that all personal data, business data, bank details, tax data, licence data, identification data and other information provided have been entered and supplied correctly, completely, up to date and truthfully.
If KYC/KYB is not completed fully, in time or successfully, Driv3 may restrict, suspend or terminate access to the Platform, ride functionalities, Wallet, Treasury functionalities, payouts, top-ups, card functionalities or other functions.
3.8 Availability per country
Treasury and Financial Account functionalities are only available if and to the extent that Stripe supports them in the relevant country, for the relevant type of User, for the relevant business model and for the relevant account status.
If Treasury functionality or Financial Account functionality is not available in a particular country, for a particular User or for a particular account status, Driv3 may use regular Stripe Connect functionality or other payment and payout methods supported by Stripe.
The User has no right to the availability of Treasury functionalities if Stripe does not offer, does not approve, restricts, changes or terminates them.
3.9 Wallet display
The Wallet within the Platform displays, to the extent available, the balance, transactions, reserves, set-offs, subscription costs, network fees, mutual forwarding fees, Stripe costs, top-ups, payouts, card spend, mutual payments, corrections and other mutations relating to the User's Stripe Connected Account and/or Stripe Financial Account.
The Wallet constitutes a technical and administrative display of underlying Stripe data and is not an independent payment account, bank account or e-money account of Driv3.
3.10 Available balance and reserved balance
Not every visible balance is immediately available.
A balance may be displayed as, among other things:
- available
- reserved
- pending
- blocked
- being processed
- under review
- not payable
- corrected
- contested
- subject to chargeback, refund, dispute, reversal, set-off or compliance check
Driv3 may distinguish in the Wallet between available balance and reserved balance.
3.11 Corrections
Driv3 may, through Stripe functionalities, correct balances, reserves, subscription costs, network fees, mutual forwarding fees, Stripe costs, transactions, top-ups, payouts, card spend, mutual payments or Wallet displays in the event of:
- technical errors
- administrative errors
- delays
- duplicate entries
- incorrect transactions
- refunds
- disputes
- reversals
- chargebacks
- negative balances
- fraud
- abuse
- outages
- compliance restrictions
- discrepancies between Platform data and Stripe data
- costs or corrections from Stripe
- instructions or corrections from Stripe
- statutory obligations
- other reasonable grounds
In the event of a difference between the Wallet display and the underlying data of Stripe, banking partners or payment partners, Driv3 may align the Wallet display with the underlying transaction or balance information.
3.12 Top-ups
Users may, where available and approved, add amounts to their Stripe Financial Account, Wallet or comparable financial functionality through methods supported by Stripe, including iDEAL, Wero or other payment methods.
Top-ups depend on Stripe, banking partners, banks, payment networks, compliance checks, business days, cut-off times, fraud prevention, technical processing, settlement periods and applicable limits.
Driv3 does not guarantee that top-ups are immediately and definitively processed, settled or irrevocably available.
3.13 Provisional balance increase on top-up
If a User carries out a top-up through iDEAL, Wero or another payment method supported by Stripe, Driv3 may choose, within the technical and contractual frameworks of Stripe and the Platform and on the basis of a payment confirmation, authorisation, webhook, status notification or other technical signal from Stripe, to make the relevant amount provisionally available in whole or in part in the Wallet or Stripe Financial Account, before the underlying funds have been definitively received, settled or made available by Stripe, a bank, payment method or financial partner.
Such a provisional balance increase qualifies as a conditional and revocable credit entry. The User thereby acquires no unconditional right to the amount as long as the underlying payment has not been processed definitively, irrevocably and without restriction by Stripe, the bank, payment method or financial partner.
Driv3 may apply conditions, limits, risk assessments, waiting periods or user profiles to provisional balance increases. Driv3 is not obliged to allow a provisional balance increase and may refuse, restrict, pause or terminate this functionality per User, country, payment method, amount, risk profile, account status or transaction.
If the underlying top-up is not definitively received, is reversed, is contested, is delayed, is withheld by Stripe, is corrected by a bank or payment method, proves to be fraudulent or otherwise does not become fully available, Driv3 may, through the available Stripe functionalities, correct, reverse, set off, reserve or recover the provisional balance increase from the User.
If Stripe or another third party applies costs, commissions, corrections, reversals or deductions to the underlying payment or top-up, Driv3 may process these in the balance made available and recover them in full from the User.
The User remains fully liable for any negative balance, any reversal, any correction and any loss arising from a provisional balance increase.
3.14 Withdrawals and payouts to external bank account
Users may, where available and approved, withdraw amounts from their Stripe Financial Account, Wallet or comparable financial functionality or have them paid out to an external bank account or other destination supported by Stripe.
Withdrawals, transfers and payouts depend on Stripe, banking partners, external banks, payment networks, compliance checks, business days, cut-off times, fraud prevention, technical processing and applicable limits.
Driv3 does not guarantee a fixed processing period and is not liable for delay, refusal, reversal, blocking or restriction by Stripe, banking partners, external banks, payment networks or competent authorities.
3.15 Financial Account IBAN and business payments
If Stripe or a financial partner makes available a Financial Account IBAN, account number or comparable payment identifier, the User may use it for business receipts, payments and transactions to the extent permitted by Stripe, applicable legislation and these Terms.
A Financial Account IBAN is provided by Stripe or a financial partner and not by Driv3. Driv3 is not a bank and does not offer an independent payment account.
Driv3, Stripe and financial partners may monitor, restrict, block, investigate or refuse transactions in the event of risk, abuse, fraud, sanctions or compliance signals, technical reasons or statutory obligations.
The User is responsible for the lawfulness, origin, destination, administration and tax treatment of payments made through the Financial Account IBAN or Wallet.
3.16 Mutual payments
Users may, where available, make mutual payments through the Wallet, Stripe Financial Account or other financial functionalities. Article 5.18 applies to mutual payments.
3.17 Passenger payments
The Platform may facilitate passenger payments or customer payments through, among other things, Tap to Pay, QR Payments, Payment Links, card payments, digital wallets or other payment methods supported by Stripe.
Passenger payments depend on Stripe, banks, card networks, payment methods, devices, internet connection, compliance checks, authorisation, settlement, fraud prevention, chargebacks, refunds and disputes.
Driv3 does not guarantee that a passenger payment is available immediately, definitively or without risk.
3.18 Issuing Card / Debit Card and card spend
The Platform may offer Users access to virtual or physical Issuing Cards / Debit Cards or comparable card functionalities, where available, activated and approved by Stripe.
Card functionalities may be linked to the Wallet, Stripe Financial Account or other Stripe functionality.
Card spend depends on available balance, reserves, limits, Stripe, card networks, card acceptors, compliance checks, technical operation and applicable terms.
Driv3 may restrict, pause, block or terminate card functionalities where necessary for compliance, security, risk management, negative balances, abuse, fraud, Stripe restrictions or technical reasons.
3.19 Limits
Driv3 and/or Stripe may apply limits to, among other things:
- top-ups
- provisional balance increases
- payouts
- withdrawals
- transfers
- reserves
- available balance
- ride volume
- outstanding amounts
- negative balances
- payment methods
- Wallet use
- Financial Account functionalities
- card spend
- Tap to Pay
- QR Payments
- Payment Links
- mutual payments
Limits may differ per User, country, account status, risk profile, compliance status, transaction history, verification status, product phase or other reasonable criteria.
4. Ride structure, forwarding and rates
4.1 Direct Rides
If a ride is accepted directly by an executing Carrier and there is no regular customer relationship of another Carrier, the contract of carriage is concluded exclusively between:
- the Passenger; and
- the executing Carrier
The executing Carrier bears full responsibility and liability for the performance of the ride.
4.2 Regular Customers / Subcontracting
If a ride is performed for the benefit of a regular customer of another Carrier:
- the original Carrier remains the contracting party towards its customer
- the executing Carrier acts as an independent subcontractor
- the executing Carrier is responsible for the correct performance of the ride
- the original Carrier is responsible for its own arrangements with the customer
The Platform is not a party to this agreement.
4.3 Selection without instruction
A Carrier may select an executing Carrier on the basis of its own preferences, including preferences based on experience, reliability, availability, statistical data, previous cooperation, reputation, customer preferences, vehicle type, Community Rules or analysis of historical performance.
This selection does not qualify as the exercise of authority by Driv3 and does not create an employment relationship.
4.4 Rate integrity
Each Carrier independently determines its rates and may independently set or differentiate them, including per client, per postcode area, per contract, per region, per type of ride, per vehicle type, per vehicle class, per service level, per Community or on the basis of other commercial arrangements.
The Platform may set standard rates, recommended rates, configurations or legally permitted maximum rates as a default, among other things to simplify the use of the Platform or to support legal frameworks.
The Carrier remains responsible for its own rates and may change them at its own discretion within the available functionalities, contractual arrangements and legal limits.
If a rate is stated for a specific Ride Order, the executing Carrier must respect that rate unless otherwise agreed with the client.
This provision does not qualify as price determination by the Platform.
4.5 Responsibility for ride data
The User is responsible for the accuracy of ride data, including pick-up location, destination, time, customer details, vehicle type, rate, payment method, remarks, contract information and any special instructions.
Driv3 is not liable for damage arising from incorrect, incomplete or late entry of ride data by Users.
4.6 No obligation to accept
Users are free to accept or refuse rides, subject to any contractual arrangements they themselves have made with customers, clients, Community Holders, other Carriers or internal staff.
The Platform does not create any obligation to work, obligation of availability or minimum performance obligation.
5. Subscriptions, network fee, mutual forwarding fee, Stripe costs, reserves and set-off
5.1 Subscriptions
Driv3 may offer access to the Platform or certain functionalities on the basis of a subscription.
Subscription costs are payable as displayed in the Platform, offer, price list, agreement or other communication from Driv3.
Subscription costs are exclusive of VAT and other levies, unless expressly stated otherwise.
Subscriptions are entered into per calendar month and may be cancelled monthly as of the end of the current subscription month, via the Platform or in writing, unless expressly agreed otherwise.
Unless expressly stated otherwise or required by law, interim cancellation, restriction, suspension or termination does not give any right to repayment or pro-rata reimbursement of subscription costs, licence costs, network fees or other fixed costs already due or paid.
5.2 Trial Period
Driv3 may offer a trial period. The standard trial period is 7 days, unless stated otherwise.
At the end of the trial period, the subscription automatically converts into a paid monthly subscription, unless the User cancels the subscription before the end of the trial period in accordance with the available functionality or the arrangements made.
A trial period does not automatically give a right to full access to all functionalities. Certain functionalities, including full ride information, financial functionalities, Wallet, Stripe Treasury, Stripe Financial Accounts, payouts, card functionalities, full community participation or the receipt and performance of rides, may depend on full KYC/KYB, account activation and approval by Stripe or Driv3.
Driv3 may show non-verified Users limited preview, test or introductory functionalities, or allow them to use such functionalities, such as a limited map view, limited ride functionality, limited creation of clients or a limited number of test/trial rides, without this giving rise to any right to full access.
5.3 Payment of subscription costs
Subscription costs may be collected, reserved or set off by Driv3 via Wallet balance, Stripe Financial Account balance, Stripe Connected Account balance, available balances, future receipts, payouts or other payment functionalities available via the Platform.
Driv3 prefers to set off subscription costs directly via the Platform, Wallet or Stripe Financial Account. Driv3 is not obliged to accept payment via SEPA direct debit or any other payment method.
If Driv3 permits payment via SEPA direct debit, card payment or another payment method, Driv3 may apply additional conditions, checks, limits or reserves on account of reversal risk, fraud risk, settlement risk or other reasonable grounds.
In the event of non-payment, insufficient balance, reversal, failed direct debit or other payment problems, Driv3 may restrict, suspend or terminate access to the Platform, financial functionalities, ride functionalities or other components.
5.4 Mutual forwarding fee
Users may agree a mutual forwarding fee among themselves for the forwarding, performance, distribution or processing of rides.
The Platform:
- does not set any mandatory mutual forwarding fees between Users
- is not a party to the underlying commercial arrangement between Users
- exclusively facilitates the technical, administrative and financial processing
- may apply system-technical limits where necessary for the operation, security or integrity of the infrastructure
5.5 Network Fee
Driv3 may charge a network fee for facilitating the network, administration, dispatch, wallet, payment and set-off functionality surrounding ride forwarding.
The network fee is calculated exclusively on the mutual forwarding fee and not on the full ride amount.
The amount of the network fee is displayed in the Platform, offer, price list, agreement or other communication from Driv3.
Network fees are exclusive of VAT and other levies, unless expressly stated otherwise.
5.6 Stripe Costs and pass-through
Stripe may charge costs, commissions, transaction costs, payment method costs, credit card costs, iDEAL costs, Wero costs, dispute fees, chargeback costs, refund costs, Connect costs, Treasury costs, Financial Account costs, payout costs, transfer costs, card costs, compliance costs, currency costs, product costs or other costs to Driv3, the Platform account or a Stripe account linked to Driv3.
For current Stripe Costs, Driv3 may refer to the rates, documentation or website of Stripe. The actual costs may depend on country, payment method, card type, product, transaction, currency, card network, Stripe configuration and applicable terms.
To the extent that these costs relate to the use of the Platform, a Stripe Connected Account, a Stripe Financial Account, Wallet functionalities, ride payments, top-ups, payouts, withdrawals, chargebacks, disputes, refunds, transfers, card spend or other transactions of or on behalf of a User, these costs are borne economically by the User concerned.
Driv3 may pass through, invoice, reserve, set off or debit these costs in full via Wallet balance, Stripe Connected Account balance, Stripe Financial Account balance, future receipts, ride proceeds, mutual forwarding fees, reserves, payouts or other amounts due to the User.
The fact that Stripe legally, technically or administratively invoices certain costs to, or debits them from, Driv3 or the Platform account does not affect the right of Driv3 to pass these costs through economically to the User concerned.
5.7 Dispute fees, chargebacks and Stripe pass-through
In the event of a chargeback, dispute, contested payment, refund disagreement, reversal, investigation by a payment method, card issuer, bank, card network, Stripe or another payment partner, Stripe or other parties involved may charge costs.
These include, among others, dispute received fees, dispute countered fees, chargeback costs, network fees, Smart Disputes fees, investigation costs, refund costs, administration costs and other comparable or future costs relating to the payment, ride, transaction, card payment, passenger payment, top-up, payout, Wallet mutation or financial functionality concerned.
These costs are borne in full by the User, Carrier, Driver, Community Holder, client or other party involved to whom the ride, payment, transaction, customer relationship, conduct, complaint, error, reversal, chargeback, dispute or cause of the contestation concerned relates.
This applies regardless of whether the User, Carrier or Driver concerned is substantively right or wrong, and regardless of whether the chargeback, dispute or contestation is ultimately won, lost, withdrawn, reversed, settled, repaid, answered manually, answered automatically or otherwise resolved.
If Stripe charges a dispute received fee, this fee is always borne by the User, Carrier or Driver concerned or causing it. This fee remains payable even if the dispute is later won, withdrawn or resolved, unless Stripe actually repays this fee to Driv3 or the Platform.
If Stripe charges a dispute countered fee, Smart Disputes fee or other fee for the manual, automatic or AI-assisted answering or handling of a dispute, this fee is also passed through one-to-one to the User, Carrier or Driver concerned or causing it. If Stripe later actually repays or credits such a fee to Driv3 or the Platform, Driv3 may administratively correct or credit this amount.
Driv3 passes through Stripe Costs, dispute fees, chargeback costs and related costs one-to-one as Stripe or another payment partner charges them to Driv3, the Platform account, a linked Stripe account or an account connected thereto. This applies to the current rates and to all future changes, increases, decreases, new cost types or amended rate structures of Stripe or other payment partners.
To the extent that Stripe or a payment partner first charges these costs technically, legally, contractually or administratively to Driv3, the Platform account or an account linked to Driv3, this does not affect the right of Driv3 to recover these costs in full from the User, Carrier, Driver, Community Holder, client or other party involved.
Driv3 may withhold, reserve, debit, write off, invoice or set off these costs via Wallet balance, Stripe Connected Account balance, Stripe Financial Account balance, future balance, ride proceeds, mutual forwarding fees, network fees, subscription fees, payouts, withdrawals, reserves, prepaid amounts or other amounts due to the User or processed via the Platform.
If insufficient balance is available, the full amount remains payable and Driv3 may use future receipts, balances, ride proceeds, credits, payouts or other amounts for set-off. The payment obligation continues to exist after suspension, restriction or termination of the account.
The amount of dispute fees, chargeback costs, Smart Disputes fees and other Stripe Costs always follows the current rates, terms and cost types of Stripe or the payment partner concerned. Driv3 is not obliged to bear or absorb these costs itself.
5.8 Set-off across payment forms
Subscription costs, network fees, mutual forwarding fees, Stripe Costs and other set-off may take place in relation to, among others:
- cash payments
- card payments
- Tap to Pay
- QR Payments
- Payment Links
- digital payments
- invoice rides
- Account Rides
- Wallet balance
- Stripe Connected Account balance
- Stripe Financial Account balance
- Treasury transactions
- card spend
- top-ups
- payouts
- withdrawals
- future receipts
- other agreed or technically supported payment methods
5.9 Automatic set-off
The User authorises Driv3 to automatically set off, withhold, reserve, correct or debit amounts via Stripe Connect, Stripe Treasury, Stripe Financial Accounts, Wallet functionalities or other available Stripe functionalities for, among others:
- subscription costs
- network fees
- mutual forwarding fees
- Stripe Costs
- administration costs
- ride-related amounts
- corrections
- refunds
- disputes
- chargebacks
- reversals
- negative balances
- fraud
- damage and penalties, exclusively to the extent that the amount thereof is established or has been determined by Driv3 with reasons and has been specified to the User in writing in advance
- third-party costs
- obligations towards other Users
- obligations towards Driv3
- statutory obligations
- other amounts owed by the User
Driv3 informs the User via the Platform or by e-mail of every set-off, withholding or reserve, stating the basis and the amount. The User may contest a set-off in accordance with article 5.20.
5.10 Pre-financing and provisional availability
Driv3 may, but is not obliged to, make amounts provisionally available to a User before the underlying payment, top-up, ride payment or other transaction has been definitively settled or released by Stripe, a bank, payment method or financial partner.
Such provisional availability is always conditional, revocable and subject to definitive receipt, settlement, compliance checks and the absence of reversal, chargeback, refund, dispute, fraud, correction or restriction.
If the underlying transaction is not received, not received in full, delayed, contested, reversed or corrected, Driv3 may immediately correct, reverse, reserve, set off or recover from the User the provisionally available amount via the available Stripe functionalities.
In doing so, Driv3 may make use of Wallet balance, Stripe Financial Account balance, Stripe Connected Account balance, future receipts, ride proceeds, mutual forwarding fees, platform credits, reserves or other amounts due to the User.
The User is obliged to make up any shortfall immediately and, where there is a negative balance, to clear it.
5.11 Limits on provisional availability
Driv3 may apply limits to the provisional availability of amounts, including limits per transaction, per day, per week, per month, per User, per payment method, per country, per risk profile or per account status.
Driv3 may refuse or restrict provisional availability in the case of, among others:
- new Users
- incomplete KYC/KYB
- deviating transaction behaviour
- high top-up amount
- previous reversals
- negative balances
- fraud indications
- compliance investigation
- restricted Stripe status
- increased risk for Driv3, Stripe, banking partners or other Users
5.12 Reserves and balance holds
Driv3 may, via the available Stripe functionalities, temporarily or structurally reserve, block or make unavailable amounts where this is reasonably necessary for:
- risk management
- securing mutual forwarding fees
- set-off of subscription costs
- set-off of network fees
- Stripe Costs
- chargebacks
- disputes
- refunds
- payment disagreements
- reversals
- fraud prevention
- negative balances
- provisional balance increases
- compliance checks
- network integrity
- protection of other Users
- protection of Passengers
- protection of Driv3
- protection of Stripe or financial partners
- performance of contractual obligations
- statutory obligations
5.13 Negative balance
If a negative balance arises as a result of chargebacks, reversals, refunds, disputes, corrections, Stripe Costs, fees, fraud, disagreements, misuse, payouts, provisional balance increases, reserves or other causes, the User remains fully bound to make up and/or clear this negative balance immediately.
Driv3 may use future receipts, Wallet balances, reserves, ride proceeds, platform credits or other amounts due to the User for set-off against negative balances or outstanding obligations.
The User remains liable for negative balances, including after suspension, restriction or termination of the account.
If a User fails to pay outstanding amounts, negative balances, Stripe Costs, dispute fees, chargebacks, subscription costs, network fees, mutual forwarding fees or other amounts owed within 14 days of notification, the User is in default without further notice of default and Driv3 is entitled to charge statutory commercial interest (article 6:119a of the Dutch Civil Code (BW)), as well as extrajudicial collection costs of 15% of the principal sum with a minimum of EUR 40, and the actual legal costs and other reasonable costs of recovery, to the extent permitted by law.
5.14 Risk buffer and minimum reserve
Driv3 may, via the available Stripe functionalities, apply a risk buffer, minimum reserve or dynamic reserve where this is necessary or desirable for risk management, continuity, securing mutual forwarding fees, Stripe Costs, chargebacks, refunds, disputes, reversals, payment risks, fraud prevention, provisional balance increases or protection of network integrity.
The amount, duration and conditions of a reserve may differ per User, country, account status, verification status, transaction volume, risk profile, payment method, ride volume, history or other reasonable criteria.
Driv3 may adjust, increase, decrease or release reserves where the circumstances give reason to do so.
5.15 No interest or provision of credit
Reserves, balance holds, delays, negative balances, top-ups, Wallet functionalities, provisional balance increases or Treasury functionalities do not qualify as an independent credit product of Driv3.
Unless expressly agreed in writing, Driv3 owes no interest on amounts held, reserved, blocked, pending or delayed.
5.16 Account Rides
Article 10.3 applies to Account Rides and rides on account. The User assesses for itself whether it accepts Account Rides from a particular Carrier, client, Community or Business Customer.
5.17 Tip / Gratuity
A tip or gratuity given via Tap to Pay, QR Payment, Payment Link, card payment or another payment method is intended for the performing Driver, unless expressly indicated otherwise or required otherwise by law or contract.
If the tip is technically received via a Carrier, Community Holder, Stripe account, Wallet or other linked payment structure, that party is responsible for correct internal processing, onward payment and tax treatment towards the Driver.
Driv3 is not responsible for the internal distribution, onward payment, payroll administration, tax treatment or employment-law qualification of tips.
5.18 Mutual Payments
Mutual Payments may be facilitated via Wallet, Stripe Financial Account or other financial functionalities where available.
Driv3 does not charge a standard network fee on Mutual Payments, unless costs or conditions have been clearly made known in advance for a specific functionality.
The User is responsible for the lawfulness, business basis, administration and tax processing of Mutual Payments.
5.19 Community-related payments
If Driv3 offers functionality for participation fees or other community-related payments, conditions or costs made known in advance may apply thereto.
Driv3 is not a party to the underlying arrangements between the Community Holder and community members, unless expressly agreed otherwise in writing.
5.20 Contestations
If a User contests a set-off, reserve, correction, fee, Stripe Costs, network fee, mutual forwarding fee or transaction, the User must report this in writing as soon as possible with sufficient substantiation.
A contestation does not automatically suspend the obligation to pay, make up, clear or set off.
Driv3 may keep amounts reserved during the investigation.
Driv3 responds substantively to a reasoned contestation within 14 days.
6. Liability, indemnity and security
6.1 Liability of the performing party
The performing Carrier is fully liable for:
- performance of the ride
- compliance with legislation
- compliance with licensing requirements
- conduct of Drivers
- damage to Passengers or third parties
- loss, injury, delay or other damage during or surrounding the ride
- soundness of the vehicle, equipment, communication means and other materials used
- correct insurance
- correct tax and administrative processing
- accuracy of ride data
- compliance with arrangements with customers, Passengers, clients, Community Holders and other Carriers
6.2 Liability of the original Carrier for a regular customer
If a ride is performed for a regular customer of another Carrier, the original Carrier remains responsible for its contractual relationship with that customer, unless agreed otherwise.
The performing Carrier remains responsible for the actual performance of the ride.
Driv3 is not a party to this mutual relationship.
6.3 Indemnity
The User indemnifies Driv3 against claims, demands, penalties, damage, costs and proceedings of Passengers, customers, clients, Drivers, community members, Community Holders, Carriers, regulators, tax authorities, Stripe, financial partners or other third parties arising from or relating to:
- performance or non-performance of rides
- acts or omissions of the User, Drivers or employees
- licences, driving licences, inspections, insurance or statutory obligations
- customer relationships
- Community Rules or community arrangements
- Account Rides
- payment, payout, tip, refund, chargeback or dispute
- tax or administrative obligations
- incorrect data
- breach of these Terms
- breach of laws or regulations
- damage caused by vehicles, Drivers, Passengers or third parties
This indemnity also applies if a third party holds Driv3 liable while the underlying responsibility lies with the User, Carrier, Driver, Community Holder or client.
6.4 Liability of the Platform
Driv3 is liable exclusively for direct damage that results directly from an attributable failure by Driv3, to the extent that liability has not been validly excluded.
Liability for indirect damage is excluded, including in any event:
- lost profit
- missed rides
- loss of turnover
- reputational damage
- consequential damage
- loss of customers
- loss of data
- business interruption
- missed opportunities
- loss due to delayed payout
- loss due to blocking or restriction of Stripe functionalities
- damage caused by third parties
- damage caused by incorrect data of Users
To the extent that the liability of Driv3 cannot be validly excluded, it is limited per event and cumulatively per calendar year to the higher of (a) EUR 500 and (b) the amount that the User concerned paid to Driv3 in subscription costs and network fees in the twelve months preceding the event causing the damage, with a maximum of EUR 1,000 per calendar year.
This limitation does not apply to the extent that the damage is the result of intent or wilful recklessness on the part of Driv3 or its managerial staff, or to the extent that liability therefor cannot be limited by law.
6.5 Financial infrastructure and third parties
Driv3 is not liable for damage, delay, loss, blocking, restriction, refusal, correction, reversal or unavailability arising from or relating to:
- Stripe Connect
- Stripe Treasury
- Stripe Financial Accounts
- Wallet functionalities
- banking partners
- external banks
- payment networks
- card networks
- compliance checks
- sanctions checks
- KYC/KYB processes
- fraud detection
- chargebacks
- refunds
- disputes
- reversals
- Stripe Costs
- reserves
- balance holds
- top-ups
- provisional balance increases
- withdrawals
- payouts
- transfers
- Tap to Pay
- QR Payments
- Payment Links
- card spend
- decisions of Stripe
- decisions of financial partners
- decisions of regulators
- other financial infrastructure provided by third parties
6.6 No guarantee of balance availability
Driv3 does not guarantee that balances, top-ups, provisional balance increases, transfers, payouts, withdrawals, card functionalities or reserves are immediately or definitively available at any given time.
Availability may depend on Stripe, banking partners, external banks, payment networks, statutory checks, technical processing, settlement periods, risk assessment, compliance checks, business days, cut-off times, outages or internal security measures.
6.7 No liability for provisional availability
If Driv3 chooses to make an amount provisionally available before the underlying payment has been definitively settled, this is done as an operational service and subject to definitive processing by Stripe, banks, payment methods and financial partners.
Driv3 is not liable for damage arising from the correction, reversal, reserve, set-off, blocking or restriction of a provisionally available amount if the underlying payment is not received definitively, in full or on time, or is later contested, reversed, corrected or restricted.
6.8 User data and external bank accounts
The User is fully responsible for the accuracy, completeness and currency of:
- bank details
- identification data
- company data
- tax data
- licence data
- contact details
- ownership structure
- KYC/KYB documentation
- other information required for the use of Stripe, Treasury, Wallet, payouts or the Platform
Driv3 is not liable for damage caused by incorrect, incomplete or outdated data of the User.
6.9 Security and account use
The User is responsible for the secure use of login credentials, devices, passwords, two-factor authentication, e-mail accounts, telephone numbers and other means of access.
All actions performed via the User's account are deemed to have been performed by or on behalf of the User, unless the User demonstrates that there has been misuse that cannot be attributed to the User and that was reported immediately after discovery.
It is not permitted to sell, transfer, give away, let, lend an account or allow it to be used by a third party without the prior written consent of Driv3.
In the event of termination, sale, transfer, merger, cessation of business, change of owner or change of control, the User must inform Driv3 where this is relevant to the account, KYC/KYB, Stripe, Wallet, community management, ride processing or financial functionalities.
In the event of unauthorised access, account compromise, unauthorised account transfer, misuse or doubt about identity or control, Driv3 may restrict or block access or require additional verification.
6.10 Duty to report incidents
The User must immediately report security incidents, suspicious transactions, incorrect balances, suspected fraud, misuse, unauthorised access, account compromise, loss of means of access or other relevant incidents to Driv3.
Upon notification or suspicion of an incident, Driv3 may temporarily restrict access to the Platform, Wallet, Treasury functionalities, ride functionalities or payouts.
7. Suspension and termination
7.1 Voluntary termination
The User may terminate the agreement with effect from the end of the current subscription month, via the functionality provided for that purpose in the Platform or in writing. Users without a paid subscription may close the account at any time.
Termination does not affect outstanding obligations, negative balances, subscription costs, network fees, mutual forwarding fees, Stripe costs, chargebacks, refunds, disputes, reserves, tax obligations, payment obligations, confidentiality obligations and anti-circumvention obligations.
7.2 Termination by Driv3
Driv3 may terminate the agreement in the event of, among other things:
- fraud
- serious safety incidents
- misuse of the infrastructure
- misuse of Wallet, Treasury or Financial Account functionalities
- unauthorised sale, transfer, rental or provision of an account
- bankruptcy or a petition for bankruptcy
- suspension of payments
- revocation, suspension or expiry of a licence
- revocation or suspension of a driver card
- revocation or invalidation of a driving licence
- structural non-compliance with obligations
- non-payment
- negative balances
- unpaid Stripe costs
- incorrect or incomplete KYC/KYB information
- refusal or restriction by Stripe
- risk to Driv3, Stripe, banking partners, other Users, Passengers or the network
7.3 Suspension and restriction
Driv3 may temporarily restrict, suspend or block access to the Platform, Wallet, Treasury functionalities, Financial Account functionalities, ride functionalities, payouts, top-ups, withdrawals, dispatch functionalities, card functionalities or other components in the event of:
- negative balances
- insufficient balance for subscription costs, network fees, mutual forwarding fees, Stripe costs or reserves
- suspicious, unusual or fraudulent transactions
- chargebacks, refunds, disputes, reversals or payment disagreements
- misuse of Wallet, Treasury or Financial Account functionality
- incomplete or refused KYC/KYB
- sanctions, AML, fraud or compliance risk
- restriction, suspension or termination by Stripe
- request or instruction from Stripe, a banking partner, a regulator or a competent authority
- risk to Driv3, Stripe, banking partners, other Users, Passengers or the network
- breach of these Terms
- breach of applicable legislation
- breach of Stripe terms
- damage to network integrity or reputation
7.4 Suspension in the event of settlement risk
Driv3 may restrict or suspend access to Wallet, Treasury, payouts, top-ups, withdrawals, ride functionalities or other components in the event of increased risk relating to provisional availability, including delayed settlement, failed top-ups, contested payments, unusual top-up behaviour, indications of fraud, negative balances or insufficient reserve.
7.5 No goodwill
Termination, restriction or suspension does not give rise to any right to goodwill compensation, compensation, damages or compensation for missed rides, turnover, customers or opportunities.
7.6 Settlement after termination
After termination, Driv3 may continue to reserve, set off or withhold amounts to the extent necessary for:
- outstanding subscription costs
- network fees
- mutual forwarding fees
- Stripe costs
- negative balances
- chargebacks
- refunds
- disputes
- reversals
- corrections
- provisional balance increases
- tax obligations
- damage
- statutory obligations
- ongoing investigations
- risk management
- instructions from Stripe or competent authorities
After termination, the User remains responsible for chargebacks, refunds, disputes, Stripe costs, corrections, negative balances and other obligations for as long as these may still arise or be processed under Stripe, payment methods, card networks, legislation, contractual rules or reasonable administrative periods.
Driv3 may hold reserves or reserved amounts for as long as reasonably necessary for the settlement of the above obligations.
7.7 Access to data after termination
Driv3 may restrict access to account data, ride data, financial data or administrative data after termination, to the extent permitted by legislation.
To the extent required by law or necessary for tax, administrative or legal purposes, data may be retained.
8. Licences, insurance, inspections and verification
8.1 Responsibility and duty to keep information current
The Carrier is responsible for valid licences, driver cards, driving licences, insurance, vehicle documentation, APK (periodic vehicle inspection), taxi inspections, periodic inspections, tax registration and other requirements necessary for offering or performing transport services.
The User keeps its business details in the Platform up to date, including registration with the Chamber of Commerce (KvK), legal form, registered address, VAT identification number, directors, ownership and control, bank details and contact details. The User checks these details at least once a year and upon every change.
The Carrier ensures that for every vehicle and every Driver deployed via the Platform a valid APK, taxi inspection, insurance (at least third-party liability insurance for professional passenger transport), licence, driver card and driving licence is registered in the Platform, and enters renewed documents before the expiry date of the previous document. Driv3 may display expiry dates and send reminders; this does not release the Carrier from its own responsibility.
A vehicle or Driver for which a required document has expired, been revoked or not been registered may not be deployed via the Platform until a valid document has been registered. Driv3 may automatically block the Driver or vehicle concerned from ride functionalities.
8.2 Verification by the Platform
Driv3 may request documentation or data to verify compliance without thereby becoming a regulator, employer, licensing authority, insurer, inspection body or main contractor.
8.3 Driving Licence and Authorisation Verification
Driv3 may check driving licence data, driver data, authorisations, licences, vehicle data or other relevant data via the RDW, linked registers, verification partners or documentation supplied by the User.
This verification may be used for safety, compliance, fraud prevention, access management, ride functionalities, community access or other reasonable platform purposes.
Successful verification by Driv3 does not mean that Driv3 assumes the legal responsibility of the Carrier, Driver or employer.
8.4 No guarantee through verification
The requesting, checking or acceptance of documents or data by Driv3 does not mean that Driv3 guarantees that the User fully complies with all legal requirements.
The User remains fully responsible for compliance with laws and regulations.
8.5 Revocation or expiry of documents
If licences, driving licences, driver cards, insurance, inspections or other required documents expire, are revoked, are suspended or prove to be invalid, Driv3 may restrict, suspend or terminate access to the Platform in whole or in part.
8.6 Continuing duty to inform
The User must report changes in licences, insurance, inspections, business details, vehicles, Drivers, driving licences, bank details, KYC/KYB information or other relevant data without delay via the available Platform functionalities or in writing. This includes, among other things, deregistration or a change of registration with the Chamber of Commerce (KvK), cessation of business, bankruptcy or a petition for bankruptcy, suspension of payments or a petition for suspension of payments, changes in registered address, trade name, legal form, VAT identification number, ownership or control, and changes of the vehicles used or their insurance or inspection status. The User is itself responsible for the accuracy, currency and timely reporting of this information; checks or verifications by Driv3 do not assume this responsibility. To the extent permitted by law, Driv3 is not liable for the consequences of incorrect, incomplete or late reported data.
9. Data protection and privacy
9.1 Controller
Driv3 is an independent controller for the processing of personal data within the Platform, unless expressly agreed otherwise.
For specific data flows, the allocation of roles between Driv3, Users, Carriers, Community Holders, Stripe or other parties may differ. For customer and passenger data that a Carrier itself enters into the Platform, the Carrier is the controller and Driv3 acts as processor within the meaning of the GDPR. In that case, the data processing agreement made available by Driv3 applies, which forms part of the agreement.
9.2 Purposes
Personal data is processed for, among other things:
- access to the Platform
- account management
- ride processing
- dispatch
- GPS location functionalities
- administration
- support
- payment and settlement
- Wallet functionalities
- Stripe Connect
- Stripe Treasury
- Financial Account functionalities
- Financial Account IBAN
- card functionalities
- mutual payments
- passenger payments
- community functionalities
- Community Statistics
- driving licence and authorisation verification
- KYC/KYB
- fraud prevention
- risk management
- compliance
- tax reporting
- CDT obligations
- statutory obligations
- security
- improvement of services
9.3 Sharing with third parties
Personal data is not sold.
Personal data may be shared with third parties to the extent necessary for the performance of the services, statutory obligations, payment processing, financial functionalities, compliance, risk management, reporting or processing by engaged processors.
These may include:
- Stripe
- financial partners of Stripe
- banking partners
- payment networks
- card networks
- external banks
- software suppliers
- hosting providers
- data centres
- compliance providers
- verification providers
- the RDW or linked registers
- tax authorities
- regulators
- competent authorities
- other parties where required by law or necessary for the performance of the agreement
9.4 Financial and compliance data
For the use of Stripe Connect, Treasury, Financial Accounts, Wallet functionalities, reserves, set-offs, top-ups, provisional balance increases, payouts, withdrawals, card functionalities and mutual payments, the following may be processed, among other things:
- personal data
- business data
- financial data
- transaction data
- balance information
- bank account details
- KYC/KYB documentation
- tax data
- fraud prevention data
- risk signals
- compliance data
- sanctions screening data
- data on ultimate beneficial owners
- data on directors or representatives
9.5 Retention periods
Data is retained in accordance with applicable national, European and local legislation and in principle for a maximum of 7 years, unless legislation, tax obligations, compliance obligations, disagreements, fraud investigations, Stripe requirements or other legitimate interests require a longer retention period.
9.6 Privacy statement
The privacy statement of Driv3 also applies to the processing of personal data.
In the event of a conflict between these Terms and the privacy statement with regard to privacy rights and data processing, the provision that most specifically relates to the processing concerned prevails, unless mandatory law provides otherwise.
9.7 Users' own privacy arrangements
The User is itself responsible for the lawful processing and provision of personal data within its own business operations and when engaging contractors, subcontractors, Drivers or other third parties. The User ensures that legally required information and mutual arrangements are in place, including a data processing agreement where the party concerned acts as processor. Where parties are independent controllers, each remains responsible for its own processing. Driv3 is not a party to these mutual arrangements and does not assume these obligations; Driv3's own statutory obligations remain unaffected.
10. Business customer relationships, account rides and invoicing
10.1 Business customer relationships
Business customers are contractually customers of the Carrier concerned, unless expressly agreed otherwise in writing.
Driv3 does not automatically become a contracting party towards a Business Customer because a ride, invoice, payment, Wallet transaction or administration is processed via the Platform.
10.2 Invoicing
The Platform is not an invoicing party for transport services, unless expressly agreed otherwise in writing.
Invoices generated via the Platform are legally deemed to have been issued by the Carrier concerned.
10.3 Account Rides
For Account Rides or rides on account, the responsibility for assessment, approval, payment and payout lies with the Carrier, client or Business Customer concerned, unless expressly agreed otherwise in writing.
Driv3 may technically register, display, administer or process Account Rides, but does not guarantee that an Account Ride will be approved, paid or paid out within a particular period.
If a Carrier, client or Business Customer fails to pay or approve Account Rides, or does so late or incompletely, Driv3 is not liable for this.
Driv3 may, but is not obliged to, mediate, flag or communicate in the event of delays, complaints or disagreements concerning Account Rides. Driv3 does not thereby become a party to the payment obligation and does not assume any collection risk.
10.4 Tax responsibility
Driv3 is not liable for the tax obligations of Carriers, including VAT, income tax, corporation tax, payroll taxes, local taxes, record-keeping obligations or invoicing requirements.
The User is itself responsible for the correct tax treatment of rides, mutual forwarding fees, network fees, subscription costs, Stripe costs, payouts, Wallet transactions, Treasury transactions, tips, reserves and other financial data.
10.5 No assumption of customer relationship
Use of the Platform does not mean that Driv3 assumes the customer relationships of Users.
Users remain responsible for their own customer arrangements, service quality, communication, prices and invoicing.
10.6 Payment processing for Business Customers
If business payments, invoice rides, corporate rides or account payments are processed via Stripe, Wallet, Treasury or other functionalities, the legal customer relationship between the Business Customer and the Carrier concerned continues to exist, unless agreed otherwise in writing.
Driv3 solely facilitates the technical, administrative and financial processing.
11. Intellectual property, software, GPS, dashboards, communities and financial functionalities
11.1 Intellectual property
All intellectual property rights in the Platform, software, source code, databases, designs, documentation, trade names, trademarks, workflows, algorithms, dashboards, portals, interfaces and other materials are vested in Driv3 or its licensors.
11.2 Licence
Users receive a limited, non-exclusive, non-transferable and revocable licence to use the Platform in accordance with these Terms.
11.3 Changes to functionalities
Driv3 may change, expand, restrict, replace, pause or discontinue functionalities.
This applies, among other things, to:
- ride functionalities
- dispatch functionalities
- Wallet functionalities
- Stripe Connect functionalities
- Treasury functionalities
- Financial Account functionalities
- top-ups
- provisional balance increases
- payouts
- reserves
- card functionalities
- Tap to Pay
- QR Payments
- Payment Links
- GPS functionalities
- dashboards
- community functionalities
- portals
- roles and rights
- rates
- network fee logic
- notifications
- reports
- integrations
11.4 Real-time notifications, GPS and location permission
The Platform uses real-time notifications and may use GPS location data for, among other things, ride execution, dispatch, ETA, route information, safety, evidence, disagreement handling, community functionalities and operational management.
For dispatch, ride execution, ETA, safety and CDT registration, access to the location of the Driver's device is necessary. The User enables location access for the Driv3 app on the device and keeps it enabled during the period in which the Driver is logged in as available or is performing a ride. Outside that period, the Platform does not record any location.
The Carrier ensures that its Drivers have been informed, before first use, about the processing of their location data, the purposes thereof and the parties with whom these are shared in accordance with article 11.5, and that a valid legal basis under the GDPR exists for this. The legal basis for the processing by Driv3 is the performance of the agreement and the legitimate interest in safe and verifiable ride execution.
Disabling notifications, location services or app permissions may result in missed functionalities, rides, messages, warnings, location updates or other relevant information.
Driv3 is not liable for damage resulting from the disabling, missing or delayed receipt of notifications or location data.
11.5 Sharing of GPS location
GPS location data may, insofar as necessary for the operation of the Platform, be shared with the Drivers, Carriers, dispatchers, clients, Community Holders, Passengers or support staff involved.
The sharing of location data is intended for ride execution, ETA, safety, operational coordination, evidence, disagreement handling and improvement of services.
During the use of location-based functionalities, the current location and availability of the Driver or vehicle may be visible to Users with the role or rights assigned for that purpose and, insofar as relevant to the ride, clients and Passengers. The Platform may record GPS locations, timestamps and route data during rides and link them to a Ride Order. These data may, within applicable authorisations and legislation, be consulted afterwards for ride administration, route information, evidence, disagreement handling, safety and fraud prevention. Driv3 does not guarantee uninterrupted or complete location recording.
11.6 Dashboards
The Platform may display dashboards with information on, among other things, rides, balances, payments, Wallet, card spend, community data, performance, statistics, rates, reserves, Account Rides, payouts and operational data.
Dashboard data may be delayed, incomplete, indicative or dependent on third parties. Driv3 does not guarantee that dashboard data are always complete, real-time or error-free.
11.7 Communities
Users may, where available, create, manage or participate in Communities.
The Community Holder is responsible for the management of the Community, including admission, removal, Community Rules, quality requirements, dress codes, vehicle requirements, service levels, customer relationships, complaints and internal arrangements within the Community.
Driv3 solely facilitates the technical environment in which Communities can be managed. Driv3 is not a party to and not responsible for the content, compliance, enforcement or reasonableness of Community Rules, unless Driv3 expressly acts itself or is legally obliged to do so.
A Community does not create a partnership, company, franchise, employment relationship, main contractorship or other legal collaboration with Driv3.
11.8 Admission to and removal from Communities
The Community Holder may admit, refuse, restrict or remove Users from its Community on the basis of its own Community Rules, arrangements, quality requirements, customer relationships, complaints or operational reasons.
Disagreements about admission, removal, customer relationships, dress, vehicle type, service quality, conduct or other internal Community Rules are primarily a matter between the Community Holder and the User concerned.
Driv3 is not obliged to mediate, enforce or intervene in internal community disagreements.
Driv3 solely reserves the right to take platform-wide measures where necessary for safety, legislation, Stripe/compliance, fraud, technical operation or protection of the Platform as a whole.
11.9 Community terms
Community Holders may apply their own community terms, house rules, quality requirements or participation conditions.
The Community Holder is itself responsible for the content, publication, reasonableness, application and enforcement of these terms.
Driv3 is not liable for damage, loss, conflicts or claims arising from community terms or their application by a Community Holder.
11.10 Community Statistics
Driv3 may make dashboards, statistics or analyses available to Community Holders about their Community, such as ride volume, peak hours, average ride prices, availability, acceptance, operational performance or other data.
Driv3 determines which data are available and whether these are displayed individually, aggregated, anonymised or in limited form.
Driv3 may offer Community Holders settings to determine which statistics or data are visible to themselves or to community members, if and insofar as this functionality is available.
Community Statistics may contain commercially sensitive information. Driv3 may therefore restrict the availability, visibility, level of detail or sharing of statistics on the basis of privacy, commercial sensitivity, technical possibilities, legislation, community settings or other reasonable grounds.
11.11 No SLA
No SLA or guaranteed uptime applies unless agreed in writing.
Driv3 strives for reliable availability, but does not guarantee that the Platform, Stripe functionalities, Wallet, Treasury, Financial Accounts, notifications, GPS, dashboards, Communities, dispatch or other functions are available without interruption or error.
11.12 Dependence on third parties
The Platform depends on third parties, including Stripe, cloud providers, telecom providers, card issuers, banking partners, payment networks, card networks, data providers, map/route providers, app stores, RDW, verification partners, data centres, API providers and other technical suppliers.
Driv3 is not liable for failures, restrictions, delays, errors, changes or termination of services by these third parties.
11.13 Additional financial functionalities
Driv3 may make additional financial functionalities available, including virtual or physical Issuing Cards / Debit Cards, expense functionalities, spending controls, additional Treasury functionalities, payment methods, reports, reserves or other Stripe services.
Such functionalities may be subject to additional terms, limits, costs, verifications, country restrictions, compliance checks and approval by Stripe or its financial partners.
Driv3 may change, restrict, pause or discontinue these functionalities at any time where necessary for compliance, risk management, technical operation, product development or network integrity.
11.14 No right to specific functionality
The User has no right to the continued availability of a specific functionality, integration, payment method, Stripe functionality, Treasury functionality, Financial Account, Wallet component, card functionality, Community, Dashboard, role, right, report or product module.
11.15 Restrictions on use
It is not permitted to use the Platform for:
- unlawful activities
- fraud
- money laundering
- sanctions evasion
- misuse of payment functionalities
- misuse of Wallet or Treasury
- misuse of card functionalities
- unauthorised access
- unauthorised account transfer
- reverse engineering
- disruption of systems
- circumvention of security
- infringement of third-party rights
- activities that are contrary to Stripe terms or applicable legislation
12. Anti-circumvention and network integrity
12.1 Anti-circumvention
It is not permitted to structurally handle customer relationships, rides, payments, mutual forwarding fees, network fees or collaborations outside the Platform with the aim of avoiding subscription costs, network fees, Stripe costs, infrastructure costs, reserves, risk management or other obligations.
It is likewise not permitted to wrongly register a ride that has actually been performed or accepted as cancelled or no-show, to deliberately adjust a ride status incorrectly or to handle a ride outside the Platform with the aim of evading mutual forwarding fees, network fees or other obligations that are due. In case of suspicion of such acts, Driv3 may investigate relevant ride, status, transaction and, insofar as lawful, location data and apply the measures of article 12.6. Driv3 is not obliged to actively check or investigate every case.
If it is demonstrable that a ride has been performed, the mutual forwarding fee and the network fee remain due as if the ride had been settled via the Platform, without prejudice to article 12.6.
12.2 Poaching and customer relationships
Active poaching of customers, Business Customers, Carriers, Drivers, contractors or network relationships of other Users is not permitted if this relationship arose via the Platform or has demonstrably been strengthened via the Platform.
A customer relationship may, among other things, have arisen via the Platform if:
- the first contact demonstrably took place via the Platform
- a ride relationship was established via the Platform
- customer data were obtained via the Platform, a Ride Order, dashboard, Community or other platform functionality
- collaboration between Users arose via the Platform
- the relationship was built up or strengthened through repeated rides, forwarding or collaboration via the Platform
12.3 Communities and customer relationships
Within Communities, additional Community Rules may apply regarding customer relationships, customer approach, quality, conduct, dress, vehicle type, service level and collaboration.
The Community Holder is primarily responsible for the enforcement of Community Rules and internal disagreements within the Community.
Driv3 is not obliged to intervene in internal community disagreements, including discussions about customer relationships, customer approach or removal from the Community, unless Driv3 itself deems this necessary for protection of the Platform as a whole, legislation, safety, Stripe/compliance or serious indications of abuse.
12.4 Network integrity
Users must refrain from conduct that harms the integrity, safety, reliability, reputation or continuity of the network.
This includes, among other things:
- structural failure to honour ride arrangements
- misuse of customer relationships
- misuse of ride information
- misuse of financial functionalities
- fraudulent transactions
- false information
- circumvention of mutual forwarding fees
- circumvention of network fees
- harmful conduct towards other Users
- improper use of data
- reputational damage to Driv3 or the network
12.5 Duration
This provision applies for the term of the agreement and for 12 months after termination, insofar as permitted by law.
12.6 Measures
In the event of a breach, Driv3 may:
- restrict access
- suspend accounts
- restrict ride functionalities
- restrict Wallet functionalities
- apply reserves
- set off amounts
- recover damage
- terminate the agreement
- take additional measures that are reasonably necessary for protection of the Platform as a whole
In the event of a breach of article 12.1, 12.2 or 12.4, or of article 17 (Confidentiality), the User forfeits to Driv3 an immediately payable penalty of € 2,500 per breach, increased by € 250 for each day that the breach continues, up to a maximum of € 25,000 per breach. This penalty is without prejudice to Driv3's right to performance and to full compensation of the damage actually suffered; article 6:92 paragraph 2 of the Dutch Civil Code (BW) does not apply.
Driv3 is not obliged to act as mediator, enforcer or disagreement-resolution body between Users or within Communities.
13. Amendment of terms
13.1 Amendment
Driv3 may amend these Terms where this is necessary or desirable due to:
- product development
- changes to Stripe functionalities
- introduction or modification of Treasury or Financial Accounts
- changes to card functionalities
- changes to subscriptions or fee structures
- changes in legislation
- compliance requirements
- risk management
- tax obligations
- operational changes
- security
- network integrity
- commercial reasons
13.2 Notification
Driv3 will inform Users of material amendments in a manner that is reasonably appropriate, for example by e-mail, platform notification, dashboard message or publication within the Platform.
Material amendments will, where reasonably possible, be announced at least 14 days before they take effect.
Driv3 may implement amendments with immediate effect where this is necessary due to legislation, Stripe, financial partners, compliance, security, fraud, misuse, technical necessity, financial risks or protection of the Platform.
13.3 Acceptance
Continued use of the Platform after amended Terms take effect constitutes acceptance of the amended Terms.
If a User does not agree to amended Terms, the User may terminate the agreement with effect from the date on which the amendment takes effect. If the amendment is a material amendment to the detriment of the User, Driv3 will credit prepaid subscription costs for the period after the termination date on a pro rata basis. Outstanding obligations continue to apply in full.
14. Tax reporting (DAC7)
14.1 Reporting obligations
Driv3 may be required to report data to competent tax authorities, including under DAC7 or other national, European or international tax regulations.
14.2 Data to be reported
For tax reporting, Driv3 may use data from, among other sources:
- the Platform
- ride records
- Stripe Connect
- Stripe Treasury
- Stripe Financial Accounts
- Wallet functionalities
- subscription costs
- network fees
- mutual forwarding fees
- Stripe Costs
- Account Rides
- tips/gratuities
- mutual payments
- community-related payments
- card spend
- payouts
- top-ups
- withdrawals
- provisional balance increases
- reserves
- corrections
- invoicing data
- customer data
- transaction history
- other financial transactions
14.3 Obligation of the User
Users are obliged to provide correct, complete and up-to-date tax, identification, business and bank details.
If a User provides incorrect or incomplete details, the User is liable for the consequences thereof, including tax corrections, penalties, delays, blocks or reporting problems.
14.4 Retention
Driv3 may retain tax and administrative data for as long as this is necessary for statutory obligations, tax reporting, audit trails, disagreements, compliance or risk management.
15. Central Taxi Transport Database (CDT)
15.1 Technical connection
The Platform may facilitate a technical connection to the Central Taxi Transport Database (CDT) or comparable statutory databases, if and to the extent required or available.
15.2 Responsibility of the Carrier
Carriers remain responsible for correct compliance with CDT obligations and other statutory obligations within the taxi industry.
15.3 No assumption of statutory responsibility
Facilitating a technical connection, data processing or reporting does not mean that Driv3 assumes the statutory responsibility of the Carrier.
15.4 Correct data
The User is responsible for the timely, complete and correct provision of data required for the CDT, ride registration, tax reporting, compliance, Account Rides or other statutory obligations.
To the extent required by the applicable CDT regulations and supported by the functionalities used, timestamps, ride statuses and location or GPS data, among other things, may be recorded when a ride is started, performed and ended and provided to competent authorities, including the ILT. The User remains responsible for correct ride and work registration and for fulfilling his statutory obligations. Driv3 does not guarantee that every data registration or forwarding takes place under all circumstances without disruption, delay or error.
16. Force majeure
16.1 Force majeure
Driv3 is not liable for failures caused by circumstances beyond its control, including:
- disruptions at external service providers
- outage or restriction of Stripe
- outage or restriction of Stripe Connect
- outage or restriction of Stripe Treasury
- outage or restriction of Stripe Financial Accounts
- disruptions at banking partners
- disruptions at external banks
- disruptions at payment networks
- disruptions at card networks
- disruptions at issuing or acquiring services
- cloud outages
- data centre outages
- CDN outages
- DNS outages
- API outages
- app store restrictions
- network outages
- telecommunications outages
- internet outages
- RDW or register outages
- disruptions at verification partners
- cyberattacks
- data breaches caused by third parties
- government measures
- sanctions
- compliance blocks
- technical calamities
- strikes
- fire
- natural disasters
- pandemics
- war
- terrorism
- other circumstances reasonably beyond the control of Driv3
16.2 Consequences
In the event of force majeure, Driv3 may suspend the performance of its obligations for as long as the force majeure continues.
Driv3 is not obliged to compensate damage resulting from force majeure.
16.3 Financial infrastructure
If, due to force majeure or third-party disruptions, top-ups, provisional balance increases, payouts, withdrawals, transfers, reserves, Wallet displays, ride payments, card payments, card spend, Stripe Costs, mutual forwarding fees, network fees or subscription costs are delayed, blocked, corrected or cannot be executed, Driv3 is not liable for this.
17. Confidentiality
17.1 Confidential Information
Confidential Information means all non-public information that a User obtains through or in connection with the Platform, including in any event:
- ride data, Ride Orders and ride history of other Users
- customer, passenger and contact details that become visible through a Ride Order, Dashboard, Community or other platform functionality
- rates, mutual forwarding fees and commercial arrangements of other Users
- Community Statistics, dashboards, balance and transaction data that do not concern the User's own data
- non-public information about the Platform, including functionality, security, pricing arrangements, integrations and product development
17.2 Duty of confidentiality
The User keeps Confidential Information confidential, uses it solely for the performance of rides and the cooperation through the Platform, and does not share it with third parties.
The User may share Confidential Information with its own Drivers, employees and dispatchers to the extent necessary for the performance of a ride, provided that these persons are bound by an equivalent duty of confidentiality. The User is responsible for compliance by these persons.
The User takes appropriate technical and organisational measures to secure Confidential Information against loss, unauthorised access and unlawful use, including secure use of login credentials and devices in accordance with article 6.9.
17.3 Customer and passenger data
Customer and passenger data that a User receives through a Ride Order from another User may be used solely for the performance of that ride. Use for the User's own marketing, recruitment, direct approach or building of the User's own customer base is not permitted, without prejudice to article 12.2.
After completion of the ride, the User deletes this data from its own systems, unless and to the extent that a statutory retention obligation applies or the data is required for the administration, invoicing or handling of disagreements relating to that ride.
17.4 Exceptions
The duty of confidentiality does not apply to information that:
- is or becomes public without any action on the part of the User
- was demonstrably already lawfully known to the User before it was obtained through the Platform
- must be disclosed under a statutory obligation or court order, in which case the User informs Driv3 in advance to the extent permitted by law
- concerns the User's own data
17.5 Confidentiality by Driv3
Driv3 treats the User's business data, rates, customer relationships and transaction data as confidential and shares them solely in accordance with article 9, the privacy statement, the Stripe terms or a statutory obligation.
Driv3 may use aggregated or anonymised data that cannot be traced back to an individual User for statistics, Community Statistics, product improvement and reporting.
17.6 Duration
The obligations under this article apply for the term of the agreement and for three years after termination. For personal data and data subject to a statutory duty of confidentiality, the obligations remain in force indefinitely.
18. Final provisions
18.1 Applicable law
These Terms are governed by Dutch law.
18.2 Competent court
Disagreements will be submitted exclusively to the District Court of Amsterdam, unless mandatory law provides otherwise.
18.3 Complaints and escalation
Users may report complaints, questions or disagreements about the Platform via info@driv3.com or via the contact channels in the Platform. Driv3 confirms receipt of a complaint and aims to respond substantively within 14 days.
Driv3 may assess complaints or reports and, if it deems this appropriate, mediate, advise, refer or take measures.
Driv3 is not obliged to act as a dispute resolver, collection party, supervisor or enforcer between Users, Community Holders, Drivers, Carriers, clients or Passengers.
18.4 Severability
If any provision of these Terms proves to be void, voidable or unenforceable, the remaining provisions remain in full force.
Driv3 may replace the provision concerned with a valid provision that corresponds as closely as possible to the purpose and intent of the original provision.
18.5 No waiver
The failure or delay by Driv3 to exercise any right does not constitute a waiver of that right.
18.6 Assignment
Driv3 may assign its rights and obligations under the agreement to a group company, legal successor, acquirer of the business or other third party, to the extent permitted by law.
The User may not assign rights and obligations without the prior written consent of Driv3.
18.7 Precedence of additional terms
Additional terms may apply to specific functionalities, including Stripe, Treasury, Financial Accounts, card functionalities, business customer portals, subscriptions, Communities, contractors, Account Rides or other modules.
In the event of conflict between documents, unless mandatory law provides otherwise or agreed otherwise in writing, the following order of precedence applies:
- individual written agreement between Driv3 and the User
- specific additional product or module terms
- Stripe terms for Stripe, Treasury, Financial Account, payment and card functionalities
- processor agreement or data processing agreement, where applicable to the data flow concerned
- privacy statement for privacy and data protection matters
- these Terms
18.8 Evidential value of platform data
Administrative data, ride data, Wallet data, Stripe data, GPS data, acceptance logs, transaction logs, communication data, dashboard data and other platform records may be used by Driv3 as evidence of use, acceptance, ride performance, payment, set-off, reserve, dispute, chargeback, balance, notification, amendment or other relevant event.
If the User asserts that this data is incorrect, the User must demonstrate this with reasons and sufficient substantiation.
18.9 Survival
Provisions which by their nature are intended to survive termination remain in force after termination of the agreement.
These include in any event provisions concerning:
- liability
- indemnity
- payment
- set-off
- subscription costs
- network fees
- mutual forwarding fees
- Stripe Costs
- chargebacks
- refunds
- disputes
- provisional balance increases
- negative balances
- reserves
- Account Rides
- tips/gratuities
- community obligations
- tax reporting
- privacy
- confidentiality
- intellectual property
- anti-circumvention
- network integrity
- disagreements
- applicable law
18.10 Language
These Terms have been drawn up in Dutch. Driv3 may make translations available. In the event of a difference in interpretation or conflict between the Dutch text and a translation, the Dutch text prevails.
18.11 Version and entry into force
This is version 1.0 of the general terms and conditions of Driv3, adopted on 10 October 2026 and effective with immediate effect from that date. The current version can always be consulted via the Platform and via driv3.com.