Tvarka Privacy Policy

This English translation is provided for convenience. In case of any discrepancy, the Lithuanian text governs. Lietuviškas tekstas

Tvarka Privacy Policy

This Privacy Policy explains how Tvarka processes personal data.

Last updated: 2026-11-19

1. Data controllers

1.1. The controllers of personal data, according to their respective functions in Tvarka.pro, are Advokato M. Kiškio kontora INVENT (the legal services provider) and Socialiniai algoritmai, UAB (the platform operator). Their roles and contact details are provided in the Contacts section.

1.2. When processing personal data, we comply with Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 (GDPR) and the applicable legal acts of the Republic of Lithuania.

2. Who this Privacy Policy applies to

2.1. The Privacy Policy applies to visitors and users of the Tvarka Platform, as well as to representatives of clients, partners and service providers when they communicate with us or use Tvarka. It also applies to employees, candidates, patients and other persons whose data clients enter in Tvarka. This data is described in Section 15.

2.2. Tvarka Services are provided to businesses only. Tvarka is not intended for minors. Please do not use the Platform if you are under 18 years of age.

2.3. If you submit third parties' personal data while using Tvarka, you are responsible for informing them about this processing and familiarising them with this Privacy Policy.

3. What personal data we process

Tvarka processes personal data to the extent necessary to provide and administer the Platform. The scope of the data may vary depending on the functions used.

3.1. Authentication (login) data

Users sign in with a one-time email link or with an electronic identity (e.g. Smart-ID, Mobile-ID, LT ID, the eID card). When an electronic identity is used, identity is confirmed through the solutions of Mitsoft TSP, SK ID Solutions AS and/or the state enterprise Centre of Registers (Registrų centras). Smart-ID and Mobile-ID certificates are issued by SK ID Solutions AS (Estonia). Depending on the route chosen, Smart-ID and Mobile-ID requests are run by SK ID Solutions AS directly or by Mitsoft TSP. The provider receives the data that the method requires: 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.

We may receive and process the following data provided by the identity verification solution providers: personal code (asmens kodas), first name, surname, country code, certificate data for the audit trail.

3.2. Account and role data

Tvarka stores account and user role information related to a specific legal entity: assigned roles and rights, the date of assignment, the person who made the assignment, and audit records of role changes.

3.3. Legal entity and activity data

Tvarka processes data about the legal entity managed on the Platform and the User's actions on the Platform, e.g.: the legal entity code (company code), name, type (e.g. UAB, MB), compliance settings, participant register records, calendar events, tasks, document metadata.

In some cases, Tvarka may use publicly available or official sources (e.g. register or taxpayer data) to verify or pre-fill legal entity data, if such a function is provided on the Platform.

3.4. Documents and qualified electronic signature (QES) signing data

If you use document storage, document generation or signing, Tvarka processes uploaded documents, generated files and the technical data arising during signing (e.g. the signing time, certificate information, the signing log). QES signing is performed using the document signing infrastructure of Mitsoft TSP, SK ID Solutions AS and/or the state enterprise Centre of Registers.

For a timestamp, the timestamp provider receives only a digest (hash) of the document, never its content. For a web page capture, the public web page the client names is opened on Tvarka's capture server. Its image, its HTML code and the facts of the capture are saved, and the result is sealed with a qualified timestamp. The address of the page is passed to the Internet Archive service "Save Page Now". When a capture location is chosen, the page is opened through a Geonode proxy server in that location.

3.5. Payment and invoice data

Payments for balance top-ups, invoices and other paid actions are processed by the chosen payment service provider. Tvarka may receive payment status, balance, invoice and payment date information needed to grant access and for accounting. Tvarka does not store full payment card or bank account data.

3.6. Technical data and cookies

Tvarka uses essential cookies and similar technologies (e.g. session cookies, CSRF protection) so that the Platform operates securely. If analytics or marketing cookies are used, they are used only with your consent.

4. Purposes of data processing, legal bases and retention

The main processing purposes are set out below. Specific periods may be adjusted taking into account legal requirements and the actual nature of the provision of the Services.

