How Herpegram protects your Transmissions.
Private Transmissions are end-to-end encrypted. This page explains what that means for your privacy and how to respond to security warnings.
What end-to-end encryption protects.
Messages are encrypted on your device before they are sent. Encryption protects their contents in transit, but cannot protect an unlocked or compromised device or stop a recipient from sharing them.
If a fingerprint changes unexpectedly, stop.
If Herpegram warns that a contact’s encryption identity has changed, do not ignore it. Verify the person using another trusted method before continuing.
Encryption has boundaries.
Claims such as “completely invisible”, “unhackable” or “zero metadata” would be technically dishonest. The useful version is knowing exactly what is protected and where the boundary sits.
- A compromised or unlocked device can expose whatever that device is able to decrypt while it is compromised.
- End-to-end encryption cannot stop the other participant from copying a message, photographing the screen or sharing information after they have received it.
- Herpegram still needs limited metadata to operate the service, such as account and conversation identifiers, device routing information, delivery state and timestamps. E2EE protects message content; it does not make all service metadata disappear.
- View-once media reduces persistence inside Herpegram, but it is not an anti-camera or anti-screen-recording guarantee.
- A malicious browser extension, operating-system compromise or sufficiently powerful malware can attack data after your browser decrypts it. E2EE cannot repair an already compromised endpoint.
Trust the encryption warning more than the conversation.
If Herpegram reports a local-key mismatch, changed peer key or unrecognised encrypted session, do not override it just because the message you were about to send feels urgent. Verify the other Variant through a separate trusted channel first.