Data Processing Agreement
Stanje: 05.11.2026
Ovaj tekst postoji samo na engleskom. Obvezujuća je engleska verzija.
This Data Processing Agreement (“DPA”) forms part of the contract between the Customer (“Controller”) and eelik d.o.o. Cazin, Ćoralići, Kovačevići bb, 77220 Cazin, Bosnia and Herzegovina (“Processor”, “eelik”) for the use of fineelik (the “Service”). It implements Article 28 of Regulation (EU) 2016/679 (“GDPR”). Terms defined in the GDPR have the same meaning here.
1. Subject matter and roles
1.1 eelik processes personal data on behalf of the Controller in order to provide the Service. The Controller decides on the purposes and means of processing; eelik acts as processor.
1.2 Subject matter, duration, nature and purpose of the processing, the types of personal data and the categories of data subjects are described in Annex 1.
1.3 For contact and contract data of the Controller’s staff that eelik processes for its own purposes (contract management, billing, support correspondence), eelik is a controller in its own right. This DPA does not apply to that processing.
2. Instructions
2.1 eelik processes personal data only on documented instructions from the Controller, unless required to do otherwise by law to which eelik is subject; in that case eelik informs the Controller before processing, unless that law prohibits it.
2.2 The contract, this DPA and the Controller’s configuration and use of the Service are the Controller’s complete instructions. Further instructions are given in text form. Instructions that go beyond the agreed Service are treated as a change request and may be charged.
2.3 eelik informs the Controller without undue delay if it considers an instruction to infringe data protection law, and may suspend carrying it out until the Controller confirms or changes it.
3. Confidentiality
eelik ensures that persons authorised to process the personal data are bound by confidentiality and process the data only as instructed.
4. Security of processing
4.1 eelik implements the technical and organisational measures described in Annex 2. They are designed to ensure a level of security appropriate to the risk.
4.2 eelik may change the measures as technology develops, provided the level of protection is not reduced.
5. Access by eelik
5.1 Support access in the application. eelik staff access the Controller’s Instance through the user interface only through support access that the Controller’s administrator grants for a limited period (24 hours, 3 days or 7 days) and can end at any time. eelik signs in with a one-time link and is signed out when the period ends. Before the Controller’s first account exists, eelik can access the Instance to set it up. All actions taken with this access are recorded in the Instance’s history.
5.2 Technical access. As operator of the infrastructure, eelik has technical access to the servers, databases, file storage and backups of the Instance, including the ability to decrypt backups. eelik uses this access only where necessary to operate, secure, back up, restore or delete the Instance, to remedy defects, or on the Controller’s instruction.
5.3 eelik is established in Bosnia and Herzegovina. Access under 5.1 and 5.2 takes place from there. Section 8 applies.
6. Sub-processors
6.1 The Controller authorises eelik to engage the sub-processors listed in Annex 3 and published at https://fineelik.com/legal/subprocessors/.
6.2 eelik informs the Controller’s administrators by e-mail of any intended addition or replacement of a sub-processor at least 30 days in advance. The Controller may object in text form within that period on reasonable data protection grounds. If the parties do not find a solution, the Controller may terminate the affected part of the Service with effect from the date of the change.
6.3 eelik imposes on each sub-processor data protection obligations that are no less protective than those in this DPA and remains liable to the Controller for the sub-processor’s performance.
6.4 Services that the Controller itself selects and contracts are not sub-processors of eelik. This applies in particular to an AI provider used with the Controller’s own key, the Controller’s own mail system (SMTP or Microsoft 365), Microsoft Entra ID, Business Central and ELO.
7. Assistance to the Controller
7.1 Data subject rights. The Service provides tools with which the Controller can respond to requests itself: export of the data relating to a person, correction of account data, anonymisation of user accounts and employees, deletion of invoices, and export of all business data. If a data subject contacts eelik directly, eelik forwards the request to the Controller without undue delay and does not answer it itself.
7.2 eelik assists the Controller, taking into account the nature of the processing and the information available to it, with data protection impact assessments, prior consultation and the obligations under Articles 32 to 36 GDPR. Assistance that goes beyond providing existing information may be charged by the hour.
8. International transfers
8.1 The Customer Data is stored on servers in Germany.
8.2 eelik is established in Bosnia and Herzegovina, a country for which the European Commission has not adopted an adequacy decision. Where the Controller is subject to the GDPR, the parties agree on the Standard Contractual Clauses adopted by Commission Implementing Decision (EU) 2021/914, Module Two (controller to processor), which are incorporated by reference, with the Controller as data exporter and eelik as data importer. For the clauses the parties select: Clause 7 (docking clause) applies; Clause 9 Option 2 (general written authorisation) with the notice period in section 6 of this DPA; Clause 11 without the optional independent dispute resolution body; Clause 17 Option 1, the law of Austria; Clause 18 the courts of Vienna, Austria. Annexes I to III of the clauses correspond to Annexes 1 to 3 of this DPA. eelik keeps a transfer impact assessment for access from Bosnia and Herzegovina, reviews it at least once a year and provides it to the Controller on request. The competent supervisory authority under Annex I.C of the clauses is the supervisory authority of the Member State in which the Controller is established.
8.3 eelik transfers personal data to sub-processors outside the European Economic Area only where the conditions of Chapter V GDPR are met. The mechanism per sub-processor is stated in Annex 3.
8.4 eelik has designated a representative in the Union under Article 27 GDPR: Kenan Trgić, Mozartstraße 7, 4063 Hörsching, Austria, hello@fineelik.com.
9. Personal data breaches
9.1 eelik notifies the Controller without undue delay, and where feasible within 48 hours, after becoming aware of a personal data breach affecting the Controller’s data. The notification goes to the Controller’s administrators by e-mail and contains the information available at the time under Article 33(3) GDPR; further information follows as it becomes available.
9.2 eelik takes reasonable measures to contain the breach and to mitigate its effects and supports the Controller in meeting its notification obligations.
10. Deletion and return
10.1 During the contract the Controller can export its data at any time (section 7.1).
10.2 After the contract ends, the Instance remains available in read-only mode for 90 days so that the Controller can export its data. eelik then deletes the Instance, including database and file storage, and confirms the deletion in text form. Backups are deleted within 30 days, when the last backup made before deletion expires. For a free trial the periods in section 3a.4 of the Terms apply instead.
10.3 eelik may retain personal data beyond that only where the law to which eelik is subject requires it, and only for that purpose.
11. Audits
11.1 eelik makes available to the Controller the information necessary to demonstrate compliance with this DPA, in particular a description of the current technical and organisational measures and the list of sub-processors.
11.2 Where this information is not sufficient, the Controller may carry out an audit, itself or through an independent auditor bound to confidentiality, once per year and additionally after a personal data breach, with 30 days’ notice, during business hours and without disrupting operations. Audits are carried out remotely where possible. Each party bears its own costs; eelik may charge its effort beyond one working day per year by the hour.
12. Liability
The limitations of liability in the Terms of Service apply to this DPA as between the parties. The rights of data subjects under the GDPR and, where applicable, the Standard Contractual Clauses remain unaffected.
13. Term and precedence
13.1 This DPA applies for as long as eelik processes personal data on behalf of the Controller.
13.2 In the event of conflict between this DPA and the other parts of the contract, this DPA prevails with regard to data protection. Where the Standard Contractual Clauses apply, they prevail over this DPA.
13.3 Governing law and venue follow the Terms of Service, unless the Standard Contractual Clauses or mandatory law require otherwise.
13.4 This DPA is drawn up in English. The English version is binding; translations are provided for convenience only.
Annex 1: Details of the processing
| Item | Description |
|---|---|
| Subject matter | Provision of fineelik: receiving, reading, reviewing, coding, approving and handing over incoming invoices; depending on the modules booked, payment runs, expenses and travel expenses |
| Duration | Term of the contract plus the 90-day read-only period and the deletion period for backups; for a free trial, the periods in section 3a.4 of the Terms |
| Nature of processing | Storage, automated reading with AI, display, modification by users, transmission to systems chosen by the Controller, export, deletion |
| Purpose | Processing of the Controller’s accounts payable |
| Categories of data subjects | Users of the Service (the Controller’s staff); employees of the Controller (expenses, travel); contact persons of suppliers; suppliers who are natural persons (sole traders); other persons named on documents |
| Special categories | Not intended. The Controller should not upload documents containing special categories of personal data unless necessary |
Types of personal data and retention in the Service
| Data | Personal data contained | Retention in the Instance |
|---|---|---|
| Invoices, document images, line items, account assignments | Supplier, contact persons named on the document | Not deleted automatically. The Controller decides on deletion (recycle bin, then permanent deletion by an administrator) |
| Payments, payment runs, bank files, payment advices | Supplier bank details | As above |
| Supplier master data | Name, address, bank details, VAT ID | As long as the supplier is kept; deactivation by the Controller |
| Employee master data | Name, e-mail, bank details, personnel number, line manager | While active; after deactivation anonymised after a period the Controller configures |
| Expense receipts, trips, mileage log | Employee, destinations, occasions | As invoices; the link to the person ends with the anonymisation of the employee |
| User accounts | Name, e-mail, language, absence, second factor | While active; after deactivation anonymised after a period the Controller configures, or immediately by an administrator |
| Sessions, API keys | Account | Until expiry or revocation |
| Microsoft sign-in (linked accounts) | Name, e-mail, object ID, tenant ID | Deleted with the account |
| History (audit trail) | Account ID, IP address of the caller; name and e-mail in entries on creating or correcting an account | Not limited in time and cannot be changed by the application, so that the history remains complete and verifiable as evidence of who did what (Article 17(3)(b) and (e) GDPR) |
| Client error messages | Account ID | 30 days |
| Document usage journal, daily user counts | Invoice ID, company, month; no names | For the life of the Instance (basis for billing) |
Photos of receipts: location and device metadata (EXIF, XMP, IPTC) are removed from JPEG, PNG and HEIC files on upload.
Annex 2: Technical and organisational measures
Status: 7 October 2026. The list states what is implemented.
1. Separation
- Each Customer has its own Instance: a separate container stack with its own database and its own file storage. Customer Data of different Customers is not stored in a shared database.
- Instances share the server, the reverse proxy and the sub-processors listed in Annex 3.
2. Hosting and physical security
- Servers are operated by Hetzner Online GmbH in a data centre in Germany. Physical security is the responsibility of Hetzner under its own certified information security management. Hetzner’s data centres are certified to ISO/IEC 27001. eelik has concluded Hetzner’s data processing agreement under Article 28 GDPR.
3. Encryption
- In transit: all access to the Instance uses HTTPS (TLS).
- Backups are encrypted before they are stored.
- Credentials and API keys for connected systems are stored encrypted in the database; the key is kept outside the database.
- Storage volumes are not additionally encrypted at rest. This is compensated by encrypted backups, encrypted credentials, a certified data centre and server access limited to named persons. eelik reviews this decision once a year.
4. Access control in the application
- Role-based access: Administrator, Accountant, Approver, Payment Approver, Employee (Expenses), Employee (Travel), Viewer, Operator. Access can be restricted per company.
- A second factor (authenticator app) is mandatory for roles with payment or user administration rights, except during a free trial and for 14 days after the first paid licence that follows it. Alternatively users sign in with the Microsoft account of the Controller’s organisation; multi-factor authentication is then enforced by the Controller’s tenant. Only accounts of the connected tenant are accepted.
- Sessions end after inactivity and after a maximum duration; both are configurable.
- Sign-in attempts are rate-limited per address.
- API keys are limited to delivering and reading documents and expire after at most 365 days.
- Segregation of duties for payments: the person who creates a bank file cannot release it; changes to bank details require a second person.
5. Logging
- The history (audit trail) records changes with account and IP address. The application cannot change or delete entries; database triggers reject such operations.
- Read access to document images and to lists containing bank details of suppliers and employees is logged.
- Exports of the invoice list and data exports are logged.
6. Access by eelik
- Access in the application only through time-limited support access granted by the Controller (section 5.1 of the DPA). The Operator cannot edit invoices or move money, cannot assign the roles Administrator or Operator, and needs a second factor.
- Technical access to servers is limited to named administrators with personal SSH keys; all administrative accounts use a second factor. eelik keeps an internal access list and reviews it every quarter.
7. Availability and recovery
- Daily backup of database and files per Instance, encrypted with age (public-key encryption; the private key is kept by eelik separately from the backups), with a checksum per backup.
- Backups are kept for 30 days on the server and at a second location (Hetzner Storage Box in Helsinki, Finland), transferred by SFTP with a key used only for backups.
- The application master key that encrypts sensitive fields is not part of the backups.
- Restoring is tested before each customer goes live on the target environment.
8. Data minimisation and deletion
- Anonymisation of deactivated user accounts and employees after a configurable period, or immediately by an administrator.
- Deletion of invoices in two steps (recycle bin, permanent deletion with reason and second factor).
- Removal of location metadata from JPEG, PNG and HEIC receipt photos.
- Error reports are stripped of request bodies and cookies before they are sent; session recordings in error reports mask text and inputs.
9. Organisation
- Persons with access are bound to confidentiality.
- eelik has an internal procedure for security incidents and for onboarding and offboarding of persons with access; access is revoked on the day it is no longer needed.
Annex 3: Sub-processors
The current list is published at fineelik.com and reproduced in the document “fineelik Sub-processors”.