We collect nothing. You do not have to take our word for it.
What never leaves your device
- The file or text you seal, and its contents.
- Your signing key. It is generated in the page, used once, then discarded.
- Your password and any private fields. They are derived and encrypted in your browser.
What the app does and does not send
- No analytics, no trackers, no beacons. The app depends only on its framework and its own cryptography. No third-party script loads.
- No stored state. Nothing about a seal is written to cookies, localStorage, sessionStorage, IndexedDB, or any cache.
- Same-origin requests only, none carrying your data. Every request goes to this site, never to a third party. Sealing makes one bodyless call for a signed timestamp; choosing “verify a sample” downloads a small sample record from this site. Neither sends any part of your seal, and the timestamp server takes no input, signs the current time, and stores and logs nothing.
Enforced by the browser, not just promised
The site's response headers enforce this at the browser layer, not merely promise it in the code:
- connect-src 'self': the page cannot open a connection to any origin but its own, so even an injected script cannot fetch, post, or beacon data to another origin.
- Referrer-Policy: no-referrer: no URL or referrer leaks on navigation.
- frame-ancestors 'none': the seal and verify tools cannot be embedded and clickjacked.
- Camera, microphone, and geolocation are denied outright.
Verify it yourself, in about a minute
- Open your browser's developer tools and select the Network tab.
- Go to the Seal page and seal a note or a small file.
- Watch the requests. You will see only same-origin requests to this site, plus one bodyless call for a signed timestamp. No third-party origins, and nothing carrying your content.
For the strongest guarantee, download the offline verifier and run it with your network disconnected. It makes no requests at all, enforced by a stricter policy that blocks every connection.
The one thing we disclose
The application collects and logs nothing. Like any site on the public internet, the hosting and CDN layer can passively see standard connection metadata (your IP address and a timestamp) for any request, including the timestamp call. That is connection metadata, not the content of your seal: the server still never sees what you are sealing. We state this plainly in the footer of every page.
Data controller and contact
This site is operated by Attested Intelligence Holdings LLC, which is the data controller for the little this page describes: the connection metadata disclosed above. The application itself collects nothing. Questions about privacy, or about anything on this page: admin@attestedintelligence.com.