invoia
WhyProductPricingDevelopers
Sign inStart free
invoia

Product

  • Features
  • Pricing
  • Documentation

Company

  • Contact

Legal

  • Privacy
  • Terms
  • Cookies
  • Security

Language

/

© 2026 invoia · Creo Digital · CVR DK45246132

Cookie Policy

2.1 · Last updated: 08/07/2026

On this page

  • 01Introduction
  • 02What cookies are
  • 03What we do not use
  • 04Cookie inventory
  • 05Your choices
  • 06What your choice does not control
  • 07Browser settings
  • 08Changes to this policy
  • 09Contact
  • 10Governing language

On this page

  • 01Introduction
  • 02What cookies are
  • 03What we do not use
  • 04Cookie inventory
  • 05Your choices
  • 06What your choice does not control
  • 07Browser settings
  • 08Changes to this policy
  • 09Contact
  • 10Governing language

Introduction#

This Cookie Policy sets out which cookies and similar technologies invoia uses, what each of them does, how long they stay on your device, and what you can do about them.

invoia is provided by Creo Digital, CVR DK45246132. Creo Digital is the data controller for the personal data processed through cookies and similar technologies on invoia.io.

This policy describes what the code actually does. Where we have not been able to verify something, we say so rather than guess.

In short

  • Most of the cookies we set are necessary in order to sign in and to complete a connection to an accounting system. Without them the service does not work.
  • We use no marketing or advertising cookies, no Google Analytics and no tag management tool.
  • We measure page views using Vercel Web Analytics. That measurement is not currently conditioned on your cookie preference — see What your choice does not control.
  • Your cookie preference is stored solely in your own browser. We keep no record of it.

What cookies are#

A cookie is a small text file that a website stores on your device and that is sent back with your next request. Cookies are used, among other things, to keep you signed in and to remember a choice you have made.

First-party cookies are set by invoia.io and can only be read by invoia.io. Third-party cookies are set by a domain other than the one you are visiting.

Session cookies are deleted when you close your browser. Persistent cookies stay until they expire or until you delete them. Our sign-in cookie is persistent, with a lifetime of 400 days. It is not a session cookie.

Similar technologies#

In addition to cookies we use browser storage (localStorage) in exactly one place: to remember your cookie preference. Entries in localStorage have no expiry, and none is set. They stay until you change your choice or clear your browser data.

We do not write to sessionStorage or indexedDB, and we use no service worker.

On /sign-in and /register a device check also runs. It reads technical characteristics of your browser — screen resolution, fonts and canvas rendering among others — and computes a device identifier from them. The computation itself happens in your browser, and neither the characteristics nor the device identifier is sent to a third party. The library we use for the computation occasionally sends an anonymous usage request to the vendor's own domain (m1.openfpcdn.io); that request contains no information about you beyond your IP address and browser identification. The identifier is sent to our own server together with the sign-in and registration request. As part of the check, a cookie named cookietest is written and immediately expired again, to test whether cookies are enabled at all.

No cookie banner is shown on /sign-in or /register.

What we do not use#

  • No Google Analytics. There is no Google Analytics, no Google Tag Manager and no analytics service other than the one listed in the inventory below.
  • No marketing, advertising or retargeting cookies and no advertising pixels. We share no information with advertising networks.
  • No cross-site tracking and no profiling for marketing purposes.
  • No fonts fetched from Google. Fonts are bundled when the site is built and served from our own domain, so your browser sends no request to Google to fetch them.

Cookie inventory

Necessary cookies

These cookies are necessary for you to sign in, to stay signed in, and for a connection to Dinero or e-conomic to be completed securely. They cannot be opted out of in our cookie settings. If you block them in your browser, you cannot use the service.

  • sb-<project-ref>-auth-tokeninvoia (Supabase)

    Keeps you signed in and holds your session with Supabase, which provides our authentication. The <project-ref> part is a fixed identifier for our Supabase project. Where needed the cookie is split into numbered parts (.0, .1 and so on) because the contents can be too large for a single cookie. It is persistent, not a session cookie.

    Lifetime
    400 days
    Type
    First-party cookie
  • sb-<project-ref>-auth-token-code-verifierinvoia (Supabase)

    Temporary PKCE verifier used during sign-in with Google or Microsoft. It ties the response from the sign-in provider to the browser that started the sign-in, so a response cannot be injected from another browser.

    Lifetime
    Short-lived — used and removed when the sign-in flow completes
    Type
    First-party cookie
  • oauth_registrationinvoia

    Marks that a sign-in with Google or Microsoft was started as the creation of a new account rather than an ordinary sign-in, so that you are routed into the right flow afterwards.

    Lifetime
    5 minutes
    Type
    First-party cookie
  • invitation_tokeninvoia

    Carries an invitation through the sign-up flow. Holds the invitation token, the invitee's email address and the name of the inviting account. Deleted once sign-up is complete.

    Lifetime
    1 hour
    Type
    First-party cookie
  • onboarding_in_progressinvoia

    Remembers that you are in the middle of setup while you are sent to Dinero or e-conomic and back again, so that you land in the right place in the flow.

    Lifetime
    30 minutes
    Type
    First-party cookie
  • dinero_connect_nonceinvoia

    One-time value ensuring that the response from Dinero belongs to the connection you started yourself. Protects against someone else initiating a connection on your behalf.

    Lifetime
    10 minutes
    Type
    First-party cookie
  • dinero_reauth_integration_idinvoia

    Remembers which existing Dinero connection is being re-authorised while you are at Dinero.

    Lifetime
    10 minutes
    Type
    First-party cookie
  • economic_connect_nonceinvoia

    One-time value ensuring that the response from e-conomic belongs to the connection you started yourself.

    Lifetime
    10 minutes
    Type
    First-party cookie
  • cookietestinvoia (FingerprintJS)

    Written and immediately expired as a test of whether cookies are enabled in your browser. Set only on /sign-in and /register as part of the device check.

    Lifetime
    Expired immediately
    Type
    First-party cookie
  • invoia-cookie-consentinvoia

    Stores your cookie preference for the three categories so that the banner is not shown again. It sits in browser storage on your own device and is not sent to us.

    Lifetime
    No expiry — browser storage does not expire on its own
    Type
    Browser storage (localStorage)

