Cookies.
There is no cookie banner on this site because there is nothing to consent to. This page exists so you can check that claim instead of trusting it.
The short version
Browsing aiterm.app sets no cookie on your browser. No tag manager, no advertising pixel, no session replay, no session cookie for visitors.
We do count visits, and we do it without storing anything on your machine: no cookie, no identifier, nothing that survives your visit. How that works is spelled out in section 3.
Two things do touch your browser storage: four local storage keys on the blog that decide whether to show the newsletter card, and one cookie on the private admin area that only the site owner ever sees.
1. What we do not use
To be explicit, because most sites claiming to be light still ship these:
- No Google Analytics, no Matomo, no account with any company whose business is your data.
- No Google Tag Manager and no tag container of any kind.
- No Meta, LinkedIn, X, TikTok or Reddit pixel.
- No advertising or retargeting cookie, and no data broker.
- No A/B testing, heatmap or session replay tool.
- No embedded social widget or chat bubble loading third-party cookies.
- No cookie, no local storage key and no identifier of any kind used to measure your visit.
This is also why the site has no consent banner. French and European rules require consent for storage that is not strictly necessary, and for audience measurement that goes beyond plain statistics. We store nothing on your device and we do not profile anyone, so there is nothing to ask you.
2. What is actually stored
| Name | Type | Purpose | Lifetime |
|---|---|---|---|
aiterm:blog-email-capture:* |
Local and session storage, blog pages only | Four keys that remember whether the newsletter card was already shown, dismissed or subscribed to, so it does not follow you around. They stay in your browser and are never sent to a server. | Until you clear your browser data |
aiterm_admin |
Cookie, HttpOnly, Secure, SameSite=Strict | Session cookie for the private back office at /admin. Set only after a successful password login, which only the site owner can do. It never appears on public pages. |
7 days |
Both are strictly necessary to the function they serve, so neither requires consent. Neither is used to profile you or to measure your visit.
3. How we count visits
We want to know how many people read this site and which pages are worth writing. Every tool that answers that question normally hands you an identifier and follows it around. We do it without one.
When you load a page, our server takes your IP address and your browser's user agent, mixes them with a random number drawn fresh every night, and keeps only the resulting hash. That hash is what counts as one visitor for the day. It cannot be reversed into an IP address, and once the nightly number is thrown away, nothing links yesterday's hash to today's. Come back tomorrow and you are a new, equally anonymous visitor.
Your browser sends one small message when you leave a page: the path you were on, how long the tab was in front of you, the site that referred you, and whether you clicked a download or subscribe button. No identifier travels with it, because there is none to send.
What we end up with is a table of counts: visits per day, most read pages, referring sites, countries, average time on page. No individual profile, no path through the site attached to a person, nothing sold and nothing shared with an advertiser or a data broker. Under French and European rules this is audience measurement strictly limited to statistics, which is exempt from consent, and that exemption is the reason you are not looking at a banner.
Alongside our own counting, the page loads Vercel Web Analytics, run by the company that already hosts this site. It works on the same principle, sets no cookie and stores nothing in your browser. It is served from aiterm.app rather than an external domain, so you will see it in your network tab as /_vercel/insights/ and nothing is requested from a third-party host. Vercel's own description of what it collects is public in their analytics privacy policy.
The files doing this on our side are readable from the site itself: /assets/measure.js in your browser, and the counting endpoint it posts to at /api/track.
4. Third-party requests
Two external hosts are contacted while a page renders, and neither of them sets a cookie for us:
- Google Fonts (
fonts.googleapis.comandfonts.gstatic.com) delivers the typefaces. Your browser sends its IP address, user agent and the referring page to Google when it fetches a font file. This is a connection, not a cookie, but it is a transfer of data and you should know about it. - YouTube thumbnails may load on some blog articles. Video players are not embedded, so no YouTube cookie is set unless you click through to YouTube itself.
The app itself is a separate matter: AITerm is a native macOS application and has no cookies at all. What it sends over the network is listed line by line in the privacy policy.
5. Staying in control
You can clear or block all of this from your browser settings, under privacy or site data for aiterm.app. Clearing local storage resets the newsletter card, which may reappear once. Nothing else on the site depends on browser storage, so blocking it entirely does not break anything.
If you would rather not be counted at all, switch on Do Not Track or Global Privacy Control in your browser: both are checked before anything is measured, and nothing is sent. Any content blocker has the same effect, and the site works exactly the same either way.
6. Checking for yourself
Open your browser developer tools, go to the storage or application tab, and load any page of this site. The cookie list for aiterm.app will be empty, and so is local storage outside the blog. The network tab shows every request the page makes: the measurement ones are served from aiterm.app itself, and the only external host remains Google Fonts.
If you find something that contradicts this page, that is a bug and we want to hear about it: hello@aiterm.app.
7. Changes
Audience measurement was added on 3 August 2026, and this page was rewritten the same day to describe it. The commitment behind it has not moved: if we ever want to measure something that needs your consent, a banner appears first and nothing loads before you agree. As long as this page describes counting without identifiers, there is nothing to agree to.