Version 1, in force from 2026-10-29. Earlier versions stay available.

Data Processing Agreement (GDPR Article 28) — template, version 1

Version 1, in force from 2026-10-29. Published at https://trustbeat.eu/legal/dpa and incorporated by section 5.8 of the Terms of Service. It applies automatically to every customer who uses Signature Preservation; a customer that needs a countersigned copy can sign it as is. Language: English; a translation, if any, is informative.


Between

the customer who holds a TrustBeat account and uses Signature Preservation (the "Controller"), and

Trustbeat s.r.o., Company ID (IČO) 24888648, VAT ID CZ24888648, registered office Korunní 2569/108, Vinohrady, 101 00 Praha 10, Czech Republic, entered in the Commercial Register kept by the Municipal Court in Prague (Městský soud v Praze), section C, file 444524 (the "Processor", "TrustBeat").

1. Subject matter and duration

1.1 The Processor processes personal data on behalf of the Controller when providing Signature Preservation under the Terms of Service (the "Service"): preservation of the digital signatures the Controller submits, with their validation data, under the preservation profile https://trustbeat.eu/preservation/profile/pds-wst-v1.

1.2 This agreement applies for as long as the Processor holds personal data submitted by the Controller through the Service — that is, until the end of the preservation period of the Controller's last record plus 30 days (Terms §5.6), even after the Controller's account or subscription has ended.

1.3 Other TrustBeat services (Document Anchoring, Tamper-Evident Logs, AI Decision Anchoring, Audit Trail) accept hash values only; TrustBeat does not process personal data on the Controller's behalf in them, and this agreement does not apply to them. Account, billing and usage data of the Controller are processed by TrustBeat as controller, under its Privacy Policy.

2. Nature, purpose and scope of the processing (Annex 1)

