PRIVACY, WITH INTENTION
Know what Pegham protects, what the service needs to process, and the choices that stay in your hands.
One-to-one messages use Olm sessions through a native cryptographic library. Shared files have separate device-generated keys; groups use MLS. The service relays encrypted content without receiving the message or file decryption keys.
Pegham uses signed, single-use invitations. Compare your contact’s device fingerprint through a channel you trust before sharing. A changed identity needs your attention; a name or avatar alone is not proof of identity.
Export an encrypted history file and save its recovery secret separately. Pegham does not keep a recovery copy of that secret. Restoring saved history does not restore an old device’s messaging identity or verified sessions.
Manage read and view receipts, optional activity alerts, incoming calls and conversation muting. Select the verified contacts who receive each Moment. Camera and microphone permissions are requested for the features that use them.
Account identifiers, public keys, device registrations, group membership, routing records, timing and encrypted file sizes are service metadata. Network providers process connection information. Encryption does not make Pegham anonymous or prevent a recipient from saving content.
Pegham is in development. The composed application and backup format have not received an independent security audit. Calls, background behavior and other release checks are still being completed. Never treat an app preview as a security certification.
Read our privacy policy for data handling, providers and retention. For account removal, see delete account. To report a security issue, email hello@dpuzzles.com with a description and safe reproduction steps. Do not include real private conversations or cryptographic secrets.
