ObliviOS Developer portal Project site

Home / Decisions / ADR-261

Turn on Vercel Web Analytics for oblivios.org, and make the issue rule one.

Accepted, recorded 18 November 2026.

Decision
ADR-261
Date
2026-11-18
Status
AcceptedAccepted (owner, 2026-11-18: Vercel Analytics on, to see whether there is interest; the issues are on, resolve the rule).
Mentioned by
ADR-264, ADR-272

1Decision

Turn on Vercel Web Analytics for oblivios.org, and make the issue rule one. (1) The owner wants to see whether there is interest, so the site counts page views with Vercel Web Analytics. It amends the privacy rule of the launch design (section 5.4: no analytics) and the line of the site \"no tracking\".

Vercel documents it as cookie free, a visitor as a hash that lasts a day, and the data points as the page, the referrer, the country and the browser, system and device type, with no tie to an IP address. It needs one script; the site carries it as <script defer src=\"/_vercel/insights/script.js\">, from its own address, only in a build that Vercel makes (VERCEL=1), so the local build, the review build and the snapshot have none.

check-build.mjs accepts exactly that tag in a Vercel build, requires it on every page there, and fails on any other script (checked: a second script fails). Speed Insights and the toolbar stay off. The Privacy page, the footer line and the README of site/ say so. (2) The sentence of the Privacy page that the owner uses only GitHub's traffic page is removed: the owner is not sure it is true.

(3) The rule for a vulnerability is one rule: an issue is fine for anything, an email is for whoever wants the problem not public before it is fixed, and encryption is optional. SECURITY.md of the four repositories (commits 9d8ef6f, 1f42fcb, 70f6fd0 and the source copy in tools/docs/), the Security, Contact and FAQ pages say it. Issues are on in all four repositories (gh api, 2026-11-18).

2Why and evidence

The product is a privacy system and the site said it ran no script; a script of the platform that serves the site is the smaller cost against not knowing whether anyone cares, which the owner weighed. The count is anonymous by Vercel's own description, and the script comes from the site's own origin, so the site still makes no request to another host and the policy default-src 'self' holds. Rejected: no analytics (GitHub traffic only), a third-party counter, a script in every build (the local build and the review build would carry a path that does not exist off Vercel).

3Consequences

Done and read on 2026-11-18: the tag appears once on each of the eleven pages in a build made with VERCEL=1 and on none in a local build; the check accepts it and fails on a second script; the page texts and the launch design are amended; the issue settings read with gh.

Not done: the analytics itself (it works only after the owner clicks Enable under Analytics in the Vercel project, which adds the routes /_vercel/insights/* at the next deployment; the path of the script is the one the plain HTML documentation of Vercel names /<unique-path>/script.js, and the classic path is used here, which a first deployment has to confirm); the limits and the price of Web Analytics on the owner's plan (Vercel's documentation says it is available on all plans; the limits page was not read); the wiki and the projects of the four repositories are on, and R-3 says they stay off.

4Review when

A deployment shows that the script path is not served; Vercel changes the terms or the data points; the owner turns the analytics off or wants a different measure of interest.

Read from docs/governance/decision-log.md, entry ADR-261.