Protection,
without the guesswork.

Find what’s private.

Hide Sensitive Data reads the capture on your Mac and counts the e-mail addresses, phone and card numbers, IBANs and keys still showing: the button says how many. One click hides them. Nothing leaves your Mac to do it.

It finds what text recognition can read. Small, blurry or unusual text can be missed, so look at the capture before you share it. Detection is never presented as perfect.

Replace the pixels.

Secure Redact writes a solid, fully opaque colour into the covered region of the exported image. The export is a freshly rendered image, with no embedded original and no editable layers. It is pixel replacement: not encryption, and not a blur filter.

The cover is applied to the capture before blur, pixelate and the magnifier, and once more on top of every mark, so nothing drawn later can show what was covered and the magnifier only ever enlarges the cover. Adjusting contrast can’t recover pixel values that are not in the file. Cover the whole detail, its edges included: what is around it can still give it away.

Blur and pixelate are visual effects. They are not presented as protection for passwords, numbers or other secrets. No security certification or independent audit is claimed.

Check exact file bytes.

The editor demo can export a SHA-256 checksum of the exact image file it downloads. A checksum is a fingerprint, not encryption and not a digital signature. It carries no trusted time and no identity. Keep the reference checksum somewhere you trust: anyone who can replace both files can make a matching pair.

Saving an image again or changing its metadata usually changes its checksum, even when it looks the same. A matching checksum says nothing about whether the scene shown is true.

Prove when it existed.

A trusted timestamp can show that a file existed no later than a certain time: a fingerprint of the finished file is signed by an independent service, and anyone can check that signature later. The image itself doesn’t need to be sent anywhere. Open standards for this include RFC 3161 timestamps and OpenTimestamps; C2PA can carry signed provenance and edit history.

What a timestamp can’t do: it doesn’t establish the moment of capture, the truth of what was on the screen, or who made it. A date written inside an image can be bound to its fingerprint, but it may have been wrong from the start.

SimpleShot doesn’t offer a time proof yet. When it does, this page will say exactly what it proves and what it doesn’t.