Nature Receiving, validating, storing, time-stamping, renewing the evidence of, and making available to the Controller, signatures taken out of the Controller's signed files by the Controller's own extractor. The signed files themselves are never received.
Purpose Preserving proof of the existence and validation status of the signatures for the preservation period, so that the Controller can establish, exercise or defend legal claims and meet retention obligations.
Categories of data subjects Signers of the documents the Controller preserves (natural persons signing or sealing on their own or an organisation's behalf); persons named in certificates of certification authorities or time-stamping units (rare).
Categories of personal data Data in the signers' certificates: name, and as the certificate holds them, personal identification number or other identifier, email address, organisation, role, country; certificate serial numbers and validity; certificate status information (OCSP responses, CRLs) concerning those certificates; signing time; names, sizes and digests of the signed files as the Controller's extractor reports them (file names may contain personal data — the Controller chooses them). Any personal data in the signature's signed attributes (for example a signer role or commitment). No special categories (Art. 9) are intended; the content of the signed documents is never received.
Retention 30 years from each submission (or as agreed in writing), then 30 days; earlier when the Controller deletes a record (§9).
Location European Union only (Germany: hosting; France: encrypted backups).

3. Instructions

3.1 The Processor processes the personal data only on documented instructions from the Controller, including with regard to transfers to third countries, unless required to do so by Union or Member State law; in that case it informs the Controller before processing unless that law prohibits it.

3.2 The Terms of Service, the preservation profile pds-wst-v1, the signature validation policy, the preservation evidence policy and the practice statement (published at trustbeat.eu/preservation), the Controller's submissions through the Service, and this agreement are the Controller's complete instructions. In particular the Controller instructs the Processor to keep each record for its full preservation period unless the Controller deletes it earlier (§9).

3.3 The Processor informs the Controller immediately if, in its opinion, an instruction infringes the GDPR or other data protection law.

4. Confidentiality

The Processor ensures that persons authorised to process the personal data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality. Access is limited to the persons who operate and support the Service.

5. Security of processing (Art. 32; Annex 2)

The Processor implements the technical and organisational measures in Annex 2 and keeps them appropriate to the risk. It may change them provided the overall level of security is not reduced.

6. Sub-processors

6.1 The Controller gives general authorisation for the sub-processors listed in Annex 3.

6.2 The Processor informs the Controller by email at least 14 days before adding or replacing a sub-processor that processes personal data under this agreement. The Controller may object on reasonable data-protection grounds within that period; if the parties cannot resolve the objection, the Controller may stop submitting new records. Records already submitted stay preserved under the sub-processors then in place.

6.3 The Processor imposes on each sub-processor, by contract, data protection obligations at least equivalent to those in this agreement, and remains liable to the Controller for its sub-processors.

6.4 Not sub-processors: the qualified time-stamping authorities (they receive only a digest, which is not personal data), and the certification authorities whose OCSP responders and CRL distribution points the Processor queries to validate a signature (each acts as an independent controller of its own status service; the query reveals to it only which of its own certificates is checked).

7. Assistance with data subject rights

7.1 The Processor forwards to the Controller, without undue delay, any request it receives from a data subject concerning data processed under this agreement, and does not answer it itself except to refer the data subject to the Controller.

7.2 The Processor assists the Controller with appropriate technical and organisational measures: the Controller can retrieve, at any time, every record and its full content (GET /v1/signature-preservation, GET /v1/signature-preservation/{id}/package) to answer requests for access or portability. Requests for erasure or restriction before the end of the preservation period are handled as in §9.

8. Assistance with security, breaches, DPIA and consultation (Art. 32–36)

8.1 The Processor notifies the Controller without undue delay, and at the latest within 48 hours, after becoming aware of a personal data breach affecting the Controller's data, with the information Art. 33(3) GDPR requires as far as available, and supplements it as it becomes available.

8.2 The Processor assists the Controller with data protection impact assessments and prior consultations, taking into account the nature of the processing and the information available to it. Its own DPIA of the Service is summarised for the Controller on request.

9. End of the processing; deletion

9.1 Deletion by the Controller. The Controller can delete any of its records at any time (DELETE /v1/signature-preservation/{id} or the portal). The Processor then deletes the Preservation Evidence Object, the stored signatures and the record without undue delay; only the SHA-256 of the Preservation Evidence Object remains, as a leaf of a hash tree shared with other customers' records, which is not personal data. Deletion is final. Where a data subject requests erasure, the Controller decides whether an exception under Art. 17(3) GDPR applies (in particular point (e), legal claims, or point (b), a legal obligation) and, if not, deletes the record.

9.2 At the end of the preservation period of a record, the Processor makes the record's export-import package available to the Controller and deletes the record, its Preservation Evidence Object and the stored signatures 30 days later (Terms §5.6). Encrypted backups made before the deletion are not trimmed on a schedule yet and may still contain it (Annex 2, backup retention).

9.3 If TrustBeat terminates the Service, the Controller receives the package of every record before the stop date (practice statement §7); the records, Preservation Evidence Objects and stored signatures are then deleted, including from backups. Any copy TrustBeat keeps to evidence its operation contains no personal data processed under this agreement.

9.4 Ending the account or subscription does not end the preservation period and does not trigger deletion (Terms §5.6).

10. Information and audits

10.1 The Processor makes available to the Controller the information necessary to demonstrate compliance with Art. 28 GDPR, in particular this agreement, Annex 2, the published preservation documents, and on request a record of the actions performed on the Controller's records.

10.2 The Processor allows for and contributes to audits, including inspections, by the Controller or an auditor mandated by it, bound by confidentiality, with at least 30 days' notice, during business hours, at most once a year unless a breach or a supervisory authority requires more. Each party bears its own costs; audits of the sub-processors are covered by their certifications and reports.

11. International transfers

No personal data processed under this agreement is transferred outside the European Economic Area.

12. Liability, precedence, law

12.1 Liability follows Art. 82 GDPR and, between the parties, the Terms of Service.

12.2 In a conflict between this agreement and the Terms of Service on the processing of personal data, this agreement prevails.

12.3 This agreement is governed by Czech law; the courts of the Czech Republic have jurisdiction, as in the Terms of Service.


Annex 1 — Details of the processing

See §2.

Annex 2 — Technical and organisational measures

Area Measure
Data minimisation The signed files never reach TrustBeat (architecture: the extractor runs on the Controller's side and sends only signatures and digests; the server rejects any CMS that still carries signed content). No account identifier inside the Preservation Evidence Object. Signer data is not written to application logs.
Access control Records are released only to the authenticated account that submitted them (API key or portal session); the public endpoints serve only the evidence record over a digest. Administrative access to servers by SSH key only, limited to the operator.
Encryption in transit TLS for every API and portal connection; TLS from the Processor to its sub-processors where offered.
Encryption at rest Backups encrypted on the server before they leave it (restic, AES-256).
Integrity Preservation Evidence Objects stored byte for byte; their SHA-256 time-stamped by an EU qualified TSA (RFC 4998 evidence record); a record is deleted only by its owner's request or at the end of its period, and every deletion is logged.
Availability and resilience Daily backups to a second EU country (Scaleway, France) in versioned storage whose history production cannot erase; integrity checked weekly, full restore tested every three months; recovery point up to 24 hours. Backup retention: copies on the database server itself are kept 14 days; offsite backups have no fixed retention period yet and are kept until one is introduced, which will then be stated here.
Separation Each record belongs to one account; every query is scoped to the authenticated account.
Logging Structured logs of requests (request id, account id, record id), no signer data; kept 14 days in the central log service (Grafana Cloud). Caller IP addresses recorded with requests are deleted after 90 days.
Vulnerability management Dependencies pinned and audited in CI; operating system updates applied regularly.
Hosting Hetzner Online GmbH data centres in Germany, certified to ISO/IEC 27001:2022.
Organisation Confidentiality commitments; written practice statement, security policy and termination plan, reviewed at least yearly.

Annex 3 — Authorised sub-processors

Sub-processor Location Processing
Hetzner Online GmbH Germany Hosting of the application and database servers
Scaleway SAS France Storage of encrypted database backups

The English text is binding. Machine-readable: api.trustbeat.eu/v1/preservation/documents/dpa-v1.