Legal · ePrivacy

Cookie policy

Last updated: 1 October 2026 · Version 1.2

This translation is provided for convenience. In case of any discrepancy, the Dutch version prevails.

In short: Budgetto uses only strictly necessary cookies: one to keep you signed in and, while you sign in with Google, a second one for ten minutes. No tracking, no analytics, no third-party cookies, no pixels.

§01

What is a cookie?

A cookie is a small text file that a website places on your device so it can recognise you on a later visit. Cookies can be strictly necessary (signing in, security) or not (tracking, advertising, analytics).

§02

Which cookies we use

Two, both strictly necessary:

Name

budgetto_session

Type

Strictly necessary

Duration

7 days

Owner

This instance

Purpose

Remembering that you are signed in, so you do not have to sign in again on every page. The cookie holds a signed JWT token and is HttpOnly + SameSite=Lax + in production Secure. It cannot be read by JavaScript.

Name

budgetto_oauth_state

Type

Strictly necessary

Duration

10 minutes

Owner

This instance

Purpose

Protects signing in with Google against a forged request. It holds a random code, your language (for the welcome email) and, if you link Google to your account, your account ID. Only set when you click "Continue with Google" or "Link Google", and cleared as soon as you come back from Google. It cannot be read by JavaScript.

Without the first cookie you would have to sign in again on every request, and without the second, signing in with Google could not be done safely. That is why both are strictly necessary and do not require consent.

§03

What we do not use

  • ×No Google Analytics, Plausible, Matomo or any other analytics tool.
  • ×No Meta Pixel, TikTok Pixel, LinkedIn Insight or any other tracking pixel.
  • ×No Cloudflare Insights, Vercel Analytics or CDN tracking.
  • ×No advertising cookies and no third-party cookies.
  • ×No localStorage or sessionStorage to track you; what your browser does remember is listed below.
§04

What else your browser remembers

Besides the cookies, your browser remembers a few things, never to track you:

  • →On this device: your language, light or dark mode, which button you want in the bottom bar and that you have seen the cookie notice, and for each profile your most recently used categories (as numbers, cleared when you sign in or out) and a few display choices, such as whether the chart starts at zero. If you have more than one profile, also that you have seen the short explanation by the profile button.
  • →In each tab: which profile you are viewing and which profile is yours, and, if you open a link from one of our emails, the code from that link until the page has used it. If you open an invitation, also the code from the invitation link and, if it is about giving a child their own profile, a marker saying so, until you accept or decline the invitation or sign out. It all disappears when you close the tab.
  • →If the app has already reloaded the tab once after a fault, the tab remembers that until you close it, so it never keeps reloading.
  • →When you sign in or out in one tab, or change the settings of your profile, the browser tells your other Budgetto tabs straight away. Nothing is stored for that.

None of this is passed to anyone else. To clear it, delete the site data for budgetto.be in your browser.

§05

How to manage cookies

Because we only use strictly necessary cookies, there is nothing to choose in the app. The cookie for signing in with Google disappears on its own; if you want to remove the session cookie:

  • →Click Sign out in the sidebar and the cookie is cleared server-side.
  • →Or clear cookies for this domain in your browser settings, which signs you out.

Tip: most browsers have a private or incognito mode in which all cookies disappear as soon as you close the window.

§06

Changes

If we ever add a cookie that is not strictly necessary, a clear consent request will appear first and this document will be updated with a new version number.

§07

More information

The technical and legal details on how we protect your data are in our privacy policy.