Hush Chat Logo
Back to Hush Chat

Privacy Policy

How we protect your data · Updated 2025-12-01

This Privacy Policy explains what information Hush Chat collects, how we use it, and the choices available to you. Our goal is simple: collect as little information as possible while providing secure, end-to-end encrypted communication.

What we store (minimal and transparent)

Hush Chat is built to run with extremely minimal data. We store only what is necessary to operate your account and subscription:

  • Account details you provide—such as your email address—so you can sign in, manage your subscription, and receive essential service communications.
  • Subscription & billing state: your plan, renewal dates, and payment status. Payment card details are processed securely by our payment provider and are never stored by Hush Chat.
  • Encrypted room data (ciphertext) when required for relay or for features you use. We cannot decrypt this data, and it is automatically purged according to strict retention rules.
  • Encrypted attachments or avatar assets you upload. These are stored only as encrypted blobs. All decryption happens locally on your device with keys we do not know.

What we never store or access (Zero Logs)

Hush Chat follows a strict zero-logs, zero-knowledge design. This means:

  • We do not store plaintext messages—ever.
  • We do not store, derive, or have access to your encryption keys.
  • We do not log IP addresses, device identifiers, room join/leave events, or participant identities.
  • We do not track what you do across rooms or sessions.
  • We do not use advertising IDs, analytics trackers, or cross-app profiling tools.

If you join a room via a shared link, your participation is completely anonymous.

Cookies and privacy-preserving analytics

We use only essential cookies—for example, to maintain your session when you sign in as an account operator. We do not use third-party tracking cookies.

When we analyze service usage, we do so in aggregate form only: things like total number of rooms created or overall feature usage. These analytics never identify individuals or tie activity to any account.

Data retention and deletion

Encrypted room data is kept only as long as needed for the room to function. When a room expires or is purged, we delete any stored ciphertext and related metadata. Because we cannot decrypt ciphertext, deleted room content is permanently unrecoverable.

Infrastructure logs, where required for debugging or security, are retained for the shortest operationally reasonable period and never include message content or user identities.

Your control & account deletion

If you use an operator account, you may:

  • Delete rooms or encrypted assets you control.
  • Update your email or account details.
  • Delete your entire account.

When you delete your account, we remove associated identifiers from our systems except for information we are legally required to retain—for example, billing or tax records.

Your rights (GDPR, CCPA, and similar laws)

Depending on your region, you may have rights such as accessing your personal data, correcting inaccuracies, requesting deletion, objecting to processing, or filing a complaint with a regulator.

Because Hush Chat stores minimal information and cannot decrypt message data, some rights apply only to the limited account data we maintain.

Service providers (infrastructure & payments)

Hush Chat uses reputable providers for hosting, storage, and payment processing. These providers only receive the data required to operate their part of the service and may not use it for marketing or resale.

No provider ever receives your plaintext messages or encryption keys.

Security model

Our privacy stance is tied directly to our security architecture: end-to-end encryption, per-room keys, and minimal metadata. For a deeper technical explanation, see our Security Overview.

Contact us

If you have questions or privacy requests, email support@hush.chat. If your request relates to privacy laws where you live, please mention that so we can route it appropriately.