the walkthrough
Protect. Watch. Prove.
What actually happens when you sign a photo with Priorframe, told plainly.
act 01 · protect
A seal, a fingerprint, a timestamp.
The moment you protect a photo, three things are computed: a cryptographic hash, which identifies the exact file, a perceptual fingerprint, which identifies how the image looks, and an embedding, which lets our matching models reason about what the image contains.
All three are sealed into a registry record with a signed timestamp. The record states one thing, plainly: this image was signed and registered, in your hands, at this moment, before it appeared anywhere else.
Your photo is not altered. No watermark, no pixel changes, no quality loss. The seal lives in the registry, not in your file.
{
"record": "sig_01j9zk7q4r8w",
"asset_sha256": "9f2a4c1d8f3b…e8c41b",
"fingerprint": "phash:c4d1a29e",
"embedding": "sig-clip:768d",
"signed_at": "2026-07-12T14:02:11Z",
"signer": "acct_wren_studio",
"status": "sealed"
}scanning public web surfaces
act 02 · watch
Scans that see what reverse search misses.
Priorframe scans the web for images that match your fingerprints, on an honest rhythm: new work is scanned right away, pinned work is watched closely week by week, and the rest of your library is covered in rotation.
Exact copies are the easy part. Perceptual matching also catches crops, mirrors, filters, screenshots, and re-encodes, the everyday disguises of a reposted image.
For AI derivatives, matching runs on embeddings: images that stay suspiciously close to your composition, your subject, your frame. Each candidate gets a similarity score. Detection is a probabilistic signal, and we label it that way in every alert.
Monitoring is best effort, and we use those words on purpose. The web is large and the people who take images adapt. We would rather promise you honesty than everything.
act 03 · prove
A record you can hand to anyone.
Every protected photo has a public verify page: the content hash, the signing time, and the account that signed it. No login is required to read it. Evidence that hides behind a login is not much of an exhibit.
Most social platforms strip embedded content credentials the moment you upload, and your record survives that: the verify link keeps working, and the fingerprint registry re-identifies your image even after the credential is stripped.
When a copy surfaces, your alert holds the side by side, the similarity score, and a takedown letter drafted from your record. The letter is a template you review and send. It is not legal advice, and we are not a law firm. It is your record, arranged to be taken seriously.
record verified
- signed_by
- wren.studio
- signed_at
- 2026-03-14T09:21:07Z
- asset_sha256
- 9f2a4c1d…e8c41b
- status
- first publication recorded
Ready when you are.
Join the waitlist and get an invite from the first wave.