Data Processing Agreement
DVP Systems Kft. as Data Processor · Annex to the Terms & Conditions · 1 January 2026
This Data Processing Agreement (hereinafter: Agreement) is entered into between DVP Systems Korlátolt Felelősségű Társaság (short name: DVP Systems Kft.; registered seat: 1141 Budapest, Szugló utca 125. G. ép. A. lház. 3. emelet 1. ajtó; tax number: 32788156-2-42; company registration number: 01 09 442670; hereinafter: Data Processor), and the Customer (hereinafter: Data Controller) that has entered into a subscription contract for the SimpliFleet and/or SimpliTime Platform.
Under the subscription contract between the Parties, the Data Processor processes personal data on behalf of the Data Controller. This Agreement is an inseparable annex to the subscription contract and takes effect on the day the subscription contract comes into force.
The Parties confirm that they are aware of, and accept as binding, their obligations under Article 28 of Regulation (EU) 2016/679 (GDPR). The Data Processor warrants that it processes personal data solely on the documented instructions of the Data Controller.
Section 1 – Subject matter and scope of the processing
The subject of the processing is the operation, support, maintenance and secure storage of DVP Systems' SimpliFleet and SimpliTime software services on behalf of the Data Controller.
| Data category | Scope of data processed | Legal basis | Retention period |
|---|---|---|---|
| Working-time data | Driver/employee name, ID, clock-in/clock-out times, project assignment, attendance data | Performance of a contract / Legal obligation | Term of the contract |
| TIG / Payroll data | Waybill data, performance-certificate records, payroll fields | Legal obligation (Accounting Act § 169) | 8 years |
| User account data | Administrator name, work email, login logs, role settings | Performance of a contract | Contract + 5 years |
| Compliance alerts | Maintenance warnings, TIG status alerts, approval-workflow records | Performance of a contract | Term of the contract |
Prohibited data: The Data Controller may not upload special categories of personal data (Article 9 GDPR: health, biometric, trade-union membership or criminal-record data) to the Platform. The Data Processor provides no feature for this.
Section 2 – The Data Processor's obligations (GDPR Article 28)
The Data Processor undertakes the following obligations under Article 28(3) GDPR:
- Following instructions: It processes personal data solely on the Data Controller's documented instructions, including instructions on transfers to a third country. If an instruction would breach the law, it informs the Data Controller without delay.
- Confidentiality: It ensures that persons authorised to process personal data are bound by confidentiality (under their employment contract or by law).
- Data security: It applies the technical and organisational measures required by Article 32 GDPR (see Section 4).
- Sub-processors: It may engage further processors under the Data Controller's general prior authorisation; it notifies the Data Controller at least 15 days before engaging a new sub-processor, and the Data Controller may object on reasonable data protection grounds.
- Data subjects' rights: It provides technical and organisational assistance to the Data Controller in fulfilling data subjects' rights (access, rectification, erasure, restriction, objection).
- Compliance assistance: It assists in meeting the obligations under Articles 32–36 GDPR (data security, breach handling, DPIA, prior consultation).
- Erasure / return of data: On termination of the Agreement — at the Data Controller's choice — it returns or deletes the personal data (see Section 6).
- Auditability: It makes available the information needed to demonstrate compliance and allows reasonable audits (on-site audits at most once a year, with 30 days' notice; remotely: by sharing security documentation and certificates).
Section 3 – Sub-processors
The Data Controller gives general prior consent to using the following categories of sub-processors. The Data Processor must pass on to every sub-processor, in writing, data protection, confidentiality, security and breach-handling obligations equivalent to those in this Agreement (Article 28(4) GDPR):
| Category | Purpose | Location | Data transfer |
|---|---|---|---|
| Cloud infrastructure (AWS/Azure) | Hosting, database, backups, compute | EU (Frankfurt/Dublin) | Processing within the EU; SCCs if a third country has access |
| Email provider | Transactional notifications, alerts | EU | Processing within the EU |
| Monitoring / logging | System monitoring, error reporting | EU | Processing within the EU |
| Support / CRM | Customer-support ticket handling | EU | Processing within the EU |
The Data Processor keeps an up-to-date list of sub-processors and provides it on request. It notifies the Data Controller at least 15 days in advance before engaging a new sub-processor. The Data Controller may object on reasonable data protection grounds; if it objects, the Parties consult in good faith about an alternative.
Section 4 – Technical and organisational measures (TOMs)
The Data Processor applies the following technical and organisational measures, proportionate to the risks (Article 32 GDPR):
Access management
Role-based access control (RBAC), least-privilege principle, MFA for administrative access, quarterly access reviews, immediate revocation on departure.
Encryption
TLS 1.2+ in transit; encryption at rest for production databases, backups and object storage; key management with restricted administrator access.
Data minimisation
Configurable retention periods; access limited to its purpose; tenant separation of working-time and TIG data.
Logging and audit trail
Administrative actions, export events, role changes and support access are logged; logs are protected against tampering, with a defined retention schedule.
Backup and recovery
Encrypted backups, regular recovery tests, defined RPO/RTO, a backup deletion/expiry policy.
Tenant isolation
Logical separation of customers' data; the production environment is kept separate from development/test environments.
Staff and development
Confidentiality obligations; GDPR and security training; change management and code review for security-relevant changes; a vulnerability-management process; secrets management.
Section 5 – Handling personal data breaches
Personal data breach: any security event that results in the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or unauthorised access to, personal data transmitted, stored or otherwise processed.
Notification deadlines
The Data Processor's 24-hour notification must include, as a minimum: the known nature of the breach; the data categories and processing operations affected; the processor systems affected; the likely consequences; the measures taken or proposed; and the contact details of the breach-handling contact. The Data Processor provides rolling updates until the full investigation is complete.
The Data Processor cooperates with the Data Controller in investigating, containing and documenting the breach, preparing the NAIH notification, and supporting the notification of data subjects (in cases under Article 34 GDPR).
Section 6 – End of the engagement and data deletion
On termination of the main service contract or this Agreement:
- The Data Processor provides the Data Controller with a 30-day export window . During this period the Data Controller may download the data stored in the system (TIG documents, working-time records, reports) in standard, machine-readable formats (CSV, XLSX, JSON).
- After the 30-day window expires, the Data Processor deletes or anonymises the Data Controller's personal data from the active systems.
- Data remaining in backups is deleted gradually in line with the normal backup lifecycle; restoration is only possible for recovery purposes or to meet a legal obligation.
- TIG/payroll data may be kept longer on the Data Controller's instruction and under the mandatory 8-year retention obligation in Section 169 of the Accounting Act.
- On request, the Data Processor issues a deletion certificate confirming the deletion carried out from the active systems.
Section 7 – The Data Controller's obligations and indemnity
The Data Controller declares and warrantsthat, before using the time tracking and TIG functions, it:
- has a valid legal basis and a documented Legitimate Interest Assessment (LIA) for processing employee data (Article 6(1)(c) and (f) GDPR).
- a Workplace Data Protection Policy has adopted (Section 11/A of the Labour Code) that meets the necessity and proportionality requirements.
- has informed its employees in advance and in writing, in a verifiable way, about the fact and purpose of time tracking, who can access the data, and data subjects' rights.
- where necessary, has carried out a Data Protection Impact Assessment (DPIA) (Article 35 GDPR).
Indemnity: The Data Controller undertakes to fully indemnify and hold the Data Processor harmless against any fine (including data protection fines imposed by the NAIH), penalty or third-party claim arising from the untruth of the Data Controller's warranty above or from an unlawful processing instruction given by the Data Controller. In a dispute, the Parties cooperate closely in the defence.
The Data Controller undertakes not to use working-time data for disproportionate employee monitoring, and to grant access only to authorised persons.
Section 8 – Final provisions
This Agreement is governed by the GDPR and Hungarian law. In a dispute, the Parties agree to the exclusive jurisdiction of the Budapest-Capital Regional Court, or, failing that, the Buda District Court .
This Agreement may only be amended in writing, signed by both parties. Any change to the Terms & Conditions automatically extends to the data-security provisions of this Agreement.
Signature block
| Field | Data Controller | Data Processor |
|---|---|---|
| Company name | _________________________ Kft./Zrt. | DVP Systems Korlátolt Felelősségű Társaság Tax number: 32788156-2-42 · Reg. no.: 01 09 442670 |
| Represented by | _________________________ | Bálint-Kurunczi Andrea Veronika |
| Title | _________________________ | Managing Director |
| Date | ____. ____. ____. | ____. ____. ____. |
| Signature | _________________________ | _________________________ |