Checking invitation…
Private until you share. Keep your originals and download your recovery file after saving. There are no retained backups; storage loss can erase a submission. Your recovery file holds keys, not a copy.
Nothing saved yet. Your draft stays only in this tab.
One last look
Ready to save?
Waiting for confirmation
Keep this tab open.
If the connection drops, saving may already have worked. Retry checks the same submission—it won’t create a duplicate.
Not a receipt yet. This private file contains keys and the exact encrypted request; use “Open a saved prediction” below to resume. Nothing retries automatically.
Saved privately
Now keep your recovery file.
This is how you open your prediction later. Keep it somewhere private: anyone with a copy can read and re-share everything; access cannot be revoked. Keep your originals too—the recovery file is not a submission backup.
Receipt & sharing options
Sharing your recovery file or link gives full access to every prediction and note. Prefer the file. Links may remain in browser history, sync, extensions or clipboard history even after this page removes the fragment.
Open a saved prediction
Your recovery file
Choose your private recovery file to open a saved prediction, or a pending file to resume saving. No invitation needed to read your own submission.
Nothing opened.
Opened only in this browser
Privacy, file limits & how this works
Your browser encrypts the exact originals and any notes. The server stores encrypted bytes, not your decryption key. No AI, OCR, analytics or automatic publication. No routine owner viewer.
Up to 12 predictions; screenshots together up to 8 MiB. Static PNG, JPEG or WebP; up to 16 megapixels and 12,000 pixels per side. Interpretations and notes are yours, not verified findings.
No automatic or off-host backups are configured. A recovery file holds keys and access information, not a copy of your submission. Keep your originals: server storage loss can permanently erase submissions. Keys cannot be reset.
This pilot is not independently audited or externally witnessed. An operator changing the web client could capture secrets. A receipt proves server registration, not authorship, screenshot authenticity or original date. Request time, size and path are not anonymous.