Privacy Policy

Hasher is designed with privacy as a core principle.

We do not collect personal identifiers such as:

• Names
• Email addresses
• Phone numbers
• Contacts

Hasher does NOT collect personal data or identifiers, including:

• Contact lists
• Call logs
• Message content
• Media content in plaintext
• Device hardware identifiers
• Hardware fingerprints
• Advertising identifiers

Hasher uses zero-knowledge, end-to-end encryption.

All messages, voice notes, media, and calls are encrypted on the user's device before transmission.

Hasher servers store only encrypted data.

We cannot read or access message content.

Decryptor passwords and device keys never leave your device unless you enable recovery; recovery stores only hashes for rebinding.

Camera and microphone access occurs only when the user explicitly initiates:

• Voice recording
• Media capture
• Calls

These permissions are:

• Requested at runtime
• Used only while the app is in the foreground
• Released immediately after use

Captured media is encrypted on-device before upload.

Hasher uses cryptographic device keys generated on the user's device to manage access.

Biometric unlock is optional. When enabled, authentication is performed by the device operating system.

Hasher does not collect, store, or access biometric identifiers. The OS manages biometrics and only returns a success or failure signal.

If biometric unlock is enabled, a copy of your private keys is stored locally on your device's secure storage so the app can unlock without your decryptor.

These keys:

• Are cryptographic device keys, not hardware fingerprints
• Are not derived from device identifiers
• Are bound only by explicit user action
• Can be reset by uninstalling the app

Only public cryptographic keys are stored on servers.

Each account supports one active device key at a time; rebinding requires explicit user action and (if enabled) recovery verification.

Servers may store:

• Encrypted message blobs
• Encrypted media blobs
• Cryptographic device public keys
• Subscription verification tokens
• Optional recovery hashes

No plaintext content is stored.

Hasher does not log message content.

We do not use invasive analytics or tracking technologies.

Limited operational logs may exist for abuse prevention and service reliability.

Hasher may use infrastructure providers for:

• Hosting
• Content delivery
• Push notifications

These providers do not receive message content.

Users may:

• Delete local app data
• Uninstall the app at any time
• Stop using the service without providing personal information

We may update this Privacy Policy as the service evolves.

Updates will be reflected on this page.

For privacy-related inquiries:

[email protected]