1. Who we are
Celbrio is software made and run by Celbrio, registered with the Netherlands Chamber of Commerce under number 92886787, VAT number NL004984472B94, at Nachtegaalstraat 11, 1021 ER Amsterdam, the Netherlands ("Celbrio", "we", "us").
For questions about privacy or to exercise your rights, email info@celbrio.com or write to the address above. If we contact your business before we have worked together, see how Celbrio contacts businesses.
2. Our two roles
Controller. We decide how and why we use the personal data of the people who open an account, sign in and use the software (our customers' users), and of visitors to this website and people who contact us. This policy explains that use.
Processor. Our customers put their own data into the software: their companies, bookkeeping, tax returns, employees and payroll, and the data of their own clients if they are an adviser. For that data the customer is the controller and we process it only on their instructions, under the data processing agreement that is part of our terms of use. If your data is in Celbrio because your employer, bookkeeper or adviser uses it, please contact them first; we will help them answer your request.
3. What we collect and why
| Data | Why | Legal basis |
|---|---|---|
| Account: organisation name, your name, email address, roles, a hash of your password (never the password itself), the version of the terms you accepted and when | To open and run your account, let you sign in, and show who did what | Contract |
| Security and audit records: sign-ins, failed sign-in attempts, the IP address of sign-up and sign-in requests, and a tamper-evident log of actions such as preparing, reviewing, filing and approving payments | To keep accounts safe, block abuse, and give you and the tax authorities a trustworthy record of who filed what | Legitimate interest; legal obligation where tax law requires records |
| Sign-in methods you choose: the email address and account identifier that Google confirms when you sign in with Google; the public key and device name of a passkey; the secret of your authenticator app, stored encrypted | To let you sign in safely without extra passwords, and to ask for a second step | Contract; legitimate interest |
| Information you send us by email | To answer you | Legitimate interest |
| What you fill in on a form in one of our Instagram or Facebook ads: your name, work email, phone number, company name and your answers (number of employees, countries, what you are looking for) | To contact you about Celbrio, as you asked, and plan a demo. We send you marketing emails only if you tick the separate box for that | Steps you ask for before a contract; consent for marketing emails |
| Newsletter sign-up (on the sign-up page, in the sign-up window or through the side tab): your email address, your first name if you give one, and a record of your consent (date and time, a shortened IP address, your browser's user agent, the page and the form you signed up on, and the exact consent text you saw) | To send you the Celbrio newsletter with news, tips and offers about our software, after you confirm by email, and to prove your consent | Consent. You can withdraw it at any time with the link in every email |
| Newsletter discount code: after you confirm, we link a personal discount code (10% off your first invoice) to your subscription; when it is used, the company it was used for (by Chamber of Commerce or VAT number) | To give you the discount you were promised for subscribing, and to apply it once per company | Performing the promised offer; legal obligation for the invoice records |
| Billing details of paying customers | To invoice and keep the accounts tax law requires | Contract; legal obligation |
We do not sell personal data and do not build profiles of you. We do not use customer data for advertising. We show ads on Instagram and Facebook, and use the details you send through an ad form only to contact you about your request.
4. Data we process for customers
As a processor we store and handle what customers put in, which can include: company and tax registration numbers; bookkeeping entries, invoices and bank statement lines (names, IBANs, amounts); tax returns; and for payroll and HR, employee names, citizen service numbers (BSN) or tax identification numbers, dates of birth, addresses, wages, leave and sick reports and pension details; expense receipts and company car details; contacts, orders and shop sales of the customer's own customers (sales, CRM, point of sale and web shop); bills that are emailed or uploaded; and documents with their electronic signatures (name, email address, time and IP address of the signer). We use this only to provide the functions the customer uses, such as preparing and filing returns, producing audit files and reports, and sending reminders.
Citizen service numbers are processed only where the law requires them, such as payroll tax returns and pension reporting.
5. Who receives data
Only when a customer uses the function that needs it:
- Tax authorities, when a return is filed: the Belastingdienst (through Digipoort), the German tax administration (ELSTER), HM Revenue & Customs in the United Kingdom, Skattestyrelsen in Denmark, and the tax administrations of Belgium and France.
- Pension funds or their administrators, when pension reports are sent.
- Business registers: the Netherlands Chamber of Commerce, Companies House in the United Kingdom and the Danish Business Authority, when a company is looked up or annual accounts are filed.
- Banks, when a customer connects a bank account to initiate approved tax payments.
- Bookkeeping and ERP systems that a customer chooses to connect.
- Resend, our email provider, which sends the sign-up confirmation and the newsletter for us and keeps the list of subscribers. Resend acts as our processor under a data processing agreement.
- Google, only when you choose to sign in with Google (Google tells us your email address and confirms it is you) or add deadlines to Google Calendar.
- Email providers that a customer connects, such as the mailbox that receives their bills, or the mail server they use to send invoices, payslips and mailings.
- Meta (Meta Platforms Ireland Ltd), when you fill in a form in one of our ads on Instagram or Facebook. Meta collects the form for us and passes it to us; for showing ads Meta is responsible itself, under its own privacy policy. We download the details from Meta and then delete them there, at the latest within 90 days.
- AI assistants that a customer connects to the software through the API or the Model Context Protocol. The assistant sees what the customer lets it read; its provider handles that data under the customer's own agreement with them.
- Our AI provider, for Celbrio AI: Celbrio AI is off until a customer's administrator switches it on for a company. Then the bill, the figures a question needs or the return being reviewed are processed by AI models hosted in the European Union by our cloud provider. The provider acts on our instructions under a data processing agreement, and does not use the data to train models. Payroll and HR data are not sent to it. Every answer is marked as written by AI, and every use is recorded in the audit trail.
- Our service providers: hosting (TransIP B.V., Leiden, the Netherlands, with servers in the Netherlands) and email (TransIP B.V., the Netherlands). They act on our instructions under a data processing agreement.
Information sent to HMRC
When a return is filed with HMRC, UK law requires us to send fraud prevention information with it. This can include how the software connects, the public IP addresses and ports of your device and of our servers, a device identifier, your user identifier in Celbrio, your time zone, screen and window size, your browser's user agent and do-not-track setting, whether multi-factor sign-in was used, and the software's name, version and licence identifiers. We send this only to HMRC and only with a filing.
6. Transfers outside the European Economic Area
Customer data goes outside the EEA only when a customer files with HMRC (the United Kingdom has an EU adequacy decision) or connects a service based outside the EEA, such as Google or an AI assistant. In those cases the provider's safeguards, such as the EU standard contractual clauses or the EU-US Data Privacy Framework, apply. Our own website and hosting stay in the Netherlands.
Our email provider for the newsletter, Resend, is a company based in the United States. We use its European region, and its safeguards (such as the EU standard contractual clauses) apply to any transfer.
7. How long we keep data
- Account data: for as long as the account is open, and up to 3 months after it is closed so the customer can export their data. Then we delete it.
- Customer data: for as long as the customer keeps it in the software. Tax law obliges businesses to keep their records for several years (seven in the Netherlands); the customer decides how long, and can export everything before closing the account.
- Security logs: up to 12 months. The audit trail of filings stays with the customer's data.
- Details from an ad form: up to 12 months after our last contact if you do not become a customer. If you do, they become part of your account data. You can ask us to delete them at any time.
- Newsletter: your address stays on the list until you unsubscribe. After you unsubscribe we keep your address on a suppression list, so we do not email you again, and the record of your consent for 5 years as proof (the date and time, the consent text you saw and its version, the source of the sign-up). After those 5 years we delete your address and that record automatically and keep only a one-way coded value (keyed hash) of the address, so it is never added again by mistake. The shortened IP address and user agent are deleted after 12 months. Sign-ups you never confirm are deleted after 30 days. Your personal discount code (10% off your first invoice) is kept until you use it, ask us to erase your data, or your data is deleted 5 years after you unsubscribed; a used code is kept as part of the invoice records for 7 years (legal retention duty).
- Our own billing records: seven years, as Dutch tax law requires.
8. Security
Passwords and access keys are stored only as hashes. Access tokens for connected services are encrypted. Sessions use secure, HttpOnly cookies. Every user has roles, filing needs a second person's review, payments need approval, and every action is recorded in a tamper-evident audit trail. Connections to tax authorities use the certificates and encryption each authority requires. If a breach affects your data we will inform the customer and, where the law requires it, the Dutch Data Protection Authority and you.
9. Cookies and storage in your browser
This website sets one functional cookie, celbrio_lang, only if you choose a language in the menu. It stores that choice (for example nl) for 12 months so the home page opens in your language. It holds no personal data and is not used for tracking. The website uses no analytics and no tracking technologies.
Storage in your browser. If you close or complete the newsletter sign-up window, or hide its side tab, we store only that choice and a date in your browser's local storage (localStorage, key celbrio_nl_popup), so the window does not keep coming back. It contains no personal data or identifier, is never sent to us, and expires after 14 days (window closed), 30 days (side tab hidden) or 12 months (signed up); an expired entry is ignored and removed on your next visit. You can clear it in your browser settings. This is functional storage that needs no consent (Article 11.7a(3) Dutch Telecommunications Act).
The Celbrio app sets one strictly necessary cookie that keeps you signed in; it holds a random session code, lasts at most 12 hours, and is not used for tracking.
10. Your rights
You may ask us to see, correct or delete your personal data, to restrict or object to its use, and to receive it in a portable format. Email us and we will answer within one month. For data that a customer controls, we pass your request to them. You may also complain to the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.
11. Changes
We will publish changes on this page with a new version date, and tell customers by email before a significant change takes effect.