How Haily Keeps You Secure
What you say to Haily is yours. Haily is built so that no one running it, its own people included, can read your conversations, and so that an organization decides exactly what Haily may do for each of its people.
This page explains how, from signing in to the keys that seal every conversation, and how Haily is getting ready for quantum computers, which will one day break much of the cryptography the internet relies on today.
- You sign in with Google. No passwords to steal, one person, one identity.
- The connection is encrypted. Every Haily app is reached over HTTPS only.
- Each app keeps to itself. An app sees only its own part of your information, never another app's.
- Conversations are sealed. Encrypted the moment they're kept, readable only by your session.
- The keys are kept apart. In a separate vault, lent to the app in memory only, never stored beside what they seal.
Your Organization Decides
Haily Admin is where an organization's Admins manage Haily for their people. Every choice there is theirs, and applies the moment it's made.
- Security groups: Admins gather their people into groups (a finance team, investors) and choose which Haily Capabilities each group may use. Someone in groups gets what one of their groups allows.
- Everyone, by default: every organization starts with one group, Everyone, holding the capabilities it has today, for anyone not placed in another group. Nothing changes until an Admin chooses.
- New capabilities, your call: each group has a setting for whether it takes each new Haily Capability as it arrives, or keeps what it has until an Admin turns the new one on.
- One person at a time, too: an Admin can turn a capability off for one person, whatever their groups allow.
- Counts, never people: Haily's own Super Admin sees each organization by name and counts alone, never its people, their questions or their files.
What's Locked, and How
- Signing in: Google Sign-In only, so Haily never holds a password. Sessions live in secure, HttpOnly cookies, and Haily keeps only a hash of each.
- Conversations at rest: sealed with AES-256-GCM, each app and interface with keys of its own. Each message is bound to its interface, its field and its owner, so a sealed value moved anywhere else won't open.
- The keys: kept in Google Secret Manager and loaded into the app's memory when it starts, never written to disk. Keys rotate: a new key seals, and older ones only open.
- Between apps: an app never learns of another. It asks Haily only about itself, and shows only its own part of your account.
- Deleting: yours to do, at any time, from your Account view, without asking anyone.
Ready for Quantum Computers
Large quantum computers, when they arrive, will break the public-key cryptography that protects most of the internet today. Someone could record encrypted traffic now and decrypt it later. The US National Institute of Standards and Technology finished its first post-quantum standards in 2024: ML-KEM for exchanging keys (FIPS 203) and ML-DSA for signatures (FIPS 204).
Haily's own encryption is symmetric, which quantum computers weaken but don't break: a 256-bit key keeps 128 bits of strength against them, far out of reach. The rest depends on the connections Haily makes and the companies it builds on, and here is exactly where each stands.
Questions About Security
Haily's security will keep changing as the standards do, and this page will say so as it does. For how Haily handles your information, read the Haily Privacy Policy. For anything else, write to chris@moba11y.com.
Last updated November 15, 2026.