Data Processing Addendum
Effective: November 2026 · Version 1.5
Published by Diip Solutions OÜ, registry code 17527757, Tallinn, Estonia.
This Data Processing Addendum ("DPA") forms part of the agreement between Diip Solutions OÜ, operator of the ProcuLink service (the "Processor"), and the customer organisation (the "Controller") for the processing of personal data under the EU General Data Protection Regulation 2016/679 ("GDPR").
1. Definitions
Capitalised terms used but not defined here have the meaning given in the GDPR. "Service" means the ProcuLink platform for business documents such as invoices, purchase orders and delivery notes, as described in the Terms of Service.
2. Roles and scope
This DPA covers the personal data contained in the documents the Controller submits to the Service, in the files the Service makes from them, and in the records the Controller keeps in the Service. For that data the Controller determines the purposes and means of processing, and ProcuLink acts as processor: it processes the data only on the Controller's documented instructions as set out in this DPA and the Terms of Service.
ProcuLink is itself the controller for the personal data it needs to run the customer relationship — website visits, user accounts and sign-in, billing and invoicing records, its own product analytics, error monitoring and security logs, and correspondence. That data is described in the Privacy Policy and is not covered by this DPA.
3. Processor obligations (GDPR Art. 28)
- Process personal data only on documented instructions from the Controller.
- Ensure persons authorised to process personal data are under a duty of confidentiality.
- Implement the technical and organisational measures described in Annex II.
- Use sub-processors only as listed in Annex III, and publish any addition or replacement — with the date it takes effect — at least 30 days before it starts processing Controller data.
- Assist the Controller in responding to data-subject rights requests under GDPR Chapter III.
- Notify the Controller without undue delay after becoming aware of a personal data breach affecting the Controller's data, and give the Controller the information it needs to assess the breach and to meet its own obligations under GDPR Articles 33 and 34 — as soon as that information is available, in stages if necessary.
- After the agreement ends, delete the Controller personal data or keep it available for the Controller to download, at the Controller's choice, on the Controller's written request — unless EU or Member State law requires it to be kept. Data is not deleted automatically when the agreement ends; deletion is carried out on request as described in the Privacy Policy.
- Make available the information necessary to demonstrate compliance with GDPR Art. 28(3).
4. International transfers
Sub-processors are listed, with their locations, on the Subprocessors page. Some of them process Controller personal data outside the EEA: authentication, AI document extraction and mapping suggestions, payments, and email in both directions — including the files the Service emails out on the Controller's instruction — are handled from the United States. Where any sub-processor processes Controller personal data outside the EEA, the relevant Standard Contractual Clauses (Commission Implementing Decision 2021/914) apply.
5. Audits
On reasonable written request and no more than once per calendar year, ProcuLink will provide the Controller with a summary of its security and compliance controls. Onsite audits are not provided as standard; mutual non-disclosure terms apply to any audit information shared.
Annex I — Parties and processing details
Controller
The customer organisation that accepts the Terms of Service.
Processor
Diip Solutions OÜ, registry code 17527757, Uus-Sadama tn 15-2, 10120 Tallinn, Estonia · Contact: legal@proculink.eu
Categories of data subjects
Employees and authorised users of the Controller; people named in the documents the Controller submits, such as contacts at its suppliers and customers; people who send documents to the Controller's ProcuLink address by email; and people in the records the Controller keeps in the Service.
Categories of personal data
The content of submitted documents, whatever personal data they contain: typically contact names, email addresses, phone numbers and postal addresses, and bank account details such as IBAN and payment references. The email address a document was sent from. Records the Controller keeps in the Service. Names and work email addresses of the Controller's users where they are recorded against workspace activity — for example, who checked, changed or sent a document. Credentials the Controller configures for delivering and collecting documents.
The Service is not intended for special categories of personal data (GDPR Article 9), data about criminal convictions or offences, or payroll and personnel records. The Acceptable Use Policy prohibits submitting them.
Purpose and duration
Processing is for the provision of the Service. It runs for the term of the agreement and afterwards until the Controller personal data is deleted, as described in section 3 and the Privacy Policy.
Annex II — Technical and organisational measures
- Encryption in transit: TLS 1.2+ for all client and inter-service traffic.
- Encryption at rest: AES-256-GCM authenticated encryption for the credentials the Controller stores for collecting and delivering documents. Cloudflare R2 server-side encryption for stored document files.
- Access control: Clerk-issued JWT authentication, organisation-scoped session isolation, every database query bound to the authenticated organisation id.
- Logging and monitoring: Sentry error monitoring (EU region), with secrets removed from error reports; structured backend logging; a record of what happened to each document and of changes made in the workspace.
- Backups: The database provider keeps a continuous point-in-time history of the PostgreSQL database, so it can be restored to an earlier moment within a rolling recovery window. Data deleted from the database drops out of that history once it is older than the window; no separate long-term backup copies are kept.
- Personnel: All personnel with access to production data are under written confidentiality obligations.
- Incident response: On becoming aware of a personal-data breach, we notify the Controller without undue delay and share what we know as it becomes available, as set out in section 3.
- Sub-processor management: additions and replacements are published with their effective date at least 30 days in advance (see Annex III).
Annex III — Authorised sub-processors
The current list of authorised sub-processors is maintained at /subprocessors. That page is the notice channel for this Annex: it carries the date the list last changed, any planned addition or replacement, the date that notice was published, and the date it takes effect. The Controller may raise an objection to a planned sub-processor within 14 days of the published notice date, in writing to legal@proculink.eu.