Cookies and Local Storage

A cookie is a small file a site stores on your device. Similar technologies include localStorage, sessionStorage, pixels, and fingerprinting scripts. Romanian Law 506/2004 and the ePrivacy Directive require information and, for non-essential storage, consent before storing or accessing information on your terminal.

This Service’s application code does not store information on your terminal except what your browser does by itself when it renders a first-party page (for example, keeping the document in memory or in back-forward cache). The create and reveal interfaces wipe plaintext on a persisted pagehide so a restored page does not show a secret. That wipe is application memory, not a cookie.

• No first-party or third-party cookies.
• No localStorage, sessionStorage, or draft persistence of plaintext, keys, proofs, or capability links.
• No analytics, tag manager, advertising, social pixel, or consent-management platform.
• No captcha widget and no third-party font or embed on create or reveal.
• No fingerprinting script and no Topics / interest-based advertising API (those APIs are also disabled in Permissions-Policy).

• The browser keeps the current page in RAM and may snapshot it for back-forward cache. That is the user agent, not an Operator cookie.
• If you choose Copy, the operating-system clipboard holds text you asked to copy. Clear it yourself if the device is shared.
• Password managers are instructed not to store the secret textarea, the capability field, or the copy fallback node. A manager that ignores those hints is outside our control.
• The hosting provider may process connection metadata (including a connection address) to deliver TLS and HTTP. That is infrastructure, described in Infrastructure and Subprocessors, not an application cookie.
• If you visit the Operator’s portfolio or a public-authority site from a footer link, that other site has its own cookies and policies.

In your browser’s developer tools, open Storage / Cookies for this origin. You should see no cookies set by the application. Network requests on create and reveal should stay same-origin. If a browser extension injects cookies or scripts, that extension is not part of the Service.

If a future version sets a strictly necessary cookie or any non-essential storage, this page will be updated before that storage is used, and non-essential storage will not run without the consent required by law. Until then, treat “no cookies” as a current fact of the shipped application, not a marketing slogan. Questions: alex.jungean@gmail.com.