Purpose Data categories Legal basis (GDPR) Retention
Account creation and authentication eID data (personal code, first name, surname), roles Contract (Article 6(1)(b) GDPR) / legitimate interest (Article 6(1)(f) GDPR) Until account deletion; audit records – based on legitimate interest and security needs.
Provision of the Services (register, calendar, document functions) legal entity data, activity records, documents Contract (6(1)(b)) While the Services are provided and for a reasonable time after their provision ends, to the extent necessary; accounting documents – 10 years.
QES signing signing log, certificate data Contract (6(1)(b)) According to document retention periods and audit needs.
Payment administration payment status, balance and invoice information Contract (Article 6(1)(b) GDPR) / legal obligation (Article 6(1)(c) GDPR) Accounting documents – 10 years.
Security, fraud prevention, incident management technical logs, IP, device / session data Legitimate interest (Article 6(1)(f) GDPR) Usually up to 12 months, unless needed longer due to an incident or dispute.
Communication and support email, content of the enquiry Contract (Article 6(1)(b) GDPR) / legitimate interest (Article 6(1)(f) GDPR) Usually up to 2 years from the last contact, unless needed longer due to a dispute.

To improve the Service, we use PostHog in its EU region to count completed email signups, a registered user’s first successful signature and first credited balance top-up. Our server sends only the milestone, time, signup website and a keyed pseudonymous account identifier. It sends no names, email addresses, documents, signature data, payment amounts or payment details. These events are separate from anonymous public-site visits. Legal basis: our legitimate interest in improving the Service (Article 6(1)(f) GDPR).

5. Data recipients (data processors and/or controllers)

Tvarka may disclose personal data to third parties only to the extent necessary to provide the Services, ensure security or fulfil legal obligations.

Main categories of recipients:

  • IT and hosting service providers (e.g. cloud infrastructure);
  • Mitsoft TSP, SK ID Solutions AS (Estonia) and/or the state enterprise Centre of Registers – providers of authentication and QES signing services;
  • Hetzner Online GmbH (Germany) – servers and database in Helsinki, Finland; Cloudflare, Inc. (United States) – network security and storage of files and backups in the EU;
  • Resend (Plus Five Five, Inc., United States) – sending emails;
  • ConvertAPI, UAB (Lithuania) – converting files to PDF and recognising text; Functional Software, Inc. (Sentry, United States) – error monitoring in its EU region, with identifiers removed from reports;
  • the state enterprise Centre of Registers – Population Register data at hiring (clause 15.4); PMC Training and the LearnWorlds training platform – enrolment of employees in courses (clause 15.2);
  • Geonode and the Internet Archive – web page capture (clause 3.4);
  • payment service providers (e.g. Stripe or another service provider specified on the Platform);
  • professional advisers (e.g. lawyers, auditors), where necessary to protect legitimate interests or under legal acts;
  • state authorities and courts – where required by law or for dispute resolution.

We conclude agreements with data processors ensuring compliance with GDPR requirements. The sub-processors that receive the data we process on behalf of clients are listed in Annex 3 of the Data Processing Agreement.

6. Cookies and other technologies

6.1. Essential cookies. Tvarka does not use additional (analytics or marketing) cookies. Only essential cookies set by infrastructure or identity service providers may be used for the operation and security of the Platform (e.g. bot protection, traffic routing, session maintenance during identity verification). These cookies are processed on the basis of our legitimate interest (GDPR 6(1)(f)).

6.2. Optional cookies. Tvarka does not use analytics or marketing cookies and does not ask for consent for such cookies.

6.3. List of cookies used

Cookie Provider Purpose Duration
__cf_bm Cloudflare Bot management / abuse protection (Cloudflare Bot Management / Bot Fight Mode). Up to ~30 min after inactivity
_cfuvid Cloudflare Rate limiting / web application firewall (WAF) rules: helps distinguish visitors when several users share the same IP address (NAT). Per Cloudflare configuration (usually session)
cf_clearance Cloudflare Proof that a Cloudflare security check has been passed successfully. Per Cloudflare configuration
__cflb Cloudflare (if applicable) Assignment of sessions to the same origin server (Cloudflare Load Balancer session affinity). From a few seconds up to 24 h (per settings)
X-Oracle-BMC-LBS-Route OCI (Oracle Cloud Infrastructure) (if applicable) OCI Load Balancer session assignment (session stickiness) to a backend server. Per OCI configuration
HCLBSTICKY Hetzner (if applicable) Hetzner Cloud Load Balancer session assignment (session stickiness) to a backend server. Per Hetzner configuration
sessionid Mitsoft TSP (tsp.mitsoft.lt) (if applicable) Session cookie required for the user to stay signed in in the eID environment (signing / identity verification). Until the browser is closed (session)
cookieyes-consent LT ID (ltid.lt) (if applicable) Remembers the user's cookie consent preferences on the LT ID website. 1 year
_GRECAPTCHA LT ID (ltid.lt) (if applicable) Protection against bots and abuse on the LT ID website. 6 months

