Data processing agreement
How ZenDev, as processor, handles your employees’ data.
Draft version
Version 1.0, 1 November 2026
This data processing agreement is the agreement referred to in Article 28 of the General Data Protection Regulation (Regulation (EU) 2016/679, "GDPR"). It applies between:
- the customer: the business or organisation that has a biller account, as controller; and
- ZenDev: Strategix CommV, trading as ZenDev, Weertstraat 15, 3800 Sint-Truiden, Belgium, enterprise number 1016.537.036, Register of Legal Entities (RPR/RPM) Antwerp, Hasselt division, as processor.
It forms part of the general terms and conditions of biller (biller.be/terms) and is accepted electronically when signing up.
Article 1. Definitions
1.1 Terms such as personal data, processing, controller, processor, data subject, personal data breach and supervisory authority have the meaning given to them in the GDPR.
1.2 Customer personal data means the personal data that ZenDev processes for the customer when providing biller, as described in Annex 1. Sub-processor means another processor that ZenDev engages for the processing of customer personal data.
Article 2. Subject matter and roles
2.1 ZenDev processes the customer personal data only to provide biller as described in the general terms and conditions and in Annex 1.
2.2 The customer determines the purpose and the means of the processing. The customer is responsible for ensuring that the processing is lawful, that it informs the data subjects (its own customers, suppliers and their contact persons), and that there is a data protection impact assessment where one is required.
2.3 For the data of its own customer relationship (account, subscription, invoicing and support), ZenDev is itself the controller. That data is governed by the privacy policy at biller.be/privacy, not by this agreement.
Article 3. Instructions
3.1 ZenDev processes customer personal data only on documented instructions from the customer, including with regard to transfers to countries outside the European Economic Area (EEA). The customer's instructions are: the general terms and conditions, this agreement, the settings and actions of the customer and its users in biller (for example an export, sending an invoice over Peppol or by e-mail, approving a document in the inbox, connecting a bank account through Ponto, activating a connection or removing a customer), and other written instructions that ZenDev accepts.
3.2 If the law of the European Union or of a Member State requires ZenDev to carry out other processing, ZenDev informs the customer of this in advance, unless that law prohibits it.
3.3 If ZenDev considers that an instruction infringes the GDPR or other data protection rules, ZenDev informs the customer immediately. ZenDev may suspend the execution of that instruction until the customer confirms or amends it.
Article 4. Confidentiality
4.1 ZenDev only gives access to customer personal data to persons who need that access for this agreement. They are bound by a statutory or contractual duty of confidentiality.
4.2 ZenDev does not disclose customer personal data to third parties, except to sub-processors in accordance with Article 6, on the customer's instructions, or where the law requires it.
4.3 If a public authority or a court asks ZenDev for customer personal data, ZenDev refers the request to the customer and notifies the customer, unless the law prohibits this. ZenDev only provides what is legally required, and challenges a request where it has reasonable grounds to do so.
Article 5. Security
5.1 ZenDev takes the appropriate technical and organisational measures referred to in Article 32 GDPR. The measures at the start of this agreement are listed in Annex 2.
5.2 ZenDev may adapt the measures to the state of the art, provided that the level of security does not decrease.
Article 6. Sub-processors
6.1 The customer gives ZenDev a general authorisation to engage sub-processors. The sub-processors at the start of this agreement are listed in Annex 3. The current list is published at biller.be/dpa.
6.2 ZenDev announces a new or different sub-processor at least 30 days in advance by e-mail to the owner of the account. Within that period, the customer may object in writing on reasonable grounds. ZenDev will then seek a solution in good faith. If there is no solution, the customer may cancel the agreement free of charge with effect from the day on which the change takes effect.
6.3 ZenDev imposes on each sub-processor, in writing, the same data protection obligations as in this agreement, with sufficient guarantees of appropriate measures. ZenDev remains fully liable to the customer for the performance of the sub-processor's obligations.
6.4 Services that the customer connects itself, such as its accounting package, its webshop, its own applications through the API or an AI assistant through MCP, are not sub-processors of ZenDev. The customer chooses them itself and has its own agreement with them. ZenDev only sends data to them, or retrieves data from them, on the customer's instructions and within the rights (read-only or read and write) that the customer grants. The same applies to the recipients of the documents that the customer sends.
Article 7. Transfers outside the EEA
7.1 ZenDev stores and processes customer personal data in the EEA.
7.2 A transfer to a country outside the EEA, including by a sub-processor or through remote access, only takes place with a safeguard under Chapter V GDPR, such as an adequacy decision (including the EU-US Data Privacy Framework) or the standard contractual clauses of the European Commission. Annex 3 states the safeguard for each sub-processor.
Article 8. Assistance with data subject rights
8.1 biller gives the customer the means to handle data subject requests itself: access to and export of the data of a customer, supplier or contact person, correction of that data, removal of contact persons and documents, and the export of all data.
8.2 If ZenDev itself receives a request from a data subject concerning customer personal data, ZenDev forwards it to the customer without undue delay and refers the data subject to the customer. ZenDev does not respond on the substance without instructions from the customer.
8.3 If the customer cannot handle a request itself with the means available in biller, ZenDev provides reasonable assistance.
Article 9. Assistance with security, DPIA and prior consultation
9.1 ZenDev assists the customer, taking into account the nature of the processing and the information available to ZenDev, in complying with Articles 32 to 36 GDPR. To this end, ZenDev provides on request the description of the processing, the data flows and the measures.
Article 10. Personal data breaches
10.1 ZenDev notifies the customer of a personal data breach concerning customer personal data without undue delay, and at the latest within 48 hours after becoming aware of it, by e-mail to the owner of the account and in the app.
10.2 The notification contains, as far as known: the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken and proposed, and a contact person. ZenDev supplements whatever is not yet known as soon as possible.
10.3 ZenDev immediately takes reasonable measures to stop the breach and limit its consequences, and documents the breach.
10.4 Notifying the Belgian Data Protection Authority (GBA/APD) and the data subjects is the task of the customer as controller. ZenDev does not make those notifications on the customer's behalf, unless the customer asks it to or the law requires it.
Article 11. Access by ZenDev for support
11.1 ZenDev staff only view customer personal data where this is necessary to resolve a malfunction, to secure the service or to answer a support question from the customer.
11.2 Looking into the customer's account only takes place if the owner of the account allows this in the settings. Such access is temporary, is logged and is visible in the app.
Article 12. Retention during the agreement
12.1 The customer determines how long customer personal data is kept. biller keeps it for as long as the customer keeps it in its account and does not remove it itself. Accounting and VAT law require the customer to keep its invoices and accounting records for a certain period, currently up to 10 years.
12.2 The customer does not remove data that it is required by law to keep. The customer remains responsible for the choice of the period.
Article 13. End of the agreement: return and erasure
13.1 During the agreement and during the data retrieval period of at least 30 days after its end, the customer can export all data itself (Article 11 of the general terms and conditions). This constitutes the return of the customer personal data.
13.2 After the data retrieval period, ZenDev erases all customer personal data within 30 days. Backups are overwritten within the backup retention period (30 days). On request, ZenDev provides a written confirmation of the erasure.
13.3 If the law of the Union or of a Member State requires ZenDev to keep certain data for longer, ZenDev only keeps that data, only for as long as necessary, and no longer processes it for any other purpose.
Article 14. Information and audits
14.1 ZenDev makes available all information necessary to demonstrate compliance with the obligations of Article 28 GDPR and of this agreement, such as this agreement, the description of the measures and the list of sub-processors.
14.2 If that information is not sufficient, the customer may have an audit carried out once per calendar year, itself or by an independent auditor bound by confidentiality, after written notice of at least 30 days. An audit takes place on working days, without disrupting the service for other customers and without access to the data of other customers. The costs are borne by the customer. After a breach or at the request of a supervisory authority, an additional audit is possible.
14.3 ZenDev cooperates with an investigation by a competent supervisory authority.
Article 15. Record of processing activities
ZenDev keeps a record of the processing it carries out for its customers (Article 30(2) GDPR) and makes it available to the supervisory authority on request.
Article 16. Liability
16.1 Between the parties, the liability provisions of Article 14 of the general terms and conditions apply, without prejudice to the rights of the data subjects (Article 82 GDPR) and except where the law prohibits a limitation.
Article 17. Term, changes, law and court
17.1 This agreement applies for as long as ZenDev processes customer personal data, also after the end of the general terms and conditions until everything has been erased.
17.2 ZenDev may change this agreement in the same way as the general terms and conditions (Article 16 thereof). Changes required by law apply from the date set by the law.
17.3 This agreement is governed by Belgian law. Article 18 of the general terms and conditions applies to disputes.
17.4 The Dutch version is the reference version; in case of differences with a translation, it prevails.
---
Annex 1. Description of the processing
Subject matter and purpose. Providing biller to the customer: drawing up and sending quotes, invoices and credit notes (over Peppol or by e-mail, with an online invoice and an EPC payment QR code), registering and matching payments, managing customers and the catalogue, the dashboard, the inbox for purchase invoices and receipts with reading by AI, the bank connection through Ponto, connections with accounting packages and webshops, the REST API and AI assistants through MCP, notifications, support and security.
Nature of the processing. Storing, organising, calculating, displaying, sending (e-mail and Peppol), receiving (forwarded e-mails, Peppol, photos and scans, the browser extension), reading documents with AI (text recognition and recognising data such as supplier, date, amounts and VAT), retrieving bank transactions and preparing payments through Ponto, exchanging data with connections activated by the customer, exporting, making backups and erasing.
Duration. For as long as the agreement runs, plus the transitional and data retrieval periods and the period for erasure (Article 13).
Categories of data subjects.
- customers of the customer who are natural persons (such as freelancers, sole traders or private individuals), and the contact persons of customers that are businesses;
- suppliers of the customer who are natural persons, and the contact persons of suppliers;
- users of the customer, such as the managing director, staff and the accountant;
- counterparties in the bank transactions of the accounts that the customer connects through Ponto;
- other persons whose data appears in documents that the customer draws up in biller or has read in the inbox.
Categories of personal data.
- identification and contact: name, company name, address, e-mail address, telephone number, language, VAT number, enterprise number, Peppol ID;
- documents: quotes, invoices and credit notes with their lines, amounts, VAT, structured payment reference, dates, due date, status and sending details (channel, time, delivery), and the online invoice;
- payments: date, amount, partial payments and the matching to invoices;
- bank data through Ponto: account number (IBAN) and name of the account holder, transactions (date, amount, counterparty with name and account number, payment reference) and prepared payments;
- inbox: the received or uploaded files, photos and scans, the e-mails with which they arrived, the data the AI read from them, and the user's check and approval;
- users: name, e-mail address, role, language, sign-ins;
- connections: the chosen rights, encrypted tokens and logs of access through the API and MCP;
- technical data: IP addresses, sign-in attempts, hashed passwords and API keys, notification preferences.
Not intended. biller is not intended for special categories of personal data (Article 9 GDPR), data relating to criminal convictions or national register numbers. If such data nevertheless appears in a document that the customer draws up or places in the inbox, biller only processes it as part of that document. biller does not process bank login credentials: access to the accounts runs through Ponto, and the customer signs payments in its own banking app.
Retention. According to the customer's choices; see Article 12.
Annex 2. Technical and organisational measures
- Hosting in the EEA: servers, database, file storage and backups are located in a data centre of Hetzner Online GmbH in Germany (Nuremberg).
- Encryption: all connections over HTTPS (TLS) with HSTS. Passwords and API keys are only stored hashed. Secrets such as the tokens of connections (Ponto, accounting packages, webshops, MCP) are stored encrypted. Encryption of the disks and the backups:.
- Separation between customers: every row belongs to one customer. Access is limited in the code on every request (global scope and policies), and automated tests prove for each data type that a customer cannot read or change another customer's data.
- Access management in the app: roles and rights for the customer's users. Passwords of at least 12 characters, two-step verification, limits on sign-in attempts per IP address and account, signing out on all devices.
- Logging: important actions, such as sending documents, registering payments, approving documents in the inbox and actions through the API or MCP, are logged with who performed them and when.
- Access by ZenDev: only for those who need it, with two-step verification. Administration interfaces can only be reached through a VPN or fixed addresses. Looking into a customer account only with the customer's permission, temporarily and logged.
- Backups: every night a full backup of the database and the files, kept for 30 days, in the EEA, on storage separate from the production environment. Restoring is tested regularly.
- Monitoring: error monitoring through Sentry in the EU region, with filtering of personal data; health checks; server logs are kept for.
- Secure development: automated tests, static analysis, checks of dependencies for known vulnerabilities, security headers (CSP, HSTS), limits on the API, dependencies kept up to date.
- Data minimisation by design: the AI only reads documents that the customer itself places in the inbox; through Ponto only the accounts that the customer connects are read, for as long as the customer does not withdraw that consent; biller does not know any bank login credentials and does not move money; an AI assistant only gets the rights the customer chooses (read-only or read and write), issuing, sending and paying always require the user's confirmation, and the customer can revoke the access; the AI provider does not use the documents to train models.
- Incidents: a procedure for breaches with notification to the customer within 48 hours (Article 10).
- Erasure: removal of data by the customer in the app; erasure of an entire account after the data retrieval period.
Annex 3. Sub-processors, data location and access by public authorities
Sub-processors on 1 November 2026
| Sub-processor | What | Data | Where | Safeguard |
|---|---|---|---|---|
| Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany | Hosting of servers, database, file storage and backups | All customer personal data | Germany (Nuremberg) | EEA; data processing agreement with Hetzner |
| Sending e-mails (documents to the customer's customers, invitations, notifications, password resets) and receiving forwarded e-mails for the inbox | Name, e-mail address, content and attachments of the e-mail | |||
| e-invoice.be | Peppol access point: sending and receiving invoices and credit notes over Peppol | The data on the documents: name, address, VAT number and Peppol ID of customer and supplier, lines and amounts | ||
| Ponto, Isabel Group | Bank connection: reading accounts and transactions, preparing payments | IBAN and name of the account holder, transactions with counterparty and payment reference, payment orders | ||
| Reading documents in the inbox | Content of the documents, such as the names, addresses, VAT numbers, account numbers and amounts they contain | |||
| Functional Software, Inc. (Sentry), San Francisco, United States | Error monitoring of the app | Technical error data; an internal user ID; personal data is filtered out as far as possible | Storage in the EU region (Frankfurt, Germany) | EU-US Data Privacy Framework or standard contractual clauses for access from the US |
Not sub-processors of ZenDev, for information
- Mollie B.V., Amsterdam, the Netherlands: only processes the customer's own payment data for the subscription with ZenDev, not the data of the customer's customers or suppliers. See the privacy policy.
- Services that the customer connects itself (Article 6.4), such as accounting packages, webshops and AI assistants.
Location and jurisdiction (Article 28 of the Data Act)
- biller runs on infrastructure in Germany, managed by ZenDev, a Belgian business. The infrastructure is subject to the law of the European Union, Germany and Belgium.
- Measures against unlawful access by public authorities outside the EU: all customer data and backups remain in the EEA; the hosting partner is a European business; we send as little data as possible to services of businesses outside the EU and filter out personal data there; all connections are encrypted; we only comply with a request from a public authority outside the EU if the law of the Union or of Belgium allows it, and we inform the customer unless this is prohibited.