Citizen Pay BV
Privacy Policy
Effective date: 12 November 2026.
1. Who we are
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").
We supply payment terminals, software (a dashboard and an app) and support to businesses running self-service points of sale such as coffee and vending machines, honesty-bar fridges and co-working spaces ("operators"). We provide software and hardware. We are not the payment processor: payments are processed by our partners, Viva for card and meal voucher card payments, and Ponto or Exthand for open banking payments (section 2). We never hold our customers' or their customers' funds.
General contact: contact@citizenpay.eu. Support: support@citizenpay.eu, or +32 471 30 85 39 by phone or WhatsApp.
Privacy contact: questions about your data go to privacy@citizenpay.eu. Our founder is responsible for privacy at Citizen Pay. We have not appointed a Data Protection Officer; our activities do not require one.
2. Two roles: controller and processor
- We are controller for data we process for our own purposes: our website, sales enquiries, operator accounts, invoicing, support, the Citizen Pay app account, device monitoring and the security of our platform.
- We are processor for the operator for the data of the operator's own customers, members and employees: badge member lists, badge and payment transactions at the operator's machines, and the sales reports derived from them. The operator decides why this data is processed. Our contract with each operator includes a data processing agreement (Art. 28 GDPR) that sets out what we may do with this data. Contact the operator first; we will help them answer you.
- Payment providers act independently. Card and meal voucher card payments are handled by Viva, with whom each operator holds its own account. Open banking payments (QR code and bank-app payments, and top-ups by bank) are handled by Ponto or Exthand and your own bank. Each of them is responsible for its own processing.
- La Caisse funds. La Caisse is open-source software that we run (host) for others. Each fund on La Caisse, such as Brussels Pay, is an independent organisation and is the controller of its members' data. We host the software for it as processor. Those funds have their own privacy notices; this policy does not cover them.
- Contact card pages. For the public contact pages at contact.citizenpay.eu we are controller (section 3.9).
3. What we collect, why, and on what legal basis
3.1 Website visitors and people who contact us
- Contact / terminal request form: business name, your name, email and/or phone number, business segment, language. We use it to call you back and send one confirmation email. It is sent by email to our team inbox; it is not stored in a database. Basis: steps at your request before a contract (Art. 6(1)(b)) and our legitimate interest in answering business enquiries (Art. 6(1)(f)).
- IP address, held in server memory for up to one hour to limit form abuse. Basis: legitimate interest (security).
- Audience measurement: we use Vercel Web Analytics, which counts page views and clicks on buttons and menus without cookies and without identifying you. Basis: legitimate interest.
- Server logs of our hosting providers, kept for a short period (see section 6). Basis: legitimate interest (security and fixing faults).
3.2 Operator account users (dashboard)
- Name, email, password or Google sign-in, role and business; a log of actions taken in the dashboard (who, what, when, IP address and browser); notification preferences.
- Billing contact, billing email, VAT number and address; delivery contact name, phone and address for hardware orders; payments of our invoices received on our bank account (payer name and IBAN).
- Basis: contract (Art. 6(1)(b)); legal obligation for invoices and accounting (Art. 6(1)(c)); legitimate interest for security and audit (Art. 6(1)(f)).
3.3 Badge holders, members and employees of an operator
- Name, optional email, optional internal ID given by the operator (entered or imported by CSV); badge chip serial number and status (active, blocked, lost); prepaid credit balance; each badge payment (time, place, machine, amount, products). We process this as processor for the operator.
- Badge credit is prepaid credit that the operator issues and that can be spent only at the operator's own machines and sites. We record badges, balances, top-ups and badge payments on a ledger that we run for the operator in our own systems in the EU (database in Germany, API and payment engine in the Netherlands). Badge credit is not recorded on a public blockchain. We create, adjust or remove credit only on the operator's instruction. The money paid for top-ups goes to the operator through its own payment partner, never to us. Because the ledger is in our systems, its records can be corrected and erased under the retention rules in section 6.
- Magic Badge: a badge that only unlocks a discount at an operator's machine. It carries no credit and no balance, and it is not funded by an employer. It is different from a badge with credit, where the credit is used to pay. When you tap it we record the badge identifier, the time, the machine and the discount applied.
- Citizen Pay app: operators can offer our app to their badge holders. If you use it: your phone number, verified by SMS code, stored in hashed form and linked to an identifier generated by your device; badges you link to the app; the places where you used it; an optional payment PIN stored as a digest; records of card-claim attempts (hashed phone and IP, browser type) used to stop misuse. For your app account we are controller (basis: contract, and legitimate interest for security). For badge and payment data shown in the app we act for the operator.
- Purpose: let you pay or get a discount by tapping a badge, keep balances, give the operator its sales and stock reports. For data we process for the operator, the operator determines the legal basis.
3.4 People paying at a machine
- Bank card, Apple Pay, Google Pay, meal voucher card: you pay on a certified card terminal. Each operator has its own account with Viva (Vivabank S.A., viva.com), which processes the card payment. Meal voucher cards are also processed through Viva. Citizen Pay is a software partner of Viva and does not hold a merchant account. We never receive your card number. We receive the transaction reference, amount, time and terminal.
- QR code or bank-app payment, and top-up by bank: you choose your bank and approve the payment in your banking app through our open banking partner, Ponto (Isabel NV) or Exthand (Exthand SA/NV). Both are regulated payment initiation services. We receive the amount, status and reference. Some banks require your IBAN; it is then passed to that partner for that payment.
- Badge: see 3.3.
- We process these on the operator's behalf to record the sale, vend the product and give the operator its sales records; and as controller for refunds, fraud prevention and billing our fees (legitimate interest; legal obligation for accounting).
3.5 People paying online (hosted ordering/checkout page)
- Order contents, amount, the bank you selected, the payment status.
- Card or wallet payments on this page are processed by Stripe on the operator's own Stripe account; we do not receive your card number.
- To pre-select banks for your country, your IP address is sent to an IP geolocation service (ip-api.com) and only the country is returned.
- If you use "report an issue", your message and the bank you selected are sent to our internal support channel.
- Basis: as in 3.4.
- Usage measurement: we measure how the checkout page is used, to fix problems and improve it. We record these steps: opening the page, adding or removing an item, starting checkout, choosing a payment method or a bank, and a completed payment (with the order number, payment method and amount). With each step we record the shop, the time, your device type, operating system and browser (read from your browser's user agent) and any campaign tags in the page address. To count visits, the page derives an identifier from technical characteristics of your browser and device (user agent, screen size, time zone, language, number of processor cores and memory size) and adds a random number for the current visit. The identifier is a one-way hash: it does not reveal these characteristics, but the same browser on the same device produces the same identifier on later visits. These records are sent to our own API and stored in our database in Germany. They do not contain your name, email address, IBAN, card details or IP address. We do not use them to identify you, do not share them with third parties and do not use them for advertising; the operator of the shop sees only the number of visits. Basis: legitimate interest.
3.6 Terminals and devices
Terminals send technical status data (battery, network type and signal, Wi-Fi network name, app version, errors, crash reports). Android terminals are managed through Google's Android Management API. Terminals with a SIM card use Proximus or Digi connectivity. This data concerns equipment, but may relate to the operator or its staff. Basis: contract and legitimate interest (keeping terminals working).
3.7 Support
When you contact support by email, phone or WhatsApp, we keep the conversation to solve your issue. If you choose WhatsApp, your messages pass through WhatsApp (Meta), under WhatsApp's own terms. Basis: contract or legitimate interest.
We do not sell personal data and do not use it for advertising or automated decisions with legal effect.
3.8 Community funds on La Caisse
Community funds on La Caisse, such as Brussels Pay, record their tokens on Gnosis Chain, a public blockchain, under the fund's own terms and privacy notice. Operator badge credit is never recorded there. Each fund is the controller of its members' data (section 2); for everything about that data, see the fund's own notice.
Public blockchain records. When a fund's token moves, a record is written to Gnosis Chain: the blockchain addresses involved, the amount and the time. Names, email addresses, phone numbers and badge serial numbers are not written to the blockchain. The link between an address and a person is kept only in the systems we host for the fund. A public blockchain is copied by many independent computers and cannot be changed or deleted by us, the fund or anyone else. If you ask the fund to erase your data, the link between you and the address is deleted in the systems we host, on the fund's instruction. The blockchain record then remains, but can no longer be connected to you through those systems.
3.9 Contact card pages (contact.citizenpay.eu)
Some cards handed out at conferences and events carry a link to a contact page at contact.citizenpay.eu. The card holder can use it to share their contact details. We are controller for these pages.
- What the page holds. Only what you choose to publish: your name, and if you wish a headline (for example your role), a short bio, a profile photo and up to 20 links (for example LinkedIn, a website, an email address, a phone or WhatsApp number, social media). We also keep the date of your last edit.
- Who can see it. The page is public. Anyone who scans the card or has the link can read it, and can save it as a contact on their phone. Do not publish anything you do not want to share.
- Your PIN. You choose a PIN on your first save. We store it only as a one-way hash. We count wrong PIN entries and lock editing for a short time after several wrong entries.
- Changes and deletion. You can change or remove anything except your name at any time. To delete the page, write to privacy@citizenpay.eu. The fund that issued the card can also delete the page, for example if you forgot your PIN. After you remove or replace a photo, copies may stay in browser caches for up to one day.
- Cookie. If you change the language of the page, a cookie (locale) remembers your choice for one year.
- Basis: providing the page you asked for (Art. 6(1)(b)), and our legitimate interest in protecting it against misuse (Art. 6(1)(f)).
The page does not show your balance or your payments, and editing it does not use the card's payment PIN.
4. Who receives personal data
The table below lists both the providers that process personal data on our behalf and the recipients that process it for their own purposes as independent controllers, such as Viva, Ponto, Exthand and Stripe (marked in the Role column). Where we act as processor for an operator, the providers that process that data for us are our sub-processors; the data processing agreement lists them.
| Provider | Role | Data | Location |
|---|---|---|---|
| Vercel | Hosting of website, dashboard and checkout; web analytics | All web traffic | EU hosting; US company |
| Railway | Hosting of our API and payment engine | All service data in transit | Amsterdam, Netherlands |
| Supabase | Database and dashboard login | All stored service data | Germany |
| Resend | Sending emails | Email addresses, email content | Ireland (EU sending region); US company |
| Amazon Web Services (SNS) | Sending SMS codes | Phone numbers | EU region |
| Dashboard sign-in; Android device management; fonts on checkout page | Account email; device data; IP address | USA / EU | |
| WhatsApp (Meta) | Support messages, only if you choose WhatsApp | Phone number, messages | EU / USA |
| Viva (Vivabank S.A., Greece) | Card and meal voucher payments on terminals, on the operator's own account (independent controller) | Payment data | EU |
| Ponto (Isabel NV, Brussels; payment institution authorised by the National Bank of Belgium) | Open banking: payment initiation for QR code and bank-app payments and top-ups by bank; bank account connection (independent controller) | Bank, IBAN, payment | Belgium |
| Exthand (Exthand SA/NV, agent of Digiteal SA, a payment institution authorised by the National Bank of Belgium) | Open banking: payment initiation for QR code and bank-app payments and top-ups by bank; bank account connection (independent controller) | Bank, IBAN, payment | Belgium |
| Stripe | Online card/wallet payments for operators (independent controller) | Payment data | EU/USA |
| Gnosis Chain | Public blockchain recording community fund tokens on La Caisse (not operator badge credit) | Addresses, amounts, times | Worldwide, public |
| Recommand (BRBX BV, Peer, Belgium) | Peppol e-invoicing access point | Invoice data of operators | Belgium; hosting in the EEA |
| Proximus, Digi | Mobile connectivity for terminals | SIM and traffic data | Belgium |
| Mapbox | Address lookup when operators enter a location | Address text | USA |
| 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, user messages | USA |
| Astro Tax (astro.tax) | Accountant, bookkeeping | Invoices, bank records | Belgium |
We deliver hardware ourselves. If we use a delivery carrier later, it will receive the delivery name, phone number and address, and we will add it to this list.
We also disclose data to authorities where the law requires it, and to the operator for whom we process it.
5. Transfers outside the EEA
Our database and servers are in the EU: the database in Germany, our API and payment engine in Amsterdam, and SMS sending in an EU region. Some providers above are companies based in the United States, and some may access data from there. In that case we rely on the EU–US Data Privacy Framework or the European Commission's Standard Contractual Clauses. Records of community fund tokens on Gnosis Chain (section 3.8) are public and can be read from anywhere.
6. How long we keep data
| Data | Period |
|---|---|
| Terminal status samples | 90 days, then deleted automatically |
| Form-abuse IP counter | 1 hour, in memory only |
| Server and application logs | 30 days |
| Checkout page usage records (section 3.5) | 13 months |
| Contact-form emails (no contract follows) | 1 year after the last contact |
| Support conversations (email, WhatsApp) | 2 years after the last contact |
| Operator account and dashboard data | Contract duration, then deleted within 1 year; the contract itself is kept 10 years after it ends (Belgian limitation period for contract claims) |
| Dashboard action log | 2 years |
| Invoices, accounting records and their supporting documents | For as long as Belgian accounting and tax law requires, currently 7 to 10 years depending on the record |
| Payment, sales and discount records, including badge payments and top-ups on the badge ledger (amount, time, machine, reference) | Same as accounting records, as they support our invoices to operators |
| Badge member data, badge balances and the link between a transaction and a named member | Until the operator deletes it; deleted within 90 days after the operator's contract ends |
| Citizen Pay app account | Until you ask us to delete it, or after 2 years without use |
| SMS verification records | 30 days |
| Card-claim records | 90 days |
| Device crash reports and device-management reports | 90 days |
| Email sending log | 1 year |
| Contact card pages | Kept until the holder or the issuing fund deletes the page, or until we delete it on request |
| Records of community fund tokens on Gnosis Chain | Permanent; cannot be deleted (see 3.8 and the fund's notice) |
7. Security
We protect data with access control per business and role; encryption of stored payment-provider credentials; API keys and PINs stored only as hashes or digests; signed and verified webhooks; rate limits on sign-in codes and badge claiming; an append-only audit log of administrative actions. Our database provider encrypts stored data and backups. Card numbers never reach our systems.
8. Your rights
You may ask for access, correction, deletion, restriction, portability, or object to processing based on legitimate interest, and withdraw consent at any time. Write to privacy@citizenpay.eu. We answer within one month. We may ask you to prove your identity. If we process your data for an operator or a La Caisse fund, we pass your request to them. Operator badge credit is kept in our own systems, so its records can be corrected and erased. Only community funds on La Caisse write records to a public blockchain, and those cannot be deleted (see 3.8).
You may complain to the Belgian Data Protection Authority (Gegevensbeschermingsautoriteit / Autorité de protection des données), Drukpersstraat 35 / Rue de la Presse 35, 1000 Brussels, www.dataprotectionauthority.be, or to the authority of your country.
9. Cookies and similar technologies
Website (citizenpay.eu): no advertising or tracking cookies. If you choose a language other than your browser's language, a language cookie (NEXT_LOCALE) remembers your choice. It is deleted when you close your browser. Login cookies are set only in our staff area. Analytics is cookieless. Fonts are served from our own domain.
Checkout page: stores on your device the last shop you visited, your selected bank and, if you entered it, your IBAN, plus your last payment method; these stay on your device. For usage measurement (section 3.5) it keeps the browser identifier, the random visit number and a list of the steps already recorded for the current visit only; they are deleted when you close the tab. If you pay through your bank app, the visit number is also kept until the payment is confirmed, so that the visit can be followed after you return; if the payment is not completed, it stays until you clear your browser's data for this site. The order numbers of completed payments are also kept, so that a payment is not counted twice; they stay until you clear your browser's data for this site. Stripe sets fraud-prevention cookies when you pay by card. Fonts are loaded from Google.
Dashboard: login cookies only. They are necessary for the service.
Contact card pages (contact.citizenpay.eu): a language cookie only, if you change the language (section 3.9).
10. Children
Our services are not directed at children. Badges and Magic Badges are meant for offices and businesses. If a member of a fund passes a badge to a child, that is the responsibility of the fund or operator that issued it.
11. Changes
We may update this policy. The effective date at the top shows the latest version; we will notify operators of material changes by email.