Functional cookies

These cookies remember a choice you have made so that you do not have to make it again. They are not necessary for the service to work.

  • NEXT_LOCALEinvoia

    Remembers the language you selected in the language switcher, so that pages are shown in the same language next time.

    Lifetime
    1 year
    Type
    First-party cookie

Statistics

We measure which pages are visited in order to understand what is being used. That measurement currently runs on every page and is not conditioned on your cookie preference.

  • Vercel Web AnalyticsVercel

    Measures page views on every page — both the public pages and the pages you see once signed in. The measurement script is loaded from our own domain and the measurements are sent to our own domain. We have checked in the browser on invoia.io that the measurement neither sets cookies nor writes to browser storage, and that no request is sent to a third-party domain. Vercel receives the address visited and your IP address; the latter happens in any event, because Vercel is our hosting provider and therefore receives all traffic.

    Lifetime
    Sets no cookie
    Type
    First-party script

Third-party scripts on individual pages

On individual pages we load a script from another provider, or a library in our own code sends a request to the provider's domain. We do not control what those providers store on your device. Your IP address and browser identification are necessarily visible to them when the request is made.

  • js.stripe.comStripe

    Loaded on the payment step during sign-up and on the payment card panels under Billing. Stripe carries out the card payment and guards against misuse. Card details are entered directly into Stripe's own field and never reach our servers. On our own domain we have observed the cookie __stripe_mid, which Stripe uses to recognise the device in its misuse checks. Stripe may set further cookies under its own cookie policy; __stripe_sid was not present at the time of measurement, and we have not verified it.

    Lifetime
    Determined by Stripe
    Type
    Third-party script
  • m1.openfpcdn.ioFingerprintJS

    The library that computes the device identifier on /sign-in and /register sends an anonymous usage request to the vendor's own domain on roughly one in a thousand loads. The request contains neither the device identifier nor any of the characteristics read, but FingerprintJS sees your IP address and your browser identification when it is sent.

    Lifetime
    Sets no cookie
    Type
    Third-party request

Marketing

We use no marketing, advertising or retargeting cookies. There are no cookies in this category, and we share no information with advertising networks.

We use no cookies in this category.

Your choices#

The first time you visit our public pages we show a cookie banner. You can choose Accept all or Reject all, and you can reopen the cookie settings and change your choice at any time.

In the settings you can switch the statistics and marketing categories on and off. The functional category cannot be switched off there. The marketing category is empty, because we use no cookies for that purpose.

Your choice is stored in your own browser under the key invoia-cookie-consent. It is not sent to us, and we keep no record of what you chose. If you clear your browser data, the choice is gone and the banner appears again.

Necessary cookies cannot be opted out of. If you block them in your browser, you cannot sign in, and a connection to Dinero or e-conomic cannot be completed.

What your choice does not control#

We would rather say this plainly than let a button promise more than it delivers:

  • Page-view measurement runs on every page, whatever you choose. Switching statistics off in our cookie settings does not currently change whether Vercel Web Analytics loads.
  • The device check on /sign-in and /register runs on every page load, whatever you choose.
  • The cookie banner and the cookie settings exist only on our public pages. They are shown neither on /sign-in and /register nor inside the signed-in workspace, even though page-view measurement runs there too.
  • Reject all removes nothing that is already on your device and unloads no script. The choice only changes a setting in your own browser.
  • We cannot document your choice. It exists only in your browser and is never sent to us.

So there are two things you can actually do: change the preference here on the site, and block or delete cookies in your browser. The second is the one that works without reservation — see Browser settings.

Browser settings

Most browsers let you inspect, block and delete cookies from their settings. Choose your browser below to see how.

  • Google Chrome

    Settings > Privacy and security > Cookies and other site data

    View instructions
  • Mozilla Firefox

    Settings > Privacy & Security > Cookies and Site Data

    View instructions
  • Safari

    Settings > Privacy > Manage Website Data

    View instructions
  • Microsoft Edge

    Settings > Cookies and site permissions > Manage and delete cookies and site data

    View instructions

Changes to this policy#

We update this policy when the cookies or scripts we use change. The version in force and the date of the most recent update appear at the top of the page.

No separate consent to the Cookie Policy is obtained when you create an account, and we keep no record of which version of the Cookie Policy an individual user has seen.

Contact#

If you have questions about our use of cookies, you can write to us:

Creo Digital CVR DK45246132 support@invoia.io

If you wish to exercise a right under the General Data Protection Regulation, the procedure is set out in our Privacy Policy, which also describes our processing of personal data more broadly.

Governing language#

This Cookie Policy was drawn up in Danish, and the Danish version is the legally binding one. The English version is a translation made available for ease of reading. In the event of any discrepancy between the two versions, the Danish version prevails.