Note: "if applicable" means that the cookie is set only if the relevant infrastructure or identity service is used in the specific environment, taking into account the user's settings.

7. Data transfers to third countries

7.1. Tvarka may use service providers that process personal data outside the European Economic Area. In such cases, we ensure appropriate safeguards (e.g. the European Commission's standard contractual clauses, adequacy decisions or other measures provided for in the GDPR).

8. Security of personal data

8.1. We apply technical and organisational measures designed to protect personal data against unauthorised access, loss or disclosure.

8.2. In the Tvarka architecture, the personal code is processed securely – an HMAC-SHA256 hash identifier is used for indexing, and encrypted data is stored separately (with keys managed separately) to reduce risk.

8.3. Although we make reasonable efforts, no method of data transmission or storage is 100% secure.

9. Your rights

You have the rights established by the GDPR: the right to access your data, to rectify or erase it, to restrict processing, to object to processing, the right to data portability (where applicable) and the right to lodge a complaint with a supervisory authority.

To exercise your rights, contact us at the email address specified in Section 12. We will respond no later than within 1 month, unless the GDPR allows the period to be extended.

The supervisory authority in Lithuania is the State Data Protection Inspectorate (Valstybinė duomenų apsaugos inspekcija, VDAI), L. Sapiegos g. 17, 10312 Vilnius, email ada@ada.lt.

10. Changes to the Privacy Policy

10.1. We may update this Privacy Policy. Updates are published on the Platform. We may additionally inform you about material changes.

11. Responsibility and account security

11.1. Tvarka users are responsible for the security of their devices, electronic identification means and actions on the Platform. We recommend using up-to-date software and taking appropriate cybersecurity measures.

12. Data controllers and contact details

The Tvarka.pro project is operated by Advokato M. Kiškio kontora INVENT and Socialiniai algoritmai, UAB. Their roles, legal entity codes, VAT payer codes and addresses are provided on the About us page.

General Tvarka.pro contact details and the enquiry channel are provided on the Contact page.

13. Tvarka Sign Free personal plan

13.1. This section applies when the free personal plan of the Tvarka Sign app is used by a natural person without a Tvarka account. By way of derogation from clause 2.2, to this extent the service is also provided for personal (non-business) purposes. The controller of the processing described in this section is the platform operator, Socialiniai algoritmai, UAB.

13.2. The following data is processed:

  • device registration data: a randomly generated device identifier and access token, technical logs and the IP address (for security, rate limiting and abuse prevention);
  • signing data: the qualified certificate data read from the eID card during signing (first name, surname, personal code, certificate information) and the signing log, as described in Section 3.4;
  • the monthly limit accounting record: a hash (HMAC) value of the personal code derived from the certificate, the calendar month and the number of signatures – the personal code is not stored in plain text for limit accounting;
  • a notification (push) token, if notifications are enabled on the device.

13.3. The PDF, ADOC or ASiC-E document being signed is uploaded to the platform solely to perform the signing operation and is not used for any other purposes. The document and its signed version are deleted once the app confirms the download of the signed document, and in any case no later than 48 hours after upload.

13.4. Legal bases: provision of the service – contract (Article 6(1)(b) GDPR); limit accounting, rate limiting and abuse prevention – legitimate interest (Article 6(1)(f) GDPR); marketing notifications in the app – only a separate consent (Article 6(1)(a) GDPR), which is off by default and can be withdrawn at any time in the app settings.

13.5. Recipients: qualified timestamping service providers in the European Union (e.g. ACCV, Spain) – only a cryptographic digest (hash) is transmitted in the timestamp request, not the content of the document; certificate validity (OCSP) requests are made to the qualified trust service provider that issued the certificate; Google Firebase Cloud Messaging on Android and Apple Push Notification service (APNs) on iOS are used for notification delivery (if enabled); as well as the IT and hosting service providers referred to in Section 5.

13.6. To exercise your rights, contact us using the details in Section 12 or the deletion request below. We may need additional information to identify the relevant records. Uninstalling the app does not automatically delete server records, revoke device access or submit a deletion request.

13.7. Tvarka Sign data deletion request

The app's reset removes its local setup and history and requests revocation of stored device or account access. This does not submit a request to delete the account, documents or other server records.

To submit a server data deletion request, write to pagalba@tvarka.pro, enter "Tvarka Sign data deletion" in the subject line and state that you used the free personal plan. If the device identifier is still visible in the app, include it with the request. We may ask for additional information to link your identity to the requested records.

Upon receiving a justified request, we remove or de-identify the data linked to the device registration that is no longer needed. Documents and their signed versions are deleted within the period set in clause 13.3. Technical security logs are usually kept for up to 12 months, support enquiries – for up to 2 years, and data that we must retain due to legal obligations, security, fraud prevention or a dispute remains only for the relevant period specified in Section 4.

14. Tvarka Sign mobile accounts and Android services

14.1. You can also use an email account for personal documents or for company workspaces to which you have access. Personal use does not require a company account. We process the account email, name, authentication and device-access records, language and workspace permissions to provide the service and protect access. The purposes, legal bases and retention rules in Section 4 apply. The platform operator is the controller for personal account administration; company documents remain subject to the company's instructions and applicable retention duties.

14.2. We process files and photos you submit, prepared PDFs, signed files and signing evidence. Depending on the action, evidence includes the signer, authentication and consent, typed or drawn mark, document version and fingerprint, method, time and IP address. Invitations also use recipient names and email addresses, and phone numbers when SMS is selected. Company users and signing recipients receive the files and evidence for which they have access. Personal and company cloud documents are retained for continued access and recovery; the accountless temporary-file rule in clause 13.3 does not apply to them.

14.3. Where device recognition is available, the server stores protected signing details after a completed qualified signature and a device-bound reference for later signatures. Device references expire after one year without use. The Mobile-ID phone directory is separate and expires after two years without use. Removing remembered details in the app prevents further use of the device reference; it does not erase completed signed documents or their evidence.

14.4. Android QR scanning uses Google code scanner. Camera frames and recognition stay on the device. Google receives device and app information, identifiers, performance and feature/error events for diagnostics and usage analytics; automatic zoom also produces scanning-session and zoom data. See Google's scanner data disclosure and Google's privacy policy.

14.5. Android notifications use Firebase Cloud Messaging, which processes installation identifiers and delivery tokens. Turning off notification display does not itself prevent the Google service from creating an installation identifier. Service notifications and optional marketing notifications have separate controls; marketing is off by default. See Firebase's data disclosure. Browser-cookie settings do not control these native Android services.

14.6. You can request account and data deletion in a browser, without the app. Sign in, confirm your identity again and submit the request. We review it before erasure, including company records, signing evidence and retention duties. Submission produces a receipt; it does not immediately disable the account or erase data. If you cannot sign in, or used the app without an account, use the support link on that page. Do not send PINs, passwords or document copies.

15. Data that clients process in Tvarka Sauga, Tvarka Formos, Tvarka HR and on tablets

15.1. Roles. A company or other organisation that processes the data of its employees, candidates, patients, clients or other persons through Tvarka is the controller of that data (in this Section, the client). Socialiniai algoritmai, UAB processes this data as a processor. The data is processed only on the client's instructions and under the Data Processing Agreement. The client decides the purpose, the legal basis and the retention period. The client informs the persons concerned. To use your rights, contact the client, such as your employer, your healthcare provider or another organisation. If you write to us, we pass your request to the client and help it answer.

15.2. Tvarka Sauga (occupational safety and health). Employee data is processed: name, surname, email address, phone number, position, personnel number, language, and the start and end dates of employment. The personal identification code is processed if the client enters it or if it is taken from a qualified signature. Records of safety briefings, test questions and answers, issues of personal protective equipment, certificates, permits to work, violations, events, accidents and inspections are processed too, with photos and signed documents. A health check record holds the date of the check, the valid-until date, the risk factors, the conclusion (fit, fit with limits or unfit) and a scan of the medical form. No diagnosis is stored. Sauga data is seen by the client's Vadovas (head of the company), an Atstovas (representative) with full rights, the responsible persons the client appoints and the specialists of a partner the client connects. An employee sees their own records. Tvarka platform roles do not open Sauga data. When the client orders PMC Training courses, the employee's name, surname and email address are passed to the LearnWorlds training platform, where the PMC Training courses run. The course, its price and the client's name and company code are passed with them. Each month PMC Training receives a statement with the client's name and company code, the employee's name, surname and email address, the course, the price and the enrolment date. The retention period of Sauga records is shown in the client's settings (by default 10 years). When an employee leaves, their access links stop working, and the signed records remain.

15.3. Tvarka Formos. The data of the person who fills in a form (a patient, client or visitor) is processed: name, surname, phone number, email address, language, the time of the visit, the form answers, attached files and photos, the drawn signature and the signing evidence. If a guardian or another representative fills in the form for the person, their name, surname and relation to the person are processed. The personal identification code is stored only as a hash. It is used to recognise the person when they come back to the same client. New forms are then prefilled with the answers of the previous visit. Form answers are stored encrypted on the server. The client may connect its own system, from which forms are prefilled, and name addresses to which the data of a completed form is passed. Data is then passed between Tvarka and the client's system. Invitations, reminders and one-time codes are sent by SMS or by email. A link stops working one day after the visit, or after 14 days when no visit time is given.

15.4. Tvarka HR. Candidate data is processed: name, surname, email address, phone number, the position applied for, the CV and the client's notes. Candidate data and files are deleted automatically 6 months after the candidate is added. If the candidate agreed that their data may be used for other selections, it is deleted after 3 years. The client may change the end date of this period. A reminder is sent to the client's Vadovas a week before deletion. Employee data is processed: name, surname, date of birth, declared place of residence, contact details, the terms of the employment contract (pay, working hours, place of work, contract type and term, trial period), leave balances, requests, work schedules, timesheets, business trips and their expense documents, changes of terms, the end of employment and disciplinary cases. During hiring the personal identification code is stored encrypted. When the hiring ends, it is removed from the hiring record. During hiring, on the client's instruction, data from the Population Register is obtained by the personal identification code through the state enterprise Centre of Registers: name, surname, date of birth and declared place of residence. The sex that the register returns is not stored. No such lookup is made for candidates. Each lookup is recorded in the audit log: the client, the person who made it, its purpose and the last four digits of the personal identification code. An answer received within the last 24 hours is reused for the same client. HR data is seen by the client's Vadovas, an Atstovas with full rights and the persons whose positions the client gave the relevant HR duty. Pay is seen only by persons who hold the pay duty. An employee sees their own data. Colleagues see only the dates of absence, without the type of leave.

15.5. Health data. Health check records (Tvarka Sauga), requests for sick leave and for pregnancy and maternity leave and extra leave days (Tvarka HR), and medical forms and health questionnaires (Tvarka Formos) are health data or can reveal it. They are special categories of personal data (Article 9 GDPR). For sick leave only the certificate number is stored. No diagnosis is stored. The client ensures the legal basis for processing this data (Article 9(2) GDPR).

15.6. Signing on a tablet. On a tablet a person signs with a signature drawn by hand. Pen data is recorded with the image of the signature: the position and time of each point, and the pressure and tilt where the device reports them. Device details (operating system, browser, screen, app version) are recorded too, and the tablet's location where the tablet's browser allows it. Pen data is bound to the fingerprint of the document being signed and to the signing event. It is encrypted (AES-256-GCM) with a key that only a private key kept off the server can unlock. The server encrypts pen data and cannot read it. The encrypted pen data is embedded in the signed PDF document and kept with the signing evidence. It is opened only for an expert examination if a signature is disputed. The client may add its own public key. The client can then open the pen data too. The signing evidence also holds the tablet's name, the client's employee who ran the tablet, the IP address, the browser, the time zone, the number of points and the duration of the signature. Pen data can be biometric data where it is used to identify a person (Article 9 GDPR). Tvarka keeps it only as sealed evidence and does not identify anyone by it. Pen data is kept for as long as the signed document is kept.

15.7. SMS codes. One-time codes and notices for the employee page, for forms and for signing are sent by SMS from a Tvarka phone number. The message is delivered by a mobile network operator. The operator receives the phone number and the text of the message. A code has six digits, is valid for 10 minutes and is stored on the server only as a hash. In the signing evidence the phone number is shown masked.

15.8. Retention, export and deletion. Unless this Section says otherwise, data is kept for as long as the client keeps it in Tvarka. The client can export its data at any time and free of charge. Tvarka Sauga exports the signed documents, the journals and the records, Tvarka Formos the signed forms and their data, and Tvarka HR the work schedules, timesheets and reports. When the contract ends, the data is returned and deleted under the Data Processing Agreement.