Cookie notice

1. Essential use

Clavis uses strictly necessary browser storage and related technical mechanisms for secure authentication and session handling.

These mechanisms are required to maintain authenticated session state, protect sign-in and token flows, and prevent replay or abuse.

2. Cloudflare Turnstile (abuse prevention)

On account registration, when you add or replace a passkey, and during account recovery, we may send device and browser signals to Cloudflare so those steps are not completed by automated abuse. Turnstile may set or read cookies or similar storage according to Cloudflare's configuration.

We treat that transmission as a security measure those actions require. We do not add a separate confirmation screen for it. We do not use it for advertising or to measure behaviour.

If we add measurement tags, or if we send these signals on any other action, we will update this notice and carry out the publication or other steps the law then requires.

3. Typefaces (Adobe Fonts)

clavis.nexus and docs.clavis.nexus load their Japanese typeface from Adobe Fonts. When a page opens, your browser sends Adobe Inc. (United States) your IP address and browser details, the page's host name, and which characters the page needs — the set of characters, not the text.

Adobe uses this to deliver the typeface and to count font usage, including paying the font foundries. Adobe states that it receives the IP address so that it knows where to deliver the font and does not store it, and that it does not set or use cookies to serve fonts (adobe.com/privacy/policies/adobe-fonts.html).

The account and signing site (id.clavis.nexus), the developer console (developers.clavis.nexus), the archive (archive.clavis.nexus) and this legal site (legal.clavis.nexus) do not load Adobe Fonts.

We do not use this transmission for advertising or to measure behaviour. If your browser blocks use.typekit.net, the pages display in your device's own fonts.

4. Non-essential tracking

Clavis does not currently use advertising cookies or behavioural tracking cookies for profiling.

clavis.nexus and docs.clavis.nexus do not load measurement tags or use cookies for measurement. We may aggregate access on the side that serves the pages, without storing anything on your device (Privacy Notice, section 3). When you press the button on clavis.nexus that asks an AI service about Clavis, your browser sends DeepDive (clavis.nexus) a request for a small image. The request carries which button and which AI service you chose and the time, together with what every request carries (your IP address and browser details). We use it only to count the presses. Nothing is stored on your device for this.

Payment for paid features moves you to Polar's site. We do not load Polar's programs on Clavis sites. Cookies on Polar's site follow Polar's notices.

If this changes, we will update this notice and implement any additional controls required by applicable law.

5. Your language choice

When you choose a language in the language menu on a Clavis site, we store that choice in a cookie named clavis_lang for clavis.nexus and its subdomains, so that every Clavis site opens in the language you chose. The cookie holds only the language code (for example en or ja) and expires after one year.

We set it only when you choose a language. We do not use it to identify you, for advertising or to measure behaviour, and access aggregation does not read it. Choosing "Use browser language" in the menu deletes it.

If you are signed in and have a contact email, the language you choose also becomes the language of the emails Clavis sends to that address.

6. What you choose to keep on this device

On the account and signing site (id.clavis.nexus), if you turn on the record kept on this device, the signing screen keeps the name, identifiers, and time of each signature in your browser's local storage, up to the latest 120. It is off by default and is not sent to us.

Whether the signing sound is on is kept in the same storage.

7. Browser controls

Users may control cookie and storage behaviour via browser settings, but restricting essential mechanisms may prevent login or SSO functionality from operating correctly.