Citizen Pay BV
Data Processing Agreement
Effective date: 12 November 2026. Version: 1.0.
This data processing agreement ("DPA") sets out how Citizen Pay processes personal data on behalf of operators. It meets Article 28 of the General Data Protection Regulation (EU) 2016/679 ("GDPR"). It forms part of the Agreement described in our Terms of Service (clauses 2 and 18).
1. Parties and scope
1.1 This DPA is between Citizen Pay BV, a private limited company (besloten vennootschap) under Belgian law, Kantersteen 47, 1000 Brussels, Belgium, enterprise and VAT number BE 1029.985.788, RPR/RPM Brussels ("Citizen Pay", "we", "us"), and the business that holds the Agreement with us ("you"): an operator or, under clause 2.3, a Reseller.
1.2 This DPA applies to the personal data that we process on your behalf when we provide the Service. It applies from the start of the Agreement, without a separate signature, for as long as we process that data (clause 3.2). We can also sign it separately on request.
1.3 Words defined in the Terms of Service, such as Agreement, Service, Operator, Reseller, Badge, Badge credit, Badge ledger, Magic Badge, Dashboard and End user, have the same meaning here. Words defined in the GDPR, such as personal data, processing, controller, processor, data subject and personal data breach, have their GDPR meaning.
2. Roles
2.1 You are controller, we are processor. For the personal data of your badge holders, members, employees and customers that we process through the Service, you are the controller and we are your processor. You decide why this data is processed. We process it only to provide the Service to you.
2.2 Examples. Your badge member lists, the badge ledger we keep for you, badge payments and Magic Badge taps at your machines, payments at your machines and on your hosted checkout page, and the sales reports we give you.
2.3 Resellers. Where a Reseller keeps the customer contract (clause 23 of the Terms), the Reseller's customer is the controller, the Reseller is its processor, and we are the Reseller's sub-processor. In that case:
- this DPA applies between us and the Reseller;
- the Reseller gives us instructions on behalf of its customer and passes on to its customer terms that are equivalent to this DPA;
- where this DPA refers to you as controller, it means the Reseller acting for its customer, and the Reseller passes on to its customer, without undue delay, any notice or information we give under this DPA.
Where the contract is with us, this DPA applies directly between us and the customer.
2.4 When we are controller. This DPA does not cover data that we process for our own purposes as controller. That includes your dashboard user accounts, our invoicing and accounting, support, device monitoring and terminal status data, the security of our platform, our website, the Citizen Pay app account of a badge holder, and the payment records we use to bill our fees, handle refunds and prevent fraud. Our Privacy Policy explains that processing. Data about the use and performance of terminals and the Service in a form that does not identify anyone is covered by clause 18.6 of the Terms.
2.5 Payment providers. Viva, Ponto, Exthand and Stripe process payment data as independent controllers, under your own agreements with them (clauses 5 and 18.3 of the Terms). They are not our sub-processors. When we pass payment data to them, we do so on your instruction, as part of the Service.
3. Subject matter, duration, nature and purpose
3.1 Subject matter. The processing of personal data needed to provide the Service to you, as described in Annex 1.
3.2 Duration. For the term of the Agreement, and after its end until we have deleted or returned the data under clause 13.
3.3 Nature. Collecting, recording, storing, organising, consulting, using, correcting, passing to the payment providers you choose, and deleting personal data, through our terminals, the dashboard, the badge ledger and the hosted checkout page.
3.4 Purpose. To let badge holders pay or get a discount by tapping a badge, to keep badge balances on the badge ledger, to record sales and vend products, to give you sales and stock reports, and to give you support on the Service.
3.5 Types of personal data and data subjects. Annex 1 lists them. We do not process card numbers. The Service is not designed for special categories of personal data under Article 9 GDPR, and you do not enter such data in the dashboard.
4. Your instructions
4.1 We process the personal data only on your documented instructions. Your instructions are this DPA, the Agreement, your use of the dashboard and your settings in it (for example badges, allowances, discounts and spend caps), and any other instruction you give us in writing.
4.2 We create, adjust or remove badge credit only on your instruction (clause 13.2 of the Terms).
4.3 If the law of the European Union or of a Member State requires us to process the data in another way, we tell you before we do so, unless that law forbids it.
4.4 If we think an instruction breaks the GDPR or another data protection law, we tell you at once. We may then wait to carry out that instruction until you confirm or change it.
5. Your responsibilities
5.1 You make sure you have a legal basis for the processing and give the required information to the people whose data you enter in the dashboard, including badge holders (clause 18.4 of the Terms).
5.2 You are responsible for the accuracy of the data you enter or import, and for your instructions.
5.3 You keep your dashboard logins safe and give access only to people who need it (clause 7.3 of the Terms).
6. Confidentiality
6.1 We give access to the personal data only to staff who need it for their work.
6.2 Everyone who has that access is bound to keep the data confidential, by contract or by law.
7. Security
7.1 We take appropriate technical and organisational measures to protect the personal data, as Article 32 GDPR requires. Annex 3 describes them.
7.2 We may change these measures over time, as long as the overall level of protection does not go down.
8. Sub-processors
8.1 General authorisation. You give us a general written authorisation to use sub-processors. The sub-processors we use today are listed in Annex 2.
8.2 Same obligations. Each sub-processor is bound by a written contract with data protection obligations equivalent to those in this DPA. We remain responsible to you for our sub-processors.
8.3 Changes. We tell you by email at least 30 days before we add or replace a sub-processor. We also update Annex 2.
8.4 Your right to object. You may object to a new sub-processor for reasonable data protection reasons, in writing, before the change takes effect. We then discuss it with you in good faith. If we cannot resolve your objection, you may end the affected services, without an early-termination charge, by telling us before the change takes effect.
9. Transfers outside the EEA
9.1 We host your personal data in the European Union: our database in Germany, and our API and payment engine in Amsterdam, the Netherlands.
9.2 Some sub-processors in Annex 2 are companies based outside the European Economic Area, or use servers outside it. Where personal data is transferred outside the EEA, or accessed from outside it, we make sure the transfer is covered by an adequacy decision of the European Commission, such as the EU-US Data Privacy Framework for certified companies, or by the European Commission's standard contractual clauses.
9.3 Badge credit is recorded on the badge ledger in our own systems in the European Union. It is not recorded on a public blockchain.
10. Help with data subject requests
10.1 If a data subject asks us to exercise a right under the GDPR about data we process for you, we pass the request to you without undue delay. We do not answer it ourselves unless you ask us to.
10.2 We help you answer such requests, as far as the nature of the processing allows. Many requests you can handle yourself in the dashboard, for example by correcting or deleting a badge member or blocking a badge. Because the badge ledger is in our own systems, we can correct and erase its records on your instruction.
11. Help with your other obligations
11.1 Taking into account the nature of the processing and the information available to us, we help you meet your obligations under Articles 32 to 36 GDPR: security of processing, notifying and communicating personal data breaches, data protection impact assessments, and prior consultation of the supervisory authority.
11.2 We keep the record of processing activities that Article 30(2) GDPR requires, and we cooperate with the supervisory authority on request.
12. Personal data breaches
12.1 We notify you without undue delay, and where feasible within 48 hours, after we become aware of a personal data breach that affects data we process for you.
12.2 Our notice describes, as far as we know at that moment, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, and the measures we have taken or propose. Where we cannot give all of this at once, we give it in stages without further undue delay.
12.3 We take reasonable steps to contain the breach and limit its effects. We do not notify the supervisory authority or the data subjects on your behalf unless you ask us to or the law requires it.
13. Retention, deletion and return
13.1 During the Agreement. You can correct and delete data in the dashboard at any time. We keep the data for the periods set out in section 6 of our Privacy Policy.
13.2 Return. Before the Agreement ends, and during 30 days after its end, you can export your list of badges, holders and balances and your sales data from the dashboard (clauses 13.10 and 14.7 of the Terms). This export is how we return the data to you.
13.3 Deletion. We delete badge member data, badge balances and the link between a transaction and a named member within 90 days after the end of the Agreement.
13.4 What we must keep. Payment, sales and discount records, including badge payments and top-ups on the badge ledger, support our invoices to you. We keep them as accounting records for as long as Belgian accounting and tax law requires, as set out in our Privacy Policy. We keep them only for that legal purpose and delete them when that period ends.
13.5 Where data remains in backups made by our database provider, it stays protected under this DPA until it is overwritten.
14. Information and audits
14.1 We make available to you the information you reasonably need to show that we meet our obligations under Article 28 GDPR and this DPA.
14.2 You may audit our compliance with this DPA, yourself or through an independent auditor bound by confidentiality, under these conditions:
- you give us reasonable written notice;
- an audit takes place at most once every 12 months, unless there has been a personal data breach affecting your data, or a supervisory authority asks for it;
- the audit takes place during our working hours and does not unreasonably disrupt our business;
- the audit respects the confidentiality of our other customers' data and of our security measures;
- you bear the costs of the audit, including your auditor's.
14.3 Where we can answer an audit request with documents and written answers, we do so first.
15. Liability
15.1 Clause 21 of the Terms of Service, including its cap, applies to all claims under this DPA.
15.2 This does not limit the rights that data subjects have under the GDPR.
16. Precedence, term and changes
16.1 On the protection of personal data, this DPA prevails over the other documents of the Agreement, unless an order form expressly changes a clause of this DPA.
16.2 This DPA ends when we no longer process personal data on your behalf. Clauses 12, 13, 14 and 15 continue for as long as they need to.
16.3 We may change this DPA as set out in clause 24 of the Terms of Service. We change the list of sub-processors as set out in clause 8.
17. Governing law and courts
17.1 This DPA is governed by Belgian law.
17.2 We first try to settle any dispute by talking to each other. If we cannot settle it within 30 days, the courts of Brussels have exclusive jurisdiction.
18. Contact
18.1 Questions about this DPA and data protection go to privacy@citizenpay.eu.
18.2 We send notices under this DPA to the email address in your order form or your billing details.
Annex 1. Details of the processing
Categories of data subjects
- your badge holders: members, employees and customers to whom you issue a badge or a Magic Badge;
- end users who pay at your machines, by card, meal voucher card, QR code, bank app or badge;
- people who pay on your hosted ordering or checkout page;
- badge holders who use the Citizen Pay app, for the badge and payment data shown in the app.
Types of personal data
- Badge members: name, optional email address, optional internal ID that you give (entered or imported by CSV).
- Badges: badge chip serial number, status (active, blocked, lost), badge type, and your settings for that badge, such as tariff, allowance, spend cap and discount.
- Badge ledger: prepaid credit balance, top-ups, allowances and badge payments (time, place, machine, amount, products).
- Magic Badge taps: badge identifier, time, machine and discount applied.
- Payments at your machines: transaction reference, amount, time and terminal; for open banking payments, the amount, status and reference, and, where the bank requires it, the payer's IBAN, which is passed to the open banking partner for that payment.
- Payments on your hosted checkout page: order contents, amount, the bank selected, payment status; the payer's IP address, used only to find the payer's country; and the message and bank selected if the payer reports an issue.
- Sales records and reports linked to a badge, a machine or a site.
Special categories of data: none.
Frequency: continuous, for as long as the Service is in use.
Annex 2. Sub-processors
| Sub-processor | Service | Data concerned | Location |
|---|---|---|---|
| Supabase | Database | All stored service data, including badge member data, the badge ledger and sales records | Germany |
| Railway | Hosting of our API and payment engine | All service data in transit | Amsterdam, Netherlands |
| Vercel | Hosting of the dashboard and the hosted checkout page | Web traffic of the dashboard and the checkout page | EU hosting; US company |
| Resend | Sending emails | Email addresses, email content | Ireland (EU sending region); US company |
| Amazon Web Services (SNS) | Sending SMS codes | Phone numbers | EU region |
| Fonts on the hosted checkout page | IP address | USA / EU | |
| ip-api.com | IP-to-country lookup on the checkout page | IP address | Servers in the EU, US and Asia-Pacific |
| Discord | Internal operational alerts and checkout issue reports | Alert text, messages written by payers | USA |
Viva, Ponto, Exthand and Stripe are not sub-processors. They act as independent controllers (clause 2.5).
Annex 3. Security measures
- Hosting in the European Union: database in Germany, API and payment engine in the Netherlands.
- Encryption in transit: the dashboard, the API and the hosted checkout page are reached over encrypted connections (HTTPS).
- Encryption at rest: our database provider encrypts stored data and backups.
- Access for our staff: only staff who need the data for their work have access to it.
- Access in the dashboard: access control per business and per role.
- Hashing: API keys and PINs are stored only as hashes or digests. Phone numbers of app users are stored in hashed form, not in clear text.
- Credentials: credentials for payment providers are stored encrypted.
- Webhooks: messages from payment providers are signed and verified.
- Rate limits on sign-in codes and on badge claiming.
- Action log: an append-only audit log of administrative actions in the dashboard (who, what, when).
- No card numbers: card numbers never reach our systems.