Open your sealed link

This counts page asset and cache loads, which are not assignment transmission. The meter cannot see or classify the sealed fragment.

What happened when you opened it

Your assignment travelled in the part of the link after the #. Browsers never send that part to a web server, so it is not in our logs, our host's logs or a chat app's link-preview fetch. This page's only network activity is fetching the site's own HTML, CSS and JavaScript. It decrypted your assignment inside this tab. We store nothing about you. The one thing kept on your device is the site's own code, cached so the tool keeps working offline.

The counter in the strip above is the weakest of the three ways to check this. It starts counting when this page's JavaScript runs, and the sealed payload was already in the address bar before that. What keeps your assignment off any web server is the browser rule described above. To check that yourself, watch your browser's own network panel, or read the site's methodology page, which ranks all three checks.

Every sealed link loads this same page and shows the same preview card, whoever it was made for. The card cannot say anything about you, because the page knows nothing until it runs on your device. Opening a link does not use it up: your organizer's copy still works, and nothing you do here changes what anyone else sees. If a link fails to open, it was damaged on the way.