ONIX Viewer privacy policy

Applies to the Chrome, Firefox and Safari extensions. Last updated 27 September 2026.

What ONIX Viewer collects

Nothing. ONIX Viewer has no accounts, no analytics, no telemetry, no crash reporting and no third-party code. It does not know who you are, which pages you visit, or what is in them, beyond rendering the one page you have open.

What it stores

Nothing. The extension stores nothing at all: it asks the browser for no permissions, and nothing about the pages you view, or anything else, is written anywhere.

What it sends

Nothing to anyone. The extension makes exactly one kind of network request: a re-fetch of the page you are already viewing, from the same address, to read its XML source. That request goes to the server the page came from and to no one else. The links to EDItEUR's code-list pages in the viewer are ordinary links that you choose to open; they carry no referrer.

What it can see

To render an ONIX file, the extension reads the content of the page you have open, on your machine. It acts only on pages served as XML whose content is ONIX, and leaves every other page exactly as the browser shows it. The permission wording in the browser's settings ("read and alter web pages you visit") is the browser's blanket description of any extension that runs on web pages; what this one does with that access is described above and can be verified in the source.

Verifying this

The extension's source is public at github.com/rognlien/onix-viewer. SECURITY.md there lists what to look for: one permission, no host permissions, no background process, no remote code, and one fetch whose argument is the page's own address. The tests hold those claims in place.

Changes and contact

If any of this ever changes, this page changes first and the change is listed in the changelog. Questions go to the issue tracker.