1. Data Controller
We act as the data controller for your personal data - meaning we determine how and why it is processed. Our details are:
KriPa Web, obrt za računalno programiranje, vl. Kristijan Pavlic Tumpa (trading as Ordo)
Owner: Kristijan Pavlic Tumpa
Registered address: Vankina ulica 8, 10000 Zagreb, Croatia, European Union
OIB: 27744574396
Business registration number (MBO): 99336766 · Craft licence no.: 21010165281
Registered with: Obrtni registar - Gradski ured za gospodarstvo, ekološku održivost i strategijsko planiranje, Odjel za gospodarske djelatnosti i rad, City of Zagreb
Email: privacy@ordo-eu.com
Website: ordo-eu.com
As a controller established in the European Union, Ordo is subject to the General Data Protection Regulation (EU) 2016/679 (GDPR), the Croatian Act on Implementation of the General Data Protection Regulation, and all applicable EU data protection law.
Where you are the controller and we are the processor
The paragraph above covers your data - your account, your billing, your use of Ordo. Your clients' data is a different relationship. When you record a client, write an invoice or send a reminder, you decide whose data goes in and why. For that data you are the controller and Ordo is your processor within the meaning of Article 28 GDPR.
In that role we undertake that we:
- process client data only on your documented instructions - what you enter, and what you ask us to send;
- never use it for our own purposes, never sell it, and never use it to train AI models;
- engage only the sub-processors listed in section 5, under equivalent obligations;
- keep it confidential and secured as described in section 9;
- help you answer a request from one of your clients exercising their own rights;
- return or delete it when you close your account, subject to the statutory retention periods in section 7.
What we cannot do for you: you remain responsible for having a lawful basis to hold your clients' data, for telling them you do, and for the accuracy of what you enter. Ordo gives you the tools; the relationship with your client is yours.
These terms serve as our processing agreement under Article 28(3). If your own compliance requires a separately signed DPA, write to us and we will provide one.
2. Data We Collect
Account & Profile Data
- Name, email address, and password (hashed)
- If you sign in with Google: the name, email address and profile picture Google shares with us. Google acts as its own controller for that sign-in.
- A profile picture, if you upload one; your team members see it
- Company name, VAT number, and registered address
- Your national tax or registration number (for Croatian users, the OIB). Collected separately from the VAT number because a business outside the VAT system has one and not the other, and fiscalization is filed under it.
- Legal form (sole trader or company) and, optionally, last year's turnover. Used for one purpose only: working out whether a national e-invoicing mandate applies to you yet. Never used to calculate tax, never shared.
- Details printed on your invoices: bank account (IBAN), logo, invoice language and payment terms
- Profile preferences and settings, including the interface language
- If you turn on two-factor authentication: a record that an authenticator app is set up for your account. The secret that generates your codes is held by our authentication provider, Supabase, not in the Ordo database.
- Which version of these Terms and this Privacy Policy you accepted when you created your account, and when
Business & Invoice Data
- Client information you enter - names, addresses, VAT numbers, national tax numbers (OIB), emails and contact details. A client may be a company or a private individual; where you record an individual, that record is personal data about them and you are its controller - see section 1.
- Invoice data (amounts, dates, line items, payment status, date of supply)
- Delivery details where you add them - the name and address of a recipient other than the client
- Private notes you attach to an invoice. These are stored for you alone: they are never printed on the invoice, never included in the e-invoice, and never sent to your client.
- Saved item templates (descriptions, prices, units, classification codes)
- Documents and PDFs generated through the service
- Incoming eRačuni your suppliers send you, where you use Croatian eRačun - including the supplier's details as they appear on the invoice
Certificates and Signing Credentials
- Where you set them up: your fiscalization certificate, the certificate you seal PDF invoices with, or the credentials for a remote signing service, and the address of a timestamping service. A certificate normally names you or your business. Private keys, passwords and PINs are stored encrypted (AES-256-GCM), are never shown back to you or to anyone else, and are used only to sign your own documents.
Payment Data
- Billing email, billing interval and number of seats
- Stripe customer and subscription identifiers, so a payment can be matched to your account
- Payment method details are processed directly by Stripe, Inc. - Ordo does not store full card numbers
Usage & Technical Data
- IP address, browser type, and operating system
- Pages visited, features used, and session duration
- Error logs and diagnostic data
- A history of changes in your workspace - who created, edited or deleted an invoice, client or setting, and when - shown to the account owner in the app
- Short-lived counters that limit how often a request can be repeated. For the pages your clients open (the online invoice and quote) and the contact form, the counter is keyed on the visitor's IP address.
Cookie Consent Records
- When you answer the cookie banner on ordo-eu.com, we record your choice with the date, your IP address and your browser's user agent, as proof of consent (Art. 7(1)).
Communications
- Emails you send to our support address
- Feedback and responses to surveys
3. How We Use Your Data
| Purpose | Data Used | Legal Basis |
|---|
| Providing the invoicing service | Account, invoice, and client data | Contract performance (Art. 6(1)(b)) |
| Processing subscription payments | Email, billing info | Contract performance (Art. 6(1)(b)) |
| Sending transactional emails (invoices, reminders) | Email address, invoice data | Contract performance (Art. 6(1)(b)) |
| Generating AI-assisted payment reminders | Invoice data, client name | Contract performance (Art. 6(1)(b)) |
| Improving the service and fixing bugs | Usage data, error logs | Legitimate interest (Art. 6(1)(f)) |
| Product analytics inside the app | Pages and features used, your user ID and email | Consent (Art. 6(1)(a)) - withdraw any time |
| Sealing issued PDF invoices, where you set it up | Your certificate or signing credentials; the document's hash | Contract performance (Art. 6(1)(b)) |
| Protecting the service from abuse - rate limits, daily sending limits, bot checks, two-factor sign-in | IP address, account ID, request counts | Legitimate interest (Art. 6(1)(f)) |
| Keeping a record of the Terms you accepted and of changes in your workspace | Account ID, document version, timestamps, changed fields | Legitimate interest (Art. 6(1)(f)) - being able to show what was agreed and who did what |
| Complying with legal obligations (tax, accounting) | Invoice and payment data | Legal obligation (Art. 6(1)(c)) |
4. Legal Basis for Processing
We rely on the following legal bases under GDPR Article 6:
- Contract (Art. 6(1)(b)): Processing necessary to provide the service you signed up for.
- Legitimate Interest (Art. 6(1)(f)): Service improvement, security, fraud prevention. We always balance our interests against your rights.
- Legal Obligation (Art. 6(1)(c)): Where required by EU or Croatian law (e.g. tax record-keeping).
- Consent (Art. 6(1)(a)): Analytics and other non-essential cookies. You may withdraw consent at any time. We do not send marketing emails or newsletters; if that ever changes, we will ask first.
5. Sub-processors & Recipients
We do not sell your personal data. Two kinds of organisation receive some of it. Sub-processors handle data on our behalf, under contract, to run the service. Recipients are public bodies and services that receive data because you asked us to send it to them, and that process it under their own rules as independent controllers.
Sub-processors
| Sub-processor | Country | Purpose | Safeguard |
|---|
| Supabase Inc. | USA company; data stored in the EU (Ireland) | Database, authentication, file storage | DPA, EU Standard Contractual Clauses |
| Stripe Inc. | USA / Ireland | Payment processing, subscription billing | DPA, EU-US Data Privacy Framework |
| Resend Inc. | USA | Transactional email delivery | DPA, Standard Contractual Clauses |
| Vercel Inc. | USA company; the app runs in the EU (Ireland) | Application hosting and CDN | DPA, Standard Contractual Clauses |
| Anthropic PBC | USA | Claude AI - generating payment reminder drafts | DPA, Standard Contractual Clauses. Sent only when you ask for a draft: the invoice number, amount, due date, service description and your client's name. Never used to train AI models. |
| Storecove B.V. | Netherlands (EU) | Cross-border e-invoice delivery over the Peppol network. Not currently in use - the integration is disabled and no invoice data has ever been sent to Storecove. Listed here so that enabling it is never a surprise; we will update this policy before it carries any data. | EU-based processing; DPA to be concluded before any use |
| PostHog Inc. | USA (EU Cloud region) | Two separate uses. Product analytics inside the app - which pages and features are used, linked to your user ID and email - only after you accept analytics; nothing is sent before that. Error diagnostics from our servers - what failed, where, and for which user ID - so we can fix it; these do not depend on your cookie choice. Invoice contents, client details and amounts are never transmitted in either. | DPA, Standard Contractual Clauses; analytics on consent (Art. 6(1)(a)), diagnostics on legitimate interest (Art. 6(1)(f)) |
| ImprovMX | USA / EU | Forwarding of email sent to our support@ and privacy@ addresses to our inbox | Provider's GDPR terms; Standard Contractual Clauses for US processing |
| Cloudflare, Inc. | USA / global network | Turnstile bot check on the sign-up, sign-in and password-reset forms, where it is switched on. Used to tell people from scripts; not used for advertising. | DPA, EU-US Data Privacy Framework, Standard Contractual Clauses |
Recipients
| Recipient | Country | Purpose | Basis |
|---|
| Financijska agencija (FINA) | Croatia (EU) | Croatian eRačun exchange, fiscalization and statutory tax reporting (certified information intermediary under the Croatian Fiscalization Act) - only for Croatian users who enable it | EU-based processing; statutory legal basis (Zakon o fiskalizaciji, NN 89/25) |
| Porezna uprava / APIS-IT | Croatia (EU) | Croatian fiscalization of consumer invoices and statutory e-reporting, sent directly to the tax authority's system (Fiskalizacija 2.0) - only for Croatian users who enable it | EU-based processing; statutory legal basis (Zakon o fiskalizaciji, NN 89/25) |
| European Commission (VIES) | EU | Validating a client's EU VAT number. We send the VAT number you enter and store the result - including the registered name and address VIES returns - as the audit trail EU law requires for a reverse-charge invoice. | EU institution; processing under Council Regulation (EU) No 904/2010 |
| Ministarstvo pravosuđa (Sudski registar) | Croatia (EU) | Looking up a Croatian company by OIB to fill in a client's name and address. Sent only when you press “Fetch from register”; the OIB is the only thing transmitted. | EU-based processing; public register published under an open licence |
| Google | USA | Only if you choose “Continue with Google”: Google confirms your identity and shares your name, email address and picture with us. | Your own Google account terms; Google acts as an independent controller |
| Timestamping and remote signing services you choose | Wherever the provider is | Only if you configure one to seal your PDF invoices. For a timestamp, only the document's hash is sent, never the document. For remote signing, the hash and the credentials you entered are sent to the provider that holds your key. | The provider is yours, under your own contract with it |
We may disclose data to public authorities or law enforcement where legally required.
6. International Data Transfers
Some of our sub-processors are based outside the European Economic Area (EEA), primarily in the United States. All transfers are protected by one or more of the following mechanisms:
- Standard Contractual Clauses (SCCs) approved by the European Commission
- EU-US Data Privacy Framework certification
- Adequacy decisions where applicable
You can request a copy of the relevant transfer mechanisms by contacting us at privacy@ordo-eu.com.
7. Data Retention
| Data Category | Retention Period | Reason |
|---|
| Account data | Until you delete your account | Service provision. Deletion is immediate; there is no recovery period |
| Invoice, client and business data | Until you delete it or your account | Service provision, on your instructions as controller (see section 1) |
| Our own records of your subscription payments | 11 years | Our legal obligation to keep business records under Croatian law |
| Cookie consent records | 3 years, then deleted automatically | Proof of consent (Art. 7(1)) |
| Workspace change history | For as long as the account exists; deleted with it | Lets the account owner see who changed what. Only changed fields are kept, never secrets |
| Record of the Terms and Privacy Policy you accepted | For as long as the account exists; deleted with it | Showing what was agreed, if it is ever in question |
| Rate-limit counters, including visitors' IP addresses | Up to 24 hours, then deleted automatically | Abuse prevention |
| Product analytics and error diagnostics (PostHog) | Up to 12 months | Fixing faults and improving the product |
| Support communications | 3 years | Legitimate interest - resolving disputes |
Note on invoice data: Deleting your Ordo account permanently removes your invoices, clients and files at once, and we keep no copy. The duty to keep issued invoices is yours as the business that issued them, and it usually outlasts any subscription: in Croatia it is 11 years, and other member states set their own periods. Before you delete, download your documents from Settings → Account: a ZIP of every invoice and credit note exactly as issued, with its fiscalization XML. Documents already filed through fiscalization stay with FINA and Porezna uprava under their own rules.
8. Your Rights Under GDPR
As a data subject under GDPR, you have the following rights. To exercise any of them, contact us at privacy@ordo-eu.com. We will respond within one month, which the GDPR lets us extend by two further months for complex requests - we will tell you if we need to.
Art. 15
Right of Access
Request a copy of all personal data we hold about you.
Art. 16
Right to Rectification
Correct inaccurate or incomplete personal data.
Art. 17
Right to Erasure
Request deletion of your data (“right to be forgotten”), subject to legal retention obligations.
Art. 18
Right to Restriction
Request that we limit how we process your data in certain circumstances.
Art. 20
Right to Portability
Receive your data in a structured, machine-readable format. Download it yourself as JSON under Settings → Account, export reports as CSV, or ask us by email.
Art. 21
Right to Object
Object to processing based on legitimate interests, including direct marketing.
You also have the right to lodge a complaint with the Croatian supervisory authority:
Agencija za zaštitu osobnih podataka (AZOP)
Selska cesta 136, 10 000 Zagreb, Croatia
Web: azop.hr · Email: azop@azop.hr
9. Security
We implement appropriate technical and organisational measures to protect your data, including:
- Encryption in transit (TLS 1.2+) and at rest (AES-256 via Supabase)
- Password hashing using bcrypt
- Optional two-factor authentication with an authenticator app, enforced by the application and by the database
- Rate limits, daily sending limits and a bot check on sign-in forms against automated abuse
- Certificates, private keys and signing credentials encrypted separately (AES-256-GCM), readable only by our servers
- Role-based access control - staff can only access data necessary for their role
- Regular security reviews and dependency updates
In the event of a personal data breach that poses a risk to your rights, we will notify the AZOP within 72 hours and you directly without undue delay, as required by GDPR Article 33-34.
10. Children
Ordo is a business tool for users aged 18+. We do not knowingly process the data of anyone under 16 (the GDPR digital-consent age in Croatia). If you believe a minor has provided us with personal data, please contact us immediately at privacy@ordo-eu.com.
11. Changes to This Policy
We may update this Privacy Policy from time to time. If we make material changes, we will notify you by email (to the address associated with your account) and update the “Last updated” date at the top of this page at least 14 days before changes take effect. Continued use of Ordo after that date constitutes acceptance of the updated policy.