Privacy
What this site records, and what it does not
Operated by Tempo AI LLC, accountable for the calculation, publication and correction of every figure published here.
There is no account, no wall and no advertising here, so there is very little to record. What follows is not a policy written next to the code: it is the code. The endpoint described below is /api/t, and its source is in the public repository.
The page count, field by field
Every page carries one line of script that calls /api/t once. That request records exactly six things, and nothing else:
| Field | Value | Why |
|---|---|---|
| type | one of site_visit, cli_query, mcp_call, share | tells a page view apart from a machine read |
| target | the page or category, at most 80 characters | which study is read at all |
| ts | the time, to the second | whether readership grows or stops |
| surface | site, cli or mcp | whether readers are people or agents |
| source_class | agent, human or unknown, from the user-agent string | same question, coarser and never stored raw |
| country | the two-letter country the edge reports | where the readership is, never who |
What is not recorded
No cookie. No local storage. No IP address kept. No identifier at all, not even a hashed one: an earlier version derived a salted daily visitor hash, and it was removed in September 2026 because no written legal basis justified it. One consequence is stated plainly rather than hidden: returning readers cannot be told apart from new ones, and no figure published here claims otherwise. No name, no email address, no profile, no cross-page linking, no third-party analytics, no advertising network.
Who else sees a request
Vercel Inc. serves this site and holds its runtime logs for a short retention window; a request line there carries the path, the response code and the moment, and it is where the counts above are read from before being aggregated. GitHub, Inc. hosts the source repository, so following a source link takes the reader to GitHub under GitHub's own terms. Both are named as processors in the data protection packet that ships with the repository.
Measurement runs are a separate matter from this page: what each run collects, from whom, why, and for how long is declared per run in that same packet, and every published run carries its own legal preflight.
Your rights, and how to use them
Swiss data protection law applies, and the GDPR in addition for data subjects in the European Union. The page count described here is operated by Tempo AI LLC. Write to emea@devlo.ch, the contact point declared in the data protection packet, to ask what is held about you, to have it corrected or erased, or to object. Because this page count holds no identifier, we usually cannot connect a request to a person: that is a limit of the exercise, and the honest answer is that there is nothing to return.
Legal notice · Who operates this · What results cannot tell you