Browser key persistence test
Does a non-extractable Ed25519 key, stored in IndexedDB, survive a week of not visiting the site? Safari's Intelligent Tracking Prevention caps script-writable storage and clears it after a period without first-party interaction. This page measures whether that happens, and whether the key still works afterwards.
Bookmark this exact link
The start date lives in the link, not in the browser. That matters: if the storage is cleared, the record of when the test began would be cleared with it, and the result would be unreadable. Keep the link and you can always tell how long has passed.
How to run it
- Press Arm the test below. A key is generated and stored; nothing leaves this browser.
- Bookmark the link it gives you.
- Do not visit this site again for at least eight days. Any visit counts as first-party interaction and resets the clock, which would invalidate the run.
- Come back via the bookmark and read the verdict.
What this can and cannot tell you
It measures what this browser does to an idle origin. It is a
proxy for app.obravera.com, not a measurement of it —
a real creator's key survives or not according to their own visit pattern,
not yours. Each browser and device is its own data point; a phone may
behave differently from a desktop.
The test deliberately does not call
navigator.storage.persist(). That is a mitigation, and calling
it would measure the mitigation instead of the default behaviour creators
will actually get. Whether the browser granted persistence on its own is
reported below.
Browser: