Privacy

No hosted service

There is no Norien server operated by anyone else. The registry, the runtime supervisor, and this web app all run as local processes on your own machine, and the database is a file in your project directory. Nothing you publish, install, or search for is transmitted to us, because there is no us to transmit it to.

No analytics, no tracking

This site loads no analytics script, no tag manager, no advertising pixel, and no third-party font. It sets no cookies. Nothing measures your visit.

Requests that do leave your machine

The data API reads from external providers, and those requests go out over the internet. When you open a token, wallet, contract, or project page, your Norien instance queries the providers you have configured, using the API keys you supplied. Those providers see the requests, and their own privacy policies apply to them.

You control this entirely. Every provider credential is optional — leaving one unset disables that provider rather than breaking anything, and the settings page shows exactly which are configured and reachable.

Your credentials

Provider API keys live in .env.local on your machine and are read only by the server process. They are never sent to the browser, never included in a response, and never written to logs — the outbound HTTP client strips query strings before logging a URL specifically so a key embedded in one cannot leak into a log file.

CLI credentials live in ~/.norien/config.json, again on your machine.

When this changes

A hosted registry and account system are planned. When they exist, this page will be replaced with a policy describing what that service stores — account identity, published records, and the operational logs any server keeps. It will be written before the service launches, not after.

Questions

Get in touch if something here is unclear.