cookie policy

last updated 2026-08-20 · briven.tech

This page explains every cookie briven.tech sets, what each one is for, and why you have not been shown a consent banner. It supplements §9 of the Privacy Policy, which remains the fuller description of how personal data is handled.

The short version. briven sets cookies for one purpose only: keeping you signed in. There are no analytics cookies, no advertising cookies, no session-replay tools and no third-party trackers on this site. Nothing measures you here.

1. What a cookie is

A cookie is a small piece of text a website asks your browser to keep and hand back on your next request. It is best thought of as a cloakroom ticket: the site gives you a token, and when you come back the token is how it recognises which coat is yours. Without one, every page you loaded would be a stranger arriving for the first time — which is why signing in would be impossible.

The ticket can also be used for things that have nothing to do with the cloakroom: the same mechanism is what lets an advertising network recognise you across unrelated websites. That second use is why cookie law exists, and it is the use briven does not make.

2. The cookies briven actually sets

Cookies on briven.tech are set by briven.tech itself — first-party — and are sent only to briven.tech and its subdomains.

• briven.session_token — your sign-in session. This is the only cookie that persists. It is set when you sign in and it is what keeps you signed in as you move between pages. It carries a session token, not your password and not your personal details. It is HTTP-only, meaning JavaScript running in the page cannot read it, which is what stops a script injected into the page from stealing your session. In production it is marked Secure, so the browser will never send it over an unencrypted connection. It lasts 30 days on a sliding basis: continuing to use briven extends it, and 30 days of not using it lets it expire on its own. Signing out clears it immediately.
• Short-lived sign-in cookies. Completing a sign-in involves a couple of temporary cookies that exist only for the duration of that exchange — they carry the state needed to finish the step safely and are cleared once you are in. They share the same briven. prefix, so anything you see beginning with it in your browser’s cookie list came from us and from nothing else.

That is the complete list. Nothing on this site sets a cookie for measurement, advertising, personalisation, or A/B testing, and no cookie is set at all until you sign in — reading the marketing pages leaves no persistent cookie behind.

3. Fonts are self-hosted, so nobody is told you visited

This is not a cookie point, but it is the same question underneath: does anyone else learn that you were here?

Most websites load their typefaces from Google Fonts, which means your browser makes a request to Google every time you open a page — sending your IP address and the page you are on, before you have clicked anything, and with no cookie involved that a banner would ever mention. briven does not do this. The typefaces are self-hosted at build time and served from briven.tech along with the rest of the page.

The consequence is worth stating plainly: no request leaves your browser for Google, and no third party is told who is visiting this site. You can verify it yourself in about ten seconds — open your browser’s developer tools, switch to the network tab, and reload this page. Every request goes to briven.tech.

4. Why there is no consent banner

Under the ePrivacy Directive (2002/58/EC, as implemented in Belgian law), consent is required before storing or accessing information on your device — except where the storage is strictly necessary to provide a service you have explicitly requested. That exemption is written into Article 5(3) of the Directive itself, and a session cookie for a service you asked to sign in to is the textbook example of it.

Every cookie described in §2 falls inside that exemption. The session cookie exists because you asked to be signed in, and without it the dashboard cannot work at all; the sign-in cookies exist to complete a step you initiated. None of them is used for measurement, profiling or advertising.

So briven does not show you a consent banner, for the simple reason that there is nothing to consent to. A banner asking permission for cookies that are legally exempt would not protect you; it would train you to click “accept all” on a site that never needed to ask, which is precisely the habit that makes the banners on other sites work as well as they do.

The commitment attached to that: if briven ever introduces a cookie that is not strictly necessary — anything analytical, and certainly anything advertising — a genuine consent mechanism appears first, with a real refusal option, and this page is rewritten in the same change. The absence of a banner is a statement about what the site does, and it stops being true the moment the site does more.

5. Third parties

No third party sets a cookie on briven.tech, and no third-party script runs on it. There is no analytics provider, no tag manager, no advertising network, no social embed, no chat widget and no session-replay tool.

Two honest notes. First, links from this site to other websites are ordinary links: once you follow one, that site’s own cookie practices apply and briven has no say in them. Second, the third parties that do process data on briven’s behalf — the mail provider that sends your sign-in codes, for instance — sit on the server side and set nothing in your browser. All of them are listed at /subprocessors.

6. How to see and clear cookies

You are in control of these, and nothing you do to them breaks anything except your sign-in.

• The simplest way: sign out of briven. That clears the session cookie straight away.
• In your browser: every major browser lets you inspect and delete cookies for a single site. In Chrome and Edge it is under Settings, then Privacy and security, then Cookies and site data. In Firefox it is Settings, then Privacy & Security, then Cookies and Site Data. In Safari it is Settings, then Privacy, then Manage Website Data. Find briven.tech in the list and remove it.
• Blocking them entirely: you can block cookies for briven.tech in your browser settings. The marketing pages will work normally; signing in will not, because there is nowhere left to keep the session.

Deleting the session cookie signs you out on that browser. It does not delete your account, your databases or anything stored in them.

7. Changes to this policy

This page is updated whenever the cookies briven sets change. Material changes are posted here with a new “last updated” date, and where a change means a new category of cookie, it is announced to account owners by email as described in the Privacy Policy before it takes effect.

8. Contact

Questions about cookies or anything else on this page: privacy@flndrn.com. Legal: legal@flndrn.com. Support: support@flndrn.com. See also the Privacy Policy for the full account of what data briven holds and why.