FAQ

What we've described is very similar to classical digital watermarks, but there's more to Sasha Signatures than that. Outside of ensuring that every Signature is unique, we also tie other unique data to the particular image at hand, making it extremely hard to move a signature from one image to another.

While the image is slightly altered as part of embedding the signature, it is done in a way that only minimally interferes with human perception. Technically speaking, embedding a signature typically results in a PSNR loss 47 which is equivalent to saving a JPEG image at 90% quality.

Never. Everything runs on-device. Our models identify what to protect without processing the actual content. All that is embedded into the image is a unique randomized numeric value. This identifier can not be traced to image content, or to who added the Signature, or to where it was done.

All data is stored with the platform to ensure the highest level of privacy. Should someone manage to find the signature, it will not make sense and even with access to our technology, they would not be able to access related user data.

No, we don’t believe so: we’ve gone to great lengths testing against “adversarial attacks” where a signature is applied to another image. In each case so far, we’ve been able to detect it.

All data is stored with the platform to ensure the highest level of privacy. The signature is simply a reference.

No. SASHA protects the original intention for all photos, whether private or commercial. How that works technically depends on the individual partner platforms and their setup.

Unlike hashing systems, which require an exact match and are vulnerable to edits, SASHA’s pixel-level protection embeds invisible watermarks that are resilient to manipulation and maintain user privacy. SASHA is part of the StopNCII community.

C2PA aims to trace media origins using public metadata, while SASHA focuses on protecting images with invisible watermarks to enable prevention at upload. C2PA traces where media comes from via public metadata. No enforcement capability. SASHA embeds protection into the image and enables active blocking. Complementary, not competing. SASHA is a member of C2PA and CAI.

Technically, we won’t require any additional image storage, as the image with the SASHA Signature embedded is a pure function of (some-id, image). The stored signature is only around 60 bits.

The signature embedding adds milliseconds to the processing time at load (depending on the image size) with no visible impact on the user experience. In practice, this remains well below typical network variance and image delivery times.