Privacy

Last updated: 8 August 2026

In short

This site uses no cookies, stores nothing in your browser, does not profile anyone and shows no advertising. That is why there is no banner to accept: there is nothing to consent to.

Two things are still measured, both in aggregate and without identifying anyone: how often a page is read, and how much traffic the site receives. How, is written below.

Who handles the data

The site is run by Frank Le Rouxe, personally. For any question: [email protected].

The reading counter

Articles and lessons may show a number of reads. Its only purpose is to understand which content people find useful, and it works like this: when you open a page, the site tells its own counter which content you are reading.

To avoid counting the same person ten times, the system computes a cryptographic fingerprint of IP address, browser, content and day, mixed with a secret key. That fingerprint is not reversible: the IP address cannot be recovered from it. The plain IP address is never stored, and the fingerprints are deleted after two days.

There are no cookies, no identifier follows you from page to page, and no single person's path through the site can be reconstructed.

Traffic statistics

To know how many people visit the site I use Cloudflare Web Analytics, which collects aggregate data: page views, referrers, device type, without cookies and without building profiles. Individual visitors cannot be identified.

Network and security

The site is served through Cloudflare, which acts as a content delivery network and protects the server. Like any service of this kind, it logs incoming requests for technical and security reasons, under its own policies.

Videos

Lessons embed videos hosted on YouTube, but the player loads only if you press play. Until you do, no request is made to YouTube and no cookie is set. From the moment you start the video, YouTube's own terms apply, over which I have no control.

Donations

Support buttons lead to a payment page operated by Stripe. Payment happens entirely on that service: no payment data passes through or is stored here.

Why I process this data

The legal basis is the legitimate interest in understanding which content people find useful and in keeping the site reachable and secure. With no profiling and no advertising, the effect on visitors is minimal. It is also why you are not asked for a consent that would serve no purpose.

Your rights

Let me start with the concrete part, which is also the answer to anyone asking for a copy of their data: I have no archive to extract it from. There are no accounts, I keep no IP addresses, there are no user profiles, and the counter's only technical fingerprints delete themselves within two days. Since I cannot identify you from that, I would not even ask you for additional data to try: that would be the opposite of the point.

The rights the regulation gives you remain nonetheless: to know what data concerns you, to ask for its correction or deletion, to restrict the processing or to object to it. To exercise them, or to tell me something looks wrong, write to [email protected]. You can also contact your data protection supervisory authority, in Italy, the Garante per la protezione dei dati personali.

The request logs kept by Cloudflare for technical reasons follow that service's policies, not mine.