Skip to content

Type something to search the manual

    Privacy

    AI-Guide is a free site. This page explains in plain words what happens to your data when you use it, no legal filler.

    Fabrizio La Rosa, Belgian VAT BE1031214819, based in Ghent, Belgium. You can reach me through the form at the bottom of the About page, or by writing to [email protected].

    • No tracking or advertising cookies.
    • No Google Analytics, Meta Pixel, or advertising trackers.
    • No accounts, no logins.
    • No newsletter, no mailing lists.

    To know how many people read the site and which pages are useful, I use Simple Analytics, a European service (Netherlands) built specifically not to profile anyone. What it collects:

    • Number of visits per page.
    • Which site you came from (referrer), if any.
    • Country, device type, browser, in aggregate form.

    What it does NOT collect:

    • No cookies.
    • No ID or fingerprint that follows you across sessions or sites.
    • No stored IP address (it’s used on the fly to derive the country, then discarded).
    • No personal data.

    That’s why the site has no consent banner: there’s nothing to ask your permission for. Details on what Simple Analytics collects.

    A technical note: even if you have Do Not Track turned on in your browser, visits still get counted. The DNT signal asks not to be profiled; here there’s no profiling to turn off, so excluding DNT users would only mean dropping the most privacy-aware readers from the aggregate numbers.

    Beyond page visits, I also count in aggregate form a few specific actions that help me understand which parts of the manual actually work:

    • Exercise opened: when you copy, download, or open one of the exercise files. I send the file name.
    • Prompt builder: when you copy the prompt assembled by the builder in the What is a prompt? lesson.
    • Share: when you click one of the icons at the bottom of a lesson. I send only the channel name (X, LinkedIn, WhatsApp, email, copy link).
    • Recap with your AI: when you generate a recap prompt, along with how many lessons you’ve completed.
    • Glossary: when you ask your AI to explain a term better, with the term name.
    • App installed: when you add AI-Guide to your device’s home screen, and when the manual has been fully downloaded for offline reading.

    None of these events carry anything that could identify you. They are just aggregate counts, from which I can’t tell who made them, where from, or exactly when.

    The site sits behind Cloudflare as a reverse proxy: it serves the pages quickly worldwide and protects against abusive traffic. To do this Cloudflare sees your IP address, which is unavoidable (it needs to know who to answer). It doesn’t use cookies to profile you; in rare cases (anti-bot challenge) it may show a check with a very short-lived technical cookie.

    Cloudflare keeps standard access logs (IP, user agent, URL) for limited periods, for technical and security reasons. These are the logs any web server keeps by default. I don’t use them for profiling.

    Details in Cloudflare’s privacy policy.

    AI-Guide uses localStorage to remember which lessons you’ve started or finished, how long you’ve spent on them, and your last position in the manual. That data powers the “Pick up where you left off” and “Recap with your AI” features.

    It never leaves your browser. It doesn’t reach me, or any third party, or any external service. It lives in localStorage and that’s it.

    You can clear it at any time with the “Clear progress” button at the bottom of the “Pick up” card on the homepage.

    If you use the “Write to me” form on the About page, or send an email to [email protected], your message lands in my own email client. The mail sits on my email provider’s server. I don’t forward it, I don’t add you to any list, I don’t use it for anything other than replying.

    Technically there’s no user database for me to modify or delete. If you want a check or an action on any data in my server logs, write to [email protected].

    If the policy changes (for example because I introduce a feature that needs some new data) I’ll update this page and flag it in the footer or homepage for a reasonable period.


    Last updated 2026-05-13.