Data Processing Agreement
Este documento está redactado en inglés. Las traducciones de la interfaz se ofrecen solo por comodidad.
1. Parties and scope
This Data Processing Agreement ("DPA") is between the Customer (controller) and DrillityGroup OÜ, registry code 17467185, Vesivärava tn 50-301, Kesklinna linnaosa, 10152 Tallinn, Harju maakond, Estonia ("Mercovio", processor). It forms part of the Terms of Service and applies when Mercovio processes personal data on the Customer's behalf in providing Mercovio. It is an agreement under Article 28 of the General Data Protection Regulation (GDPR). Terms not defined here have the meaning given in the GDPR. Where this DPA and the Terms conflict on personal data, this DPA prevails.
2. Subject matter, duration, nature and purpose
Mercovio hosts and processes the content that the Customer, its users and its guests add to the Customer's channels, for the duration of the Terms and until deletion under section 11. Annex 1 describes the processing.
3. Instructions
Mercovio processes the personal data only on the Customer's documented instructions, including with regard to transfers outside the EU/EEA. The Terms, this DPA and the Customer's use and configuration of the Service are the Customer's instructions. If Union or Member State law to which Mercovio is subject requires other processing, Mercovio informs the Customer of that requirement before processing, unless that law prohibits it. Mercovio informs the Customer without delay if it believes an instruction breaks data protection law.
4. Confidentiality
Mercovio ensures that people authorised to process the personal data are bound by confidentiality. The owner's operator console shows company names, counts, tokens and money, never customer content.
5. Security
Mercovio implements the technical and organisational measures in Annex 2 and may update them if the level of protection is maintained.
6. Subprocessors
- The Customer gives general authorisation for the subprocessors listed on the subprocessors page.
- Mercovio informs the Customer of an intended addition or replacement at least 30 days in advance, by updating the subprocessors page and by email to the Customer's administrators.
- The Customer may object on reasonable data protection grounds within that period. The parties then look for a solution in good faith. If none is found, the Customer can end the Terms before the change takes effect, and Mercovio refunds fees paid for the time after the end.
- Mercovio imposes data protection obligations on each subprocessor that are equivalent to those in this DPA and remains responsible to the Customer for its subprocessors.
7. Assistance
Mercovio assists the Customer, taking into account the nature of the processing and the information available to it, with requests from data subjects, with security, with notification of personal data breaches, with data protection impact assessments and with prior consultation of a supervisory authority. Channel exports, company exports, deletion and the audit log let the Customer do much of this itself. Assistance is free of charge. Where a request needs substantial work beyond the Service's own tools and beyond what the law requires of a processor, Mercovio may charge its reasonable costs, which it states in advance.
8. Personal data breaches
Mercovio notifies the Customer without undue delay, and in any case within 48 hours after becoming aware of a personal data breach affecting the Customer's personal data. The notice goes to the Customer's administrators by email and describes what is known at the time: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences and the measures taken or proposed. Mercovio updates the notice as more becomes known.
9. Transfers
Mercovio does not transfer the personal data outside the EU/EEA except to subprocessors listed on the subprocessors page. Where such a subprocessor is in a country without an adequacy decision of the European Commission, Mercovio ensures a valid transfer mechanism under Chapter V GDPR, such as the Commission's standard contractual clauses.
10. Audits
Mercovio makes available all information necessary to demonstrate compliance with Article 28 GDPR, including this DPA, the measures in Annex 2 and written answers to reasonable questions. If that is not sufficient, or a supervisory authority requires it, the Customer may audit Mercovio's compliance itself or through an independent auditor bound by confidentiality, once in any 12 months, with at least 30 days' written notice, during business hours and without disrupting the Service or seeing other customers' data. Each party bears its own costs of an audit.
11. Deletion or return
At the end of the Service the Customer can export its channels and records. When the Customer deletes its company workspace, its personal data is removed from Mercovio's live system at once; when the Terms end in another way, Mercovio deletes it from the live system within 30 days. Mercovio's encrypted backups are not edited; they expire within 35 days (daily backups on the server after 14 days, and off-site snapshots after 35 days). Restored data is never used for anything other than recovery. These periods apply to Mercovio's own systems. The prompts and replies of AI requests are also held by the AI subprocessor, Grunden AI AB, under its own privacy policy, as described on the subprocessors page; deleting the workspace does not delete those copies. Apart from those copies, Mercovio keeps personal data after the end only where Union or Member State law requires it, such as billing and accounting records, which the Estonian Accounting Act requires Mercovio to keep for seven years.
12. Liability and law
Liability under this DPA follows the Terms of Service. This DPA is governed by the laws of the Republic of Estonia, and disputes are resolved by Harju County Court (Harju Maakohus) in Tallinn, Estonia. This DPA is written in English. If it is translated, the English version prevails.
Annex 1. Description of the processing
| Data subjects | The Customer's users, invited guests from other companies, and people named in channel content. |
|---|---|
| Personal data | Names, work email addresses, company names, language choice; messages, files and drawings, quotes, approvals and withdrawals with the approver's name, company and time; any personal data in uploaded files. |
| Special categories | Not intended. The Customer does not upload special categories of personal data or data about criminal convictions unless it has a lawful basis and has assessed that the measures in Annex 2 are appropriate for that data. |
| Processing | Storage and encryption, display and file previews, document analysis and text recognition, comparison of revisions, automatic translation, AI answers and briefs at Grunden AI AB in Sweden, searches of public sources by the assistant with a reduced query, email delivery of invitations and notifications, browser and chat app notifications people switch on, backup and recovery. |
| Frequency | Continuous, while the Customer uses the Service. |
| Duration | For the term of the Terms and until deletion under section 11. |
Annex 2. Technical and organisational measures
- Encryption at rest. Message text, translations, document summaries and analyses, quote terms, approval receipts and original files are encrypted with AES-256-GCM before storage, using keys derived with HKDF-SHA-256 from a master key for each company and purpose. Mercovio's servers hold the keys and decrypt content to provide the Service.
- Encryption in transit. The Service is served over HTTPS with HSTS.
- Access control. Every channel resource is checked against the requester's membership on the server. Sessions are HTTP-only cookies. Every change request must come from Mercovio's own origin. Passwords are stored only as scrypt hashes. Sign-in, registration and invitation acceptance are rate limited. Customers can require two-step sign-in.
- Isolation. The application and the file parser run in separate containers as an unprivileged user, with a read-only root file system and all capabilities dropped. The parser has no access to the data volume or the master key.
- Hosting. The application runs on a Hetzner server in Helsinki, Finland.
- Backups and recovery. Encrypted daily backups go to a dedicated Hetzner Storage Box subaccount in Falkenstein, Germany, and expire within 35 days. The master key is never included in a backup. Restores of production backups were tested on 18 November 2026.
- Logging. Error logs record the request method, a redacted path and the error, never request bodies, cookies or message content. The company audit log records who did what and when, is encrypted and is kept for 24 months.
- Operator access. Only the owner and the operators the owner names have access to the production server, through personal SSH keys. The master key is held in a protected file on the server, and its recovery copy is kept in protected custody separate from the backups. People with access are bound by confidentiality.
- Changes. Each release is built from the source repository, tested, and preceded by a backup and a rehearsal of the database migration on a copy.
- Incidents. A suspected incident is assessed, contained and recorded, and affected customers are notified as described in section 8.
Annex 3. Subprocessors
See the subprocessors page.