securityEncryption, retention and who can read what
Who else can readour DMs?
Your messages are your company's. Here is exactly who can read them, where they live, how long we keep them, and what happens when something goes wrong.
Principles
- 01
Encrypted, always
TLS 1.3 in transit and AES-256 at rest on every plan, including Free. Keys rotate every 90 days.
- 02
Summaries stay yours
The catch-up and huddle notes only read what you can read. Nothing you write trains any model, ours or anyone's.
- 03
Your region, your keys
Choose EU (Frankfurt) or US (Virginia) data residency. Business can bring its own key and revoke it at any time.
- 04
Deleted means deleted
Deleted messages leave live systems within 24 hours and backups within 35 days. Retention rules apply to exports too.
Who can read this message?
Pick where it was posted. The answer is the same in the product, in exports and in the catch-up.
A message posted in
4 of 7 can open a message in #launch
- Channel membersPeople in the channel or conversationCan read
- Everyone in the workspaceMembers who are not in itCan read
- GuestsSingle- and multi-channel guestsCan't
- The other companyPeople on the far side of a shared channelCan't
- Workspace adminsThrough exports, on Business onlyCan read
- Your catch-upOnly for people who can already read itCan read
- Hum staffOnly with your written support requestCan't
The specifics, in one table.
- Encryption in transit
- TLS 1.3, HSTS preloaded
- Encryption at rest
- AES-256, keys in a managed HSM
- Data regions
- EU (Frankfurt) or US (Virginia)
- Customer-managed keys
- Business, revoke any time
- Backups
- Every 6 hours, kept 35 days, restore tested quarterly
- Single sign-on
- SAML 2.0 and SCIM on Business
- Audit log
- 30 days on Pro, 1 year on Business
- Penetration tests
- Twice a year, by an outside firm
Audits and agreements
SOC 2 Type II
Audited yearly. Report under NDA.
ISO 27001
Certified since 2025.
GDPR
DPA signed online in two minutes.
HIPAA
BAA available on Business.
Up, and honest about it.
Every incident gets a public write-up within five business days, including the boring ones.
All systems normal
Checked every 30 s · Nov 20, 2026
Messaging
99.99% over 90 days
Huddles
99.97% over 90 days
Catch-up
99.98% over 90 days
Search
99.99% over 90 days
Notifications
99.96% over 90 days
Integrations and API
99.98% over 90 days
Last incident, Oct 14, 2026: Delayed notifications on some Android 15 phones. Between 06:10 and 07:25 UTC, some Android users received notifications up to 12 minutes late. Messages were never lost. Fixed in 4.10.3.
Asked by security teams.
Found something? Tell us first.
We answer every report within one business day and pay bounties from $200 to $10,000. Please give us 90 days before going public, and don't access data that isn't yours.
Report a vulnerabilityNo. Production data is reachable only through a break-glass process that needs your written support request, a second engineer's approval, and is logged in your audit log.
Need the paperwork?
SOC 2 report, DPA, pen-test summary and a filled-in security questionnaire. Business customers get them in a day.