Data processing agreement
Version 2026-11-14
This data processing agreement (the Agreement) is made between the company or other organisation that uses Tvarka services on tvarka.pro as controller (the Client), and Socialiniai algoritmai, UAB, company code 304068578, VAT number LT100019931317, registered office at M. Valančiaus g. 1A-21, LT-03155 Vilnius, Lithuania, as processor (Tvarka). The Agreement forms part of the Tvarka Terms of Use (the Terms) and is accepted with them. It sets out the terms that Article 28(3) of Regulation (EU) 2016/679 (the GDPR) requires.
Contents: 1. Scope and definitions. 2. Details of the processing. 3. Instructions. 4. The Client's duties. 5. Confidentiality. 6. Security. 7. Sub-processors. 8. Assistance. 9. Personal data breaches. 10. Export, return and deletion. 11. Audits. 12. Transfers. 13. Liability. 14. Term and changes. Annex 1, details of the processing. Annex 2, security measures. Annex 3, sub-processors.
1. Scope and definitions
1.1. The Agreement applies to the personal data that Tvarka processes on behalf of the Client in providing Tvarka Sign, Tvarka Sauga, Tvarka Formos, Tvarka HR and tablet signing (Client Personal Data).
1.2. Words defined in the Terms have the same meaning in the Agreement. Controller, processor, personal data, processing, data subject, personal data breach and supervisory authority have the meanings given in the GDPR. The standard contractual clauses are those adopted by Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
1.3. If the Client is itself a processor for another controller, Tvarka acts as its sub-processor. The Client ensures that its instructions are authorised by that controller.
1.4. The personal data that Tvarka processes for its own purposes (Accounts, billing, security, support and its legal duties) is processed by Tvarka as a controller under the Privacy Policy. The Agreement does not apply to it.
2. Details of the processing
2.1. Annex 1 sets out the subject matter and duration of the processing, its nature and purposes, the types of personal data and the categories of data subjects.
3. Instructions
3.1. Tvarka processes Client Personal Data only on documented instructions from the Client, including with regard to transfers to a third country or an international organisation. This rule does not apply where EU or Member State law to which Tvarka is subject requires such processing. In that case Tvarka informs the Client of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.
3.2. The Client's documented instructions are the Terms, this Agreement and the Client's actions and settings in the Services. Examples are uploading and deleting documents, inviting signers, turning on SMS codes, adding employees and candidates, a Population Register lookup at hiring, publishing forms, connecting the Client's own system and registering a tablet. Further instructions are given in writing and must be consistent with the Terms. Tvarka may charge reasonable costs for instructions that require work outside the Services.
3.3. Tvarka informs the Client without delay if, in its opinion, an instruction infringes the GDPR or other EU or Member State data protection provisions. Tvarka may suspend the processing concerned until the Client confirms or changes the instruction.
4. The Client's duties
4.1. The Client is responsible for the lawfulness of the processing it instructs. The Client ensures a legal basis for the processing and informs the data subjects as the GDPR requires. The data subjects are the Client Users, signers, employees, candidates, patients and form fillers.
4.2. The Client processes special categories of personal data (such as health check records, requests for sick leave and for pregnancy and maternity leave, and medical forms) and personal identification codes only on a ground under Article 9(2) GDPR and the applicable law. The Client assesses whether the measures in Annex 2 are appropriate for such data. The Client carries out a data protection impact assessment where Article 35 GDPR requires one.
4.3. The Client gives correct details of signers, employees and candidates. The Client keeps its Accounts, access codes and tablets secure, and its own private key for pen data if it uses one.
4.4. The Client decides which of its employees, responsible persons and partner specialists have access to the data, and removes access that is no longer needed in good time.
5. Confidentiality
5.1. Tvarka ensures that persons authorised to process Client Personal Data have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
5.2. Tvarka staff access Client Personal Data only where needed to provide the Services, to give support that the Client asks for, to keep the Services secure or to comply with the law. Tvarka platform roles do not open Tvarka Sauga data.
6. Security
6.1. Tvarka takes the technical and organisational measures required by Article 32 GDPR. They are described in Annex 2.
6.2. Tvarka may update the measures as technology develops, provided that the overall level of security does not decrease.
7. Sub-processors
7.1. The Client gives Tvarka a general written authorisation to engage sub-processors. The sub-processors engaged on the date of this version are listed in Annex 3.
7.2. Tvarka informs the Client of any intended addition or replacement of a sub-processor at least 30 days in advance, by email or in the Services, and updates Annex 3. If a sub-processor must be replaced urgently to keep the Services running or secure, Tvarka may replace it at once and informs the Client as soon as possible.
7.3. Within the notice period the Client may object to a change on reasonable data protection grounds. The parties then discuss the objection in good faith. If they find no solution, the Client may end the Terms before the change takes effect. Tvarka refunds any unused prepaid balance.
7.4. Tvarka imposes on each sub-processor, by contract, the same data protection obligations as those in this Agreement, in particular sufficient guarantees to implement appropriate technical and organisational measures. Where a sub-processor fails to fulfil its data protection obligations, Tvarka remains fully liable to the Client for the performance of those obligations, subject to section 13.
8. Assistance
8.1. Taking into account the nature of the processing, Tvarka assists the Client by appropriate technical and organisational measures, insofar as this is possible, in responding to requests from data subjects to exercise their rights. In the Services the Client can find, export and delete documents and their evidence. The Client can delete candidate data at any time.
8.2. If Tvarka receives such a request about Client Personal Data, it passes the request to the Client without undue delay and does not answer it itself, unless the Client authorises it or the law requires it.
8.3. Taking into account the nature of the processing and the information available to it, Tvarka assists the Client in meeting its obligations under Articles 32 to 36 GDPR. These are the security of processing, the notification of personal data breaches, data protection impact assessments and prior consultation.
8.4. Tvarka may charge reasonable costs for assistance beyond what the Services and this Agreement provide, unless the assistance is needed because of Tvarka's breach.
9. Personal data breaches
9.1. Tvarka notifies the Client without undue delay after becoming aware of a personal data breach affecting Client Personal Data.
9.2. The notice describes, as far as then known, the nature of the breach, including the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Where not all information is available at once, it is provided in phases without undue further delay.
9.3. Tvarka takes reasonable steps to contain the breach and limit its effects. A notice under this section is not an admission of fault or liability.
10. Export, return and deletion
10.1. While the Terms are in force, the Client can export and delete its data in the Services at any time and free of charge. Tvarka Sign documents and their evidence are downloaded. Tvarka Sauga exports the signed documents, the journals and the records. Tvarka Formos exports the signed forms and their data. Tvarka HR exports the work schedules, timesheets, payroll files and reports. A deleted Tvarka Sign document stays in the trash for 7 days and is then deleted with its evidence.
10.2. Candidate data is deleted automatically when the keeping period set by the Client ends (by default 6 months, or 3 years with the candidate's consent). The Client sets the keeping period of other Client Personal Data.
10.3. Within 30 days after the Terms end, the Client may ask for a copy of Client Personal Data in the formats the Services use. Within 90 days after the Terms end, Tvarka deletes Client Personal Data, unless EU or Member State law requires it to be stored.
10.4. Copies in backups are deleted as the backups are overwritten in their normal cycle. Until then they stay encrypted, are used for no other purpose, and are restored only to recover the Services after an incident.
11. Audits
11.1. Tvarka makes available to the Client all information necessary to demonstrate compliance with Article 28 GDPR, including this Agreement, Annex 2 and answers to reasonable written questions.
11.2. Where that information is not enough, Tvarka allows for and contributes to audits, including inspections, by the Client or by an independent auditor mandated by the Client. The Client gives at least 30 days' notice. An audit takes place during business hours, at most once a year, unless a supervisory authority requires it or a personal data breach justifies it. It is carried out under a duty of confidentiality and at the Client's cost. It must not expose other clients' data or put the security of the Services at risk.
11.3. For sub-processors, Tvarka provides their audit reports or certifications where available, in place of an inspection of their premises, unless a supervisory authority requires more.
12. Transfers
12.1. Tvarka stores Client Personal Data in the European Union. The servers are in Helsinki, Finland, and files are stored in Cloudflare R2 storage within the EU jurisdiction.
12.2. Some sub-processors may process Client Personal Data outside the European Economic Area, as Annex 3 shows. Tvarka ensures that each such transfer complies with Chapter V of the GDPR. It relies on an adequacy decision, including the EU-U.S. Data Privacy Framework for certified recipients, or on the standard contractual clauses with additional measures where needed. The Client authorises these transfers.
13. Liability
13.1. Liability under this Agreement is governed by Section 9 of the Terms. The limits of Tvarka's liability set there apply, as far as the applicable law permits, to all claims under this Agreement and the Terms together.
13.2. This section does not limit the rights of data subjects under Article 82 GDPR.
14. Term and changes
14.1. The Agreement applies for as long as Tvarka processes Client Personal Data.
14.2. If the Agreement and the Terms conflict on the processing of Client Personal Data, the Agreement prevails.
14.3. Tvarka may change the Agreement as Section 13 of the Terms provides. Changes to Annex 3 follow section 7.
14.4. The Agreement is governed by the law of the Republic of Lithuania. Disputes are resolved as Section 14 of the Terms provides. The Agreement is published in Lithuanian and English. If the texts differ, the Lithuanian text prevails.
14.5. Notices under the Agreement go to Tvarka at info@tvarka.pro, and to the Client at the email addresses of its Vadovas (head of the company) and of the Client Users who manage the Client's settings.
Annex 1. Details of the processing
Subject matter: the provision of Tvarka Sign, Tvarka Sauga, Tvarka Formos, Tvarka HR and tablet signing to the Client under the Terms.
Duration: the term of the Terms, and after it until deletion under section 10.
Nature: collection, recording, organisation, storage, conversion and compression of files, text recognition, adding signature marks, signing summaries and timestamps, encryption of pen data, retrieval, consultation, use, disclosure by transmission (emails, SMS, delivery of signed files, transfer of data to a system the Client connects and to training the Client orders), restriction and erasure.
Purposes: storing and signing the Client's documents; running occupational safety and health processes (Tvarka Sauga); filling in and signing forms (Tvarka Formos); running candidate selection, hiring and employment (Tvarka HR); tablet signing; sending invitations, reminders, codes and notices; keeping signing evidence; keeping the Services secure and preventing abuse; and support.
Categories of data subjects: Client Users; signers; the Client's employees; candidates; patients, clients, visitors and other form fillers, and their guardians and representatives; persons named in the Client's documents.
Types of personal data:
- Tvarka Sign: the signer's name, email address, phone number (when SMS codes are used), language, IP address, browser, time zone, the results of access code and SMS code checks, the consent given, the typed or drawn signature image, the time of signing and the reason for declining. For a qualified signature, the data in the qualified certificate (name, personal identification code, certificate number and issuer) and the signing log;
- Tvarka Sauga: the employee data listed in clause 15.2 of the Privacy Policy, including health check records;
- Tvarka Formos: the form filler data listed in clause 15.3 of the Privacy Policy, including form answers and attached files;
- Tvarka HR: the candidate and employee data listed in clause 15.4 of the Privacy Policy, including Population Register data obtained at hiring;
- tablet signing: the pen, device and signing evidence data listed in clause 15.6 of the Privacy Policy;
- document content: any personal data in the documents the Client uploads, as the Client decides;
- evidence data: document fingerprints (SHA-256), reference codes and timestamps.
Special categories of personal data: health data in Tvarka Sauga health check records, in Tvarka HR requests for sick leave and for pregnancy and maternity leave, and in Tvarka Formos medical forms. Pen data can be biometric data where it is used to identify a person. Tvarka does not use it to identify anyone. The Client may include other special categories in documents under clause 4.2.
Frequency: continuous, while the Client uses the Services.
Retention: as the Client decides, subject to section 10. Candidate data is deleted automatically under clause 10.2.
Location: the European Union, with the transfers shown in Annex 3.
Annex 2. Technical and organisational security measures
- Hosting in the EU. Servers and the database run in a Hetzner data centre in Helsinki, Finland. Files are stored in private Cloudflare R2 storage within the EU jurisdiction.
- Encryption in transit. Traffic between browsers and the Services is encrypted with HTTPS. Connections between Cloudflare and Tvarka's servers are encrypted and authenticated with an origin certificate.
- Encryption at rest. Stored files are encrypted by the storage provider. Database backups are encrypted and kept in a separate private storage bucket in the EU, with separate credentials. Personal identification codes are stored encrypted, and searches use an HMAC-SHA256 hash with a separately managed key. Tvarka Formos answers are stored encrypted.
- Pen data. A fresh AES-256-GCM key is created for each signature. It is encrypted with an RSA-OAEP public key whose private key is kept off the server. The server cannot read pen data. Pen data is bound to the document's SHA-256 fingerprint and to the signing event.
- Access control for users. Sign-in is by an electronic identity or a one-time email link. A fresh identity check may be asked for before sensitive actions. Sessions expire. Roles and duties limit what each Client User can see and do. Tvarka Sauga data is seen only by the Client's administrators, responsible persons and the specialists of a connected partner. In Tvarka HR, pay is seen only by persons who hold the pay duty.
- Tablets. A tablet is registered with a one-time code. Its credential is stored only as a hash and can be revoked at any time. A tablet sees only its own open signing session. The screen is cleared when a session ends.
- Access control for staff. Access to production systems is limited to authorised persons and uses key-based authentication, firewalls and private networks. Tvarka staff access Client Personal Data only as clause 5.2 allows.
- Signing evidence. Evidence records are append-only and linked by a hash chain. Each signing event gets a timestamp from an independent timestamp authority, and each completed document gets a document timestamp, so any later change is visible.
- Codes and links. Signing links are long random tokens, personal to one person and one document, and they expire. Access codes and SMS codes are stored only as hashes. An SMS code is valid for 10 minutes and allows five tries.
- Abuse prevention. Rate limits apply to invitations, code checks, SMS sends and tablets. Cloudflare protects the network.
- Data minimisation. No diagnosis is stored in health check records or sick leave requests. The sex returned by the Population Register is not stored. When a hiring ends, the personal identification code is removed from the hiring record. Notices to employees carry no health, family, pay or case details. Error reports are cleaned of identifiers (email addresses, phone numbers, IP addresses, personal codes, tokens and name fields) before they leave Tvarka's servers.
- Audit logs. Every Population Register lookup and every data export is recorded in the audit log.
- Backups and recovery. The database is copied continuously to a standby server and archived every hour to encrypted storage. Restores are tested. An encrypted copy is also kept in Lithuania.
- Monitoring. Errors, uptime and server health are monitored, with alerts. Personal data breaches are handled as section 9 provides.
- Development. Changes are tested before release, including automated tests of the access boundaries between workspaces.
Annex 3. Sub-processors
The sub-processors engaged on the date of this version are:
- Hetzner Online GmbH, Germany. Servers and database. Location: Helsinki, Finland (EU).
- Cloudflare, Inc., United States. Network security and delivery of the Services, storage of files and database backups (R2). Location: files and backups in the EU; network traffic in Cloudflare's data centres, including outside the EEA. Safeguards: the standard contractual clauses or the EU-U.S. Data Privacy Framework.
- Resend (Plus Five Five, Inc.), United States. Sending emails (invitations, reminders, sign-in links, signed files, notices to employees). Safeguards: the standard contractual clauses or the EU-U.S. Data Privacy Framework.
- GatewayAPI (ONLINECITY.IO ApS), Denmark. Sending SMS codes and SMS notices. Location: EU. Text messages reach the person through mobile network operators.
- ConvertAPI, UAB, Lithuania. Converting files to PDF, compressing large PDFs and recognising the text of scanned documents. Location: EU and EEA.
- Functional Software, Inc. (Sentry), United States. Error monitoring, with identifiers removed before sending (Annex 2, point 11). Location: EU region. Safeguards: the standard contractual clauses or the EU-U.S. Data Privacy Framework.
- Mitsoft TSP, Lithuania. Qualified signatures and identity checks with Smart-ID, Mobile-ID, LT ID, ZealiD and SimplySign, when a signer uses one of them. Location: EU.
SK ID Solutions AS, Estonia, issues the Smart-ID and Mobile-ID certificates and runs the requests of these methods. It receives the data the method needs: the personal identification code or a certificate or account identifier, for Mobile-ID the phone number, and for signing the digest of the data to be signed. For a qualified signature, the trust service provider that issued the signer's certificate acts under its own terms with the signer.
The state enterprise Centre of Registers (Registrų centras) provides Population Register data at hiring on the Client's instruction. It receives the personal identification code. The Centre of Registers acts on its own legal basis and under its agreement with Tvarka.
When the Client orders PMC Training courses, employee data is passed to PMC Training and to the LearnWorlds training platform to the extent set out in clause 15.2 of the Privacy Policy. When the Client connects a Tvarka Sauga partner, the partner's specialists get access to the Client's Tvarka Sauga data. When the Client connects its own system to Tvarka Formos, data is passed to that system. These recipients receive data on the Client's instruction.
Timestamp authorities receive only a document fingerprint (a SHA-256 hash) and no personal data, so they are not sub-processors.
Stripe processes payment data for Tvarka's own billing, as the Privacy Policy explains. It receives no documents and no Client Personal Data.