Open your sealed link

What just happened, and what didn't

Your assignment travelled in the part of a URL after the #. Browsers never send that to a web server, so it is not in our logs, not in our host's logs, and not in a chat app's link-preview fetch. This page fetched its own HTML, CSS and JavaScript when it loaded — that is the whole of its network activity — and then decrypted the rest inside the tab you are looking at. 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 that, and it would be dishonest to present it as the strongest. It can only start counting once this page's JavaScript exists, and the sealed payload was already in the address bar before that — no arm point can pre-date it. The real argument on this page is the one about the fragment, and the way to verify it independently is your browser's own network panel, or the site's methodology page, which ranks all three and says which is which.

Every sealed link produces exactly this page and exactly the same preview card, whoever it was made for — the card cannot say anything about you because the page it describes does not know anything until it runs on your device. Opening a link is also not a one-way door for anyone else: your organizer's copy still works, and nothing you do here changes what anyone else sees. If a link ever fails to open, it has been damaged in transit rather than used up.