Cookie Policy

Most cookie policies are long because the site behind them is doing a lot. Ours is short for the opposite reason.

This website sets no cookies unless you agree to them. Not for advertising, not ever — and not for analytics either, unless you say yes when we ask.

We count visits in two different ways, and only one of them involves your device at all. The first runs for everyone and stores nothing. The second is Google Analytics, which does use cookies, and which we do not load at all until you have said yes. Decline and it is never fetched; accept and later change your mind, and we delete what it left.

One thing is stored on your device, and only if you ask for it: if you use the light/dark switch, your choice is remembered so the site does not forget it on the next page. That is described in full below.

We would rather show you that than ask you to take our word for it, so this page explains what cookies are, what we do instead, and how you can check.

What cookies are

A cookie is a small file a website asks your browser to store, so it can recognise your browser later. Related technologies do the same job by other means — local storage, session storage, tracking pixels, and browser fingerprinting, which infers who you are from your device’s characteristics rather than storing anything at all.

Under EU law — the ePrivacy Directive as implemented in Portugal, alongside the GDPR — a site must get your consent before storing or reading anything on your device, unless it is strictly necessary to deliver something you asked for. Analytics is not strictly necessary. Advertising certainly is not.

What we use instead of cookies

Nothing. To be specific about it:

Technology	Do we use it?
Cookies	Only if you accept Google Analytics. None otherwise
Local storage	One item, only if you use the theme switch
Session storage	No
Tracking pixels or web beacons	No
Analytics	Two counts — one cookieless and always on, one cookie-based and only with consent. See below
Advertising or retargeting tags	No
Embedded third-party media	No
Browser fingerprinting	No

The site is a set of static pages. Your browser downloads them, and the only thing running afterwards is the page counter described in the next section — which never learns who you are.

Analytics

We measure two things, in two different ways, and the difference is what you are being asked about.

The one that always runs

Cloudflare Web Analytics. It stores nothing on your device — no cookie, no local storage, no identifier that outlives the tab. There is nothing left on your machine for anyone to read on your next visit.

It records the page you opened, the site you arrived from if there was one, and coarse facts about your setup: country, browser, operating system, and whether you are on a phone or a computer. It does not record your IP address, and it never sees anything you type.

Counting different visitors without storing anything is done with a one-way hash calculated per request and changed every day. Changing it daily is the point: yesterday’s visit cannot be joined to today’s, so no profile of you accumulates anywhere.

This one needs no permission, and that is not a loophole. EU rules require consent for storing or reading things on your device. This stores nothing, so there is nothing to consent to. We tell you about it because being exempt from asking is not the same as being exempt from saying.

The one we ask about

Google Analytics. It sets cookies — _ga and _ga_ followed by an id — which is storage on your device, which needs your permission first.

So we do not load it until you give that permission. Not “load it and hold the cookies back”: the script is never fetched at all until you accept. Decline, and your browser never contacts Google on our behalf.

If you accept, these appear:

Name	Purpose	Expires
_ga	Tells one browser apart from another, so a returning visit is not counted as a new person	2 years
_ga_<id>	Keeps the state of the current session for this specific site	2 years

We turn off Google’s advertising features on this property — no ad personalisation, no cross-site signals. It is used to see which pages are read, not to follow you.

Changing your mind. Choose “No thanks” and we delete the _ga cookies immediately and stop loading the script. You can also clear site data in your browser at any time, and nothing about the site breaks either way.

What we store on your device

Two values, both in local storage, both put there by something you did:

Name	Value	Purpose	Expires
theme	light or dark	Remembers the appearance you chose	Never, until you clear it
analytics-consent	granted or denied	Remembers your answer, so we stop asking	Never, until you clear it

Neither is a cookie: both stay in your browser and are never sent to our server. The second one exists because you were asked — without it the banner would reappear on every page, which is its own kind of rude.

Until you touch that switch, nothing is stored at all and the site simply follows your device’s own light or dark setting.

This is not a cookie — it is never transmitted to us, and our server never sees it. It identifies nothing about you: the entire content is the word “light” or the word “dark”. It needs no consent banner, because ePrivacy rules exempt storage that is strictly necessary for something you explicitly asked for, and clicking a theme switch is exactly that. Being exempt from asking is not the same as being exempt from telling you, which is why it has a section.

To remove it, clear site data for rimembo.com in your browser, or switch the theme back — the site works identically either way.

Third-party cookies

Two, and only with the limits described above.

Cloudflare serves the page-view counter’s script. Google serves Google Analytics, and only after you accept. Nothing else on this site is loaded from anyone else’s server. That is a deliberate build decision, not luck: our typefaces are downloaded at build time and served from our own domain rather than requested from Google Fonts, and there are no embedded videos, maps, chat widgets, comment systems, or social buttons that phone home.

That leaves the two counters, and we would rather be exact about them than round in our own favour. The cookieless counter’s script is fetched from Cloudflare, and Google Analytics — if you accept it — is fetched from Google. Both are third-party requests. Neither is an advertising tag, and the first stores nothing at all, but a script from someone else’s server is a script from someone else’s server and the honest word for it is third-party.

Cloudflare also hosts the site and provides its DNS. Hosting anything means the host handles the request — that is what hosting is — and their servers log it, as every web server has since the web began.

The only exception is links. When you follow a link to another website — the App Store, Google Play, or one of the regulators named in our other policies — you are on their site under their rules, and they may well set cookies. That is outside our control and begins the moment you click.

What our server records

Serving a page requires a request, and requests leave a trace. Our hosting provider keeps short-lived technical logs — the page requested, the time, a browser user-agent string, and the IP address the request came from — for security and troubleshooting. These are not cookies, they are not tied to a profile of you, they are not used for analytics, and they age out automatically.

What the app does

Rimembo itself is a mobile app, not a website, and it does not use cookies. It does use local storage on your own device to keep you signed in and remember your settings, and it uses Google Analytics for Firebase to understand which features get used.

That is a different system with different rules, and it is covered in the Privacy Policy rather than here.

Checking that this is true

You do not have to believe us:

• Open your browser’s developer tools, go to the storage or application tab, and look at cookies for this domain. It will be empty.
• In the same tab, look at local storage. It will be empty too, unless you have used the theme switch — in which case it holds exactly one entry, theme.
• Look at the network tab and check the domains being contacted. Everything comes from rimembo.com.

If you ever find that untrue, please tell us at legal@rimembo.com — it would be a bug, and we would want to fix it.

Managing cookies generally

Since we set none, there is nothing here to turn off. For the rest of the web, every major browser lets you view and delete stored cookies, block third-party cookies, and clear everything on exit — under Settings, usually within a Privacy section. Blocking cookies on some sites will break sign-in; on this one it will change nothing at all.

If this ever changes

If we later decide we need analytics, we will not simply switch it on. We would update this page first, explain what is collected and why, and ask for your consent before anything is stored — with declining as easy as accepting, and no pre-ticked boxes. Until you agreed, nothing would be set.

Get in touch

Email: legal@rimembo.com

Website: www.rimembo.com