[18.4., 14:24] Yannick Schroth: @⁨Kai⁩ bin grade nochmal am whitepaper dran. wie würdest du das auf deutsch neu formulieren mit der neuen technologie?

A unique, invisible verification code is embedded directly into the image. This code consists of a prefix and a partial hash (e.g., "0-a1b2c3"), creating a tamper-evident seal that travels with the photo.
[18.4., 14:25] Yannick Schroth: und das hier stimmt so nicht, oder? "The hash is stored securely on our servers. Importantly, only the hash is stored. The original image cannot be reconstructed from it, ensuring full GDPR compliance and enabling immediate, permanent deletion when required."
[18.4., 14:25] Yannick Schroth: und das fällt jetzt weg, oder? "Anyone can verify a photo's authenticity by entering the 6-digit code on our web app or through API integration. If the image has been altered in any way, verification fails instantly."
[18.4., 14:26] Yannick Schroth: stimmt das hier noch? "Change just one pixel, adjust the brightness by 1%, or crop a single millimeter, and the entire hash changes completely."
[18.4., 14:27] Yannick Schroth: das hier stimmt so auch nicht, oder? "Many verification systems rely on blockchain or IPFS. These technologies are designed for permanence. But permanence is the enemy of privacy. When users have the right to be forgotten, immutable storage becomes a liability.

TrustCamera takes a different approach. We store only the cryptographic hash, never the image itself. This hash cannot be reversed to reconstruct the original photo. It's a one-way proof that the image existed in a specific form, nothing more."