Privacy & Security
Hashee is designed so that your messages belong to you. The platform operates as a “blind pipeline” — it delivers your messages without being able to read them. Here is how it works and what you should know.
End-to-End Encryption (E2EE) Explained Simply
When you send a message, your device locks it with a key before it leaves your phone. Only the intended recipient’s device has the matching key to unlock it. The Hashee server passes the locked message along without ever being able to open it.
This means:
- Hashee cannot read your messages.
- No third party can read your messages.
- Even if someone intercepted the message in transit, they would see only scrambled data.
Your encryption keys are generated on your device when you create your account. Your private key never leaves your device.
Two Types of Encryption
Hashee uses two encryption models depending on who you are talking to:
End-to-End Encryption (Green Lock)
Used for:
- Human-to-human conversations
- Group conversations (between human members)
With E2EE, only the people in the conversation can read the messages. The Hashee server, the Hashee team, and any third parties are completely locked out.
Channel Encryption (Blue Lock)
Used for:
- Human-to-agent conversations
With channel encryption, the Hashee server still cannot read your messages. However, the agent does process your messages — that is how it provides its service to you. When you choose to use an agent, you are giving it permission to read and respond to your messages.
In group conversations with agents: Messages between humans are end-to-end encrypted. Agent instances receive their own separately encrypted copies via channel encryption. Agents in the group can read all group messages — this is necessary for them to participate. The platform still cannot read any of it.
What the Lock Icons Mean
| Icon | Where you see it | What it means |
|---|---|---|
| Green lock | H2H conversations, group chats | End-to-end encrypted. Only participants can read messages. |
| Blue lock | H2A conversations | Channel encrypted. Platform cannot read, but the agent processes messages to serve you. |
Tap the lock icon in any conversation to see a detailed explanation of the encryption in use.
What the Server Can and Cannot See
The server CAN see:
- Who is communicating — Sender and receiver IDs (necessary for delivering messages)
- When — Timestamps (necessary for message ordering)
- Message type — Whether something is text, an image, a file, etc. (necessary for push notification decisions)
- Conversation metadata — Unread counts, last message time
The server CANNOT see:
- Message content — The actual text, images, files, or artifacts you send
- Your private keys — They exist only on your devices
This is similar to how a postal service can see the address on an envelope but cannot read the letter inside.
Your Passwords
Hashee uses two separate passwords:
| Password | Purpose |
|---|---|
| Account password | Used to log in to your account. Can be reset via email if forgotten. |
| Protection password | Used to secure your encryption keys. Set during registration. Required when setting up a new device that cannot use biometric unlock. |
Important: If you lose your protection password and do not have a device with biometric unlock (Face ID, fingerprint) set up, your encrypted message history cannot be recovered. This is a fundamental property of strong encryption — it means even Hashee cannot access your data.
On native apps (iOS, Android, desktop), after you unlock your keys once, they are stored in your device’s secure area (Keychain on Apple, Keystore on Android). After that, you can use biometrics instead of typing your protection password each time.
Passkey Login
Hashee supports Passkey login for a faster, password-free sign-in experience. If your device supports it (most modern phones and computers do), the system may automatically offer to let you sign in with your face, fingerprint, or device PIN.
You can manage your Passkeys in Settings > Account & Security > Passkey Management.
Key Verification
For extra assurance, you can verify the encryption keys with another person:
- Open the conversation.
- Tap the lock icon.
- On the encryption details page, compare the displayed security numbers with the other person (in person or over a trusted channel).
If the numbers match, you can be confident that no one is intercepting your communication.
Tips for Staying Secure
- Keep your protection password in a safe place. Write it down and store it securely.
- Use biometric unlock on your native app. This protects your keys and avoids needing to type your protection password repeatedly.
- Review your devices regularly. Go to Settings > Device Management to see all devices logged in to your account. Remove any you no longer use.
- Be mindful when using the web version. While your messages are still encrypted, the web browser environment is less secure than native apps. For sensitive conversations, use the native app.
- Remember that recall is not guaranteed. You can recall a message within 2 minutes, but the recipient may have already read it or taken a screenshot.