Privacy policy

Last reviewed: 9 August 2026.

This policy covers this blog only. Restato Labs is the publisher and the point of contact: [email protected].

What this site does not do

This is a set of static pages. There are no accounts, no sign-in, no newsletter, no comment system and no contact form, so the site itself asks you for nothing and stores nothing you type.

Hosting

Delivering a page over the web necessarily means the host receives technical request data: your IP address, the page requested, the time, and your browser's user-agent string. That is how any web request works, not something this site adds.

What the host does with that data is governed by its own terms, not by this page. The production deployment is not final, so we do not name the provider or describe its practices here — we would only be guessing. This page will be updated before the site is served from its production host, and it will name the provider and link to the terms that apply. For our part, we do not read that data, build a profile from it, or combine it with anything else.

Analytics and consent

No analytics or measurement runs on this site today. When measurement is introduced, it will not load unless you have allowed it through the consent control on the page, and this page will be updated to name the provider before it runs.

Accepting today starts nothing, because there is no measurement code to start. It records a preference for that future, and nothing else happens when you choose.

Your choice is stored in your browser's local storage under the key restatolabs.analytics-consent. It is a single value — accepted or declined — and it never leaves your browser. Declining is a normal outcome, not a degraded one: the site is complete without it.

That control covers analytics only. It does not grant consent for advertising. If advertising is ever introduced, consent for it will be handled separately through the advertising network's supported consent flow, and this page will describe it first.

Advertising

No advertising is served on this site today, and no advertising script is loaded. We intend to apply to a third-party advertising network in future. We do not claim to have been accepted by one. If advertising is ever enabled, this page will be updated first to name the network and describe the choices available to you, and ads will be clearly separated from articles.

External links

Articles link to documentation, source code and other sites as evidence. Once you follow such a link, the site you arrive at applies its own privacy policy, which we do not control.

Retention

We would rather describe this accurately than completely. What we can state today:

• Your consent choice. It stays in your browser until you clear this site's storage. Nothing about it is sent to us, so there is nothing on our side to keep.
• Email you send us. It arrives in an ordinary mailbox and stays there. We have not set a retention schedule for correspondence, and we would rather say so than publish a period we do not keep to.
• Hosting request data. Held by the hosting provider under its own terms, which we do not set and will not paraphrase here.

This page will be updated before any of that changes — before the site collects anything it does not collect today, and before it is served from its production host.

Your choices and questions

You can clear this site's browser storage at any time to reset your consent choice; the control then reappears on your next visit.

Questions about what this site does with data are welcome at [email protected], including questions about a message you have already sent us. We will answer with what we actually know rather than with a policy we have not put into practice.

Children

This blog is written for software practitioners. It is not directed at children, and we do not knowingly collect information from them.

Changes

If what the site does changes, this page changes before the change takes effect, and the review date above is updated.