Nerela
Back to the app

Cookie Policy

Last updated: 16 October 2026

Nerela uses as few cookies as possible, and draws a careful line between two very different places: the application where you work with your patients (app.nerela.eu), which carries no advertising cookies at all, and the public website (nerela.eu and nerela.lat), where, only if you give us permission, we use advertising cookies from Google Ads and Meta — and you can withdraw it whenever you like.

1. What cookies are

Cookies are small text files stored in your browser. Some are essential for something to work — keeping you signed in, remembering your language, remembering this very decision. Others exist to measure which ad brought you here, and those require your prior permission.

2. The application does not load advertising

On app.nerela.eu, where your patient records, sessions and clinical notes live, no Google, Meta or other network tag is loaded, and no third-party advertising cookie is installed. There is no banner because the decision about marketing is made on our public website, before you reach the application: only the cookies needed to run the application operate there. The only link with advertising is the one described in section 3: if you accepted marketing cookies on the website, the nerela_attrib cookie stores two Meta identifiers for up to 90 days and, when you create your account, our server notifies Meta.

This is not a preference we can quietly change — it is the reason you can handle health data in Nerela at all.

One clarification about Meta: its cookies (_fbp and _fbc) are written by the pixel for the whole domain of the public website (nerela.eu or nerela.lat), so, if you accept them, your browser also sends them to app.nerela.eu along with your other cookies. The application does not write them and has no advertising tag loaded.

3. The public website does use advertising, with your permission

On nerela.eu and nerela.lat we advertise on Google and Meta (Facebook and Instagram) so that other psychologists can find us. To know which ads work, and to optimise them without burning the budget on the ones that do not, we use the Google Ads cookies and the Meta pixel listed in the table. They do not switch themselves on: until you press “Accept” on the cookie notice, your browser stores no Google Ads or Meta cookie, and the Meta pixel is not even loaded.

We use Google Consent Mode, the mechanism through which Google's tag learns your decision and honours it. If you say no, Google receives only an anonymous signal — no cookies, no identifiers — that a visit happened, and nothing more. The Meta pixel has no such mode: if you say no, it is not loaded and Meta receives nothing about your visit.

If you accept, the Meta pixel stores the _fbp and _fbc cookies (the latter only if you arrive from a Facebook or Instagram ad) and sends Meta your browser identifiers, your IP address, your browser and the page you visit, together with the visit events: viewing the page, pressing the sign-up button or pressing the WhatsApp button. Nothing from the application and no patient data is sent to Meta. The Privacy Policy (section 11) explains that processing.

4. Strictly necessary cookies

These do not require prior consent under the ePrivacy Directive. Even so, every one of them is listed in the table below, with its lifetime and what it does.

5. Our own measurement

The nerela_attrib and nerela_utm cookies record which campaign, search or link you arrived from (nerela_utm holds the campaign's utm tags for 30 days), so that when someone creates an account we know what brought them; those tags also travel in the sign-up link to the application. They are our own cookies on our own domain: they are shared with nobody, never cross-referenced against any other database, and they never store Google's or Meta's click identifier.

6. Product analytics

Inside the application we use no product analytics tool — neither cookie-based nor cookieless. If we ever turn one on, it will carry no persistent per-visitor identifiers, and we will update this page beforehand — never silently.

7. Changing or withdrawing your decision

At the foot of any page on nerela.eu and nerela.lat there is a “Cookies” link that reopens the preferences panel. Withdrawing permission costs exactly what granting it costs: one click. When you withdraw it, the Meta pixel stops sending data and we delete its cookies from your browser. Your decision is stored separately on each domain: if you make it on nerela.eu, nerela.lat asks you again.

You can also delete or block cookies in your browser settings. If you block the necessary ones, the application stops working normally — you would have to sign in on every visit, and it would not remember your language.

8. Changes to this policy

If we add a new purpose, we update this page and ask you again: your previous decision stops counting automatically, because the permission you gave was for something else. We do not widen the use quietly.

CookieWhereWhat forLifetimeType
sb-access-token / sb-refresh-tokenapp.nerela.euKeeping you signed in (Supabase Auth)Session / up to 1 yearStrictly necessary
nerela_localeBothRemembering which language you want Nerela in1 yearStrictly necessary
nerela_consentnerela.eu, nerela.latRemembering your decision about these cookies180 daysStrictly necessary
nerela_attribnerela.eu, nerela.latRemembering which campaign or search you arrived from90 daysOur own measurement
nerela_utmnerela.eu, nerela.latRemembering the utm tags of the campaign that brought you, to link them to your sign-up30 daysOur own measurement
_gcl_aunerela.eu, nerela.latGoogle Ads: knowing which ad brought a new account90 daysAdvertising — only with your permission
_fbpnerela.eu, nerela.latMeta: recognising your browser to measure and optimise our ads90 daysAdvertising — only with your permission
_fbcnerela.eu, nerela.latMeta: remembering the click on a Facebook or Instagram ad that brought you (only if you arrive from one)90 daysAdvertising — only with your permission
Cookie Policy · Nerela