Data Processing Agreement
GDPR Data Processing Agreement taxiID B.V.
Download the Data Processing Agreement (PDF)
This Data Processing Agreement applies to all forms of personal data processing carried out by taxiID B.V., registered with the Chamber of Commerce under number 52397297 (hereinafter referred to as "Processor"), on behalf of a counterparty to whom it provides services, the client (hereinafter referred to as "Controller"). This data processing agreement forms an integral part of the arrangements between the Parties as agreed in the Agreement (hereinafter referred to as "Agreement") between both parties.
1. Purposes of processing
1.1. The Processor agrees to process personal data on behalf of the Controller under the terms of this Data Processing Agreement. Processing shall take place exclusively within the framework agreed upon in the Agreement, plus those purposes that are reasonably related thereto or that are determined with further consent.
1.2. The personal data processed by the Processor in the context of the activities referred to in the previous paragraph, and the categories of data subjects to whom they relate, are included in Appendix 1.
1.3. The Processor shall not process the personal data for any purpose other than as determined by the Controller. The Controller shall inform the Processor of the processing purposes insofar as these have not already been stated in this Data Processing Agreement.
1.4. The personal data to be processed on behalf of the Controller remain the property of the Controller and/or the relevant data subjects.
2. Processor Obligations
2.1. With regard to the processing operations mentioned in Article 1, the Processor shall ensure compliance with applicable laws and regulations, including in any case the laws and regulations in the field of personal data protection, such as the General Data Protection Regulation.
2.2. The Processor shall, upon the first request of the Controller, provide information regarding the measures it has taken concerning its obligations under this Data Processing Agreement.
2.3. The obligations of the Processor arising from this Data Processing Agreement also apply to those who process personal data under the authority of the Processor, including but not limited to employees, in the broadest sense of the word.
2.4. The Processor shall immediately inform the Controller if, in its opinion, an instruction from the Controller infringes upon GDPR legislation.
2.5. To the extent within its power, the Processor shall provide reasonable assistance to the Controller for the purpose of conducting Data Protection Impact Assessments (DPIAs). The time spent on this will be charged by the Processor to the Controller.
3. Transfer of personal data
3.1. The Processor may process personal data in countries within the European Union. Transfer to countries outside the European Union is not permitted unless the Controller provides consent for this.
3.2. The Processor shall inform the Controller which country or countries are involved.
4. Allocation of responsibility
4.1. The permitted processing activities will be carried out by the Processor's employees within an automated environment.
4.2. The Processor is solely responsible for the processing of personal data under this Data Processing Agreement, in accordance with the instructions of the Controller and under the express (final) responsibility of the Controller. The Processor is expressly not responsible for other processing of personal data, including but not limited to the collection of personal data by the Controller, processing for purposes not notified to the Processor by the Controller, processing by third parties, and/or for other purposes.
4.3. The Controller guarantees that the content, use, and instructions for the processing of personal data as referred to in this Data Processing Agreement are not unlawful and do not infringe upon any rights of third parties.
5. Engaging third parties or subcontractors
5.1. The Processor may use third parties in the context of this processor agreement and will provide a list of third parties (sub-processors) to the Controller upon request.
5.2. The Processor shall, in any case, ensure that these third parties assume in writing at least the same obligations as those agreed upon between the Controller and the Processor.
5.3. The Processor guarantees correct compliance with the obligations of this Processor Agreement by these third parties and is, in the event of errors by these third parties, liable for all damages as if it had committed the error(s) itself.
6. Security
6.1. The Processor will make efforts to take sufficient technical and organizational security measures regarding the processing of personal data to be performed, against loss or any form of unlawful processing (such as unauthorized access, impairment, alteration, or disclosure of personal data).
6.2. The Processor has, in any case, taken the security measures as mentioned in the Security Protocol, which is attached as an annex to this Processor Agreement. The Processor may unilaterally amend the Security Protocol at any time. It will inform the Controller of any amendments.
6.3. The Processor does not guarantee that the security is effective under all circumstances. If an explicitly described security measure is missing from the Processor Agreement, the Processor will make efforts to ensure that the security meets a level that is not unreasonable, given the state of the art, the sensitivity of the personal data, and the costs associated with implementing the security.
6.4. The Controller shall only make personal data available to the Processor for processing if it has ensured that the required security measures have been taken. The Controller is responsible for compliance with the security measures agreed upon by the Parties.
7. Notification obligation
7.1. The Controller is at all times responsible for reporting a security breach and/or data breach (defined as: a breach of the security of personal data that leads to a risk of adverse consequences, or has adverse consequences, for the protection of personal data) to the supervisory authority and/or data subjects. To enable the Controller to comply with this legal obligation, the Processor shall inform the Controller of the security breach and/or data breach within 48 hours after becoming aware of the breach.
7.2. A notification must always be made, but only if the event has actually occurred.
7.3. The notification obligation includes, in any case, reporting the fact that a breach has occurred. In addition, the notification obligation includes:
- the nature of the personal data breach, including, where possible, the categories of data subjects and personal data records concerned and, approximately, the number of data subjects and personal data records concerned;
- the name and contact details of the data protection officer or other contact point where more information can be obtained;
- the likely consequences of the personal data breach;
- the measures proposed or taken by the Processor to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
8. Handling requests from data subjects
8.1. In the event that a data subject submits a request to exercise their legal rights to the Processor, the Processor will forward the request to the Controller, and the Controller will handle the request further. The Processor may inform the data subject accordingly.
9. Secrecy and confidentiality
9.1. Regarding secrecy and confidentiality, reference is made to the taxiID General Terms and Conditions.
10. Audit
10.1. The Processor hereby grants the Controller the right to have an audit conducted by an independent third party bound by confidentiality to verify compliance with the provisions of this Data Processing Agreement, or the Processor shall provide the Controller with a third-party statement from which it can be assumed that the Processor is acting in accordance with the provisions of this Data Processing Agreement. The foregoing is subject to the judgment of the Processor.
10.2. This audit may take place once per year, as well as in the event of a concrete suspicion of misuse of personal data.
10.3. The Processor will cooperate with the audit and make all information reasonably relevant to the audit, including supporting data such as system logs, and staff available as promptly as possible.
10.4. The findings resulting from the audit will be assessed by the Processor and may be implemented by the Processor at its own discretion and in a manner determined by the Processor itself.
10.5. The costs of the audit shall be borne by the Controller.
11. Liability
11.1. Regarding liability, reference is made to the General Terms and Conditions of taxiID, with the following additional paragraphs:
11.2. The Processor's liability for indirect damage is excluded. Indirect damage is defined as all damage that is not direct damage, including but not limited to consequential damage, lost profits, missed savings, reduced goodwill, damage due to business stagnation, damage resulting from the failure to determine marketing objectives, damage related to the use of data or data files prescribed by the Controller, or loss, corruption, or destruction of data or data files.
11.3. The exclusions and limitations referred to in this article shall not apply if and to the extent that the damage is the result of intent or willful recklessness on the part of the Processor's management.
12. Duration and termination
12.1. This Data Processing Agreement is concluded upon successful registration at www.taxiid.nl and the commencement of the use of the taxiID software.
12.2. For existing users (as of May 18, 2018), this agreement becomes effective as part of the existing agreement upon notification on May 18, 2018, with the opportunity to object until May 25, 2018.
12.3. This Data Processing Agreement is entered into for the duration specified in the Agreement between the Parties, or in the absence thereof, for the duration of the collaboration.
12.4. Once the Data Processing Agreement has been terminated for any reason and in any manner, and upon request, the Processor shall—at the Controller's discretion—return all personal data in its possession in original or copy form to the Controller, and/or delete and/or destroy such personal data and any copies thereof. The foregoing is subject to the exception of personal data that the Processor is required to retain in order to comply with legal (retention) obligations.
12.5. The Processor is entitled to revise this Data Processing Agreement from time to time. It will notify the Controller of any changes at least three months in advance. The Controller may terminate the agreement by the end of this three-month period if they cannot agree to the changes. Otherwise, the changes will be deemed to have been accepted by the Controller.
13. Governing law and dispute resolution
13.1. The Data Processing Agreement and its implementation are governed by Dutch law.
13.2. Any disputes that may arise between the Parties in connection with the Data Processing Agreement shall be submitted to the competent court in the district where the Processor is established.
Appendix 1: Specification of personal data and data subjects
taxiID processes data in a number of different contexts. These are described below for each data set. taxiID stores this data in its online network, which is secured and provided by Denit. taxiID has a data processing agreement with Denit.
taxiID makes all data of its clients (the taxi companies) available to those clients. It is the responsibility of the clients to handle this data appropriately.
Taxi companies can register with taxiID and supplement their profile with information about their business. For GDPR purposes, we distinguish between the contact person's personal data and the company details.
Contact person's personal details:
| Data | Reason for storage |
|---|---|
| Gender | For correct salutations in information and notification emails |
| First and last name | For contact and identification between taxi companies and for invoicing between taxi companies |
| Phone number | For identifying user accounts and for providing support. |
| Email address | Unique per account, also used as the profile username |
Company details:
These company details are not shared with third parties. However, taxi companies do have the option to share their details with other taxi companies via our system. They are free to choose whether or not to use this feature.
| Data | Reason for storage |
|---|---|
| Company Name | For identification between taxi companies, as well as in various contact and notification emails. |
| Address | For contact and identification between taxi companies and for invoicing between taxi companies |
| Chamber of Commerce Number | For identifying user accounts and for providing support. |
| VAT Number | Unique per account, also used as the profile username |
| TX-Quality Mark | To gain insight into the services to be provided to the taxi company |
| Number of vehicles | For the provision of taxiID services |
| Number of P-numbers | For the provision of taxiID services |
| Opening hours | For limiting booking options for passengers wishing to order from the taxi company. |
| Dispatch phone number | For providing services to passengers booking with the taxi company. |
| Dispatch email address | For providing services to passengers booking with the taxi company. |
Taxi company payment details
If a taxi company chooses to enter into a contract with taxiID, they pay via direct debit. To facilitate this, we store the following data.
| Data | Reason for storage |
|---|---|
| SEPA – IBAN | For direct debit of monthly payments |
| SEPA – BIC | For direct debit of monthly payments |
| SEPA – Account holder | For direct debit of monthly payments |
Driver data for taxi companies
Taxi companies have the option to add their drivers to their staff list. The taxi companies are responsible for this themselves; taxiID B.V. only processes this data. The agreements regarding this are set out in the data processing agreement between the taxi company and taxiID B.V.
taxiID does not own this data and will not use, share, or sell it.
| Data | Reason for storage |
|---|---|
| Gender | For correct salutations in information and notification emails. |
| First and last name | For contact and identification purposes for passengers. |
| Phone number | This is the number the passenger can use to reach the driver. |
| Address | For trip settlement / invoicing purposes |
| Email address | This email address is used by the taxi company to inform drivers. |
| Driver badge no. | Optional, can be used for accurate record-keeping |
| Driver's license no. | Optional, can be used for accurate record-keeping |
| Speaks | To provide the appropriate services |
BSN Number
We can also store a driver's BSN (Citizen Service Number). We consider this to be sensitive personal data. The BSN is used for logging into taxi BCTs. We need the BSN to exchange data with these BCTs. The BSN is also used as the driver card number.
Track and trace
In addition to personal data, we store track and trace data for taxi drivers for up to 1 year. This data allows local authorities to monitor and validate incidents in the taxi industry. We only store GPS data if a driver indicates they are online in their BCT or their Driver App. We do not store location data if a driver indicates they are offline or is logged out.
| Data | Reason for storage |
|---|---|
| GPS location | We store a vehicle's GPS data at 1-minute intervals. |
Taxi company member payment details
If a taxi company wishes to process direct debits or payments from within the taxiID administration, they may choose to add the following data to a taxi company profile. Payments can only take place between taxi companies; this data is only accessible by the central administrator of the members.
| Data | Reason for storage |
|---|---|
| SEPA – IBAN | For direct debit file generation |
| SEPA – BIC | For direct debit file generation |
| SEPA – Account holder | For direct debit file generation |
Passenger data
Passengers can book rides with our clients in a number of ways. Passenger data is the property of our clients and therefore not of taxiID B.V. taxiID does not consider itself the owner of this data and will not use, share, or sell this data.
We divide passenger data into 2 parts.
- Ride booking data
- The YourTaxiApp passenger accounts
Ride booking data
Passenger data is provided separately for each ride. This data is only used for processing the relevant ride. This may occur during booking, during the ride, or afterward for invoicing. It is possible that when booking a ride, the taxi company may ask if this data can also be used for other purposes. However, correct usage is the responsibility of the taxi companies; as taxiID, we only provide the options to agree to the data that a taxi company requests from its passengers.
It is possible that the data listed below may be expanded per taxi company; agreements regarding this are set out in the data processing agreement and are entirely the responsibility of the taxi company.
| Data | Reason for storage |
|---|---|
| Name | For correct salutations in information and notification emails. |
| Phone number | For contacting the passenger regarding service provision. |
| Email address | For contacting the passenger regarding service provision. |
Passenger app accounts
The passenger apps we provide are supplied white-label to taxi companies. Data from these apps is stored in the taxiID network at Denit.
Unlike "ride booking data," passenger accounts are created when using the app. These accounts are used repeatedly for booking taxi rides. When creating this account, we ask the passenger to accept a privacy policy. This statement specifies that a passenger can cancel their account by contacting the relevant taxi company.
| Data | Reason for storage |
|---|---|
| Name | For correct salutations in information and notification emails. |
| Phone number | For contacting the passenger regarding service provision. |
| Email address | For contacting the passenger regarding service provision. |
Specific payment details
It is possible to link a payment method to your passenger account. Please note that we do not process or store this data on taxiID Network servers. As a security measure, we ensure that credit card, bank, or other payment details are never sent to taxiID. We always use a third-party certified payment service provider (PSP) that handles payments with the banks.
We store the following data to process payments via the payment service provider (PSP).
| Data | Reason for storage |
|---|---|
| Payment label | Name the passenger gives to their payment method. |
| Credit card type | We store this for recognition in the app (e.g., Mastercard or Visa). |
| Card details | In the case of a credit card, we store the following identification details:
|
| SEPA – IBAN | For identification in the App |
| SEPA – BIC | For identification in the App |
| SEPA – Account holder | For identification in the App |
| Payment token | This is a reference to the payment details, allowing a payment request to be made to the PSP. |
Appendix 2: Security Protocol
Firewall
All servers are protected by a firewall managed by Denit. This provides protection for the servers from external threats.
VPN
To access our internal network from outside, a secure VPN connection must always be established. Access is granted only on a personal basis from within taxiID.
Antivirus
We use the latest version of antivirus software on all our machines.
Backups
Backups are made of all servers in the data center. Backups are performed at both the file level and the entire server level. These backups are stored in a separate data center.
Updates
Servers are actively updated with the latest patches to ensure they are equipped with the most recent security measures.
SSL
Our website is accessible via HTTPS. Data is transmitted over the network using SSL encryption.
Passwords
All passwords used are generated and stored by our password manager. These are highly secure passwords that are impossible to memorize.
Data center
Our servers are located in a highly secure data center in the Netherlands. This data center is permanently guarded and equipped with excellent climate control and fire protection systems.
Network infrastructure
The network infrastructure is optimally secured and custom-configured for taxiID. All incoming and outgoing data traffic is actively monitored by Denit.
Encryption
All passwords are stored in an encrypted format and are therefore unreadable. This also applies to other sensitive settings.
Monitoring
taxiID oversees all servers and applications through active monitoring, allowing for quick identification of any irregularities. In such cases, taxiID is also able to take immediate action.
Error handling
If an application displays an error message, it is presented in such a way that no technical or sensitive information is revealed.
Employee non-disclosure agreement
All our employees have signed a non-disclosure agreement to ensure that confidential information remains confidential.
Rights and roles
All systems in our network are only accessible via a login. Each employee has their own rights and roles, ensuring that not everyone has access to all systems.
taxiID B.V.
Overleek 4
1671 GD Medemblik
The Netherlands
Chamber of Commerce no. 52397297