What does secure messaging mean?

Secure messaging means a chat system that encrypts messages in transit and at rest, verifies who is talking, limits who can see each conversation, records activity in an audit trail and keeps or deletes messages according to policy. It is a combination of controls rather than one feature, and the exact mix depends on the regulations the organisation is subject to.

Is secure messaging the same as end-to-end encryption?

No. End-to-end encryption is one way to secure content, in which only the participants' devices can decrypt messages. Many secure messaging systems for regulated industries instead encrypt in transit and at rest while allowing an authorised server to archive, audit and moderate content, because record-keeping rules require it. Both can be secure; they defend against different threats.

What is secure messaging in healthcare?

In healthcare, secure messaging refers to communication between clinicians, staff and patients that protects protected health information as the HIPAA Security Rule requires: encryption, access controls, audit logs, integrity checks and a Business Associate Agreement with the vendor. Consumer SMS and most personal messengers do not meet this bar, which is why hospitals use dedicated platforms or in-app chat.

Does HIPAA require end-to-end encryption for messaging?

No. HIPAA requires that electronic protected health information be protected with access controls, audit controls, integrity controls and transmission security, and encryption is an addressable safeguard that covered entities are expected to implement where reasonable. It does not specify end-to-end encryption, and many compliant platforms use server-side encryption so that records can be retained and audited.

Is Ethora a secure messaging platform?

Ethora provides TLS in transit, encryption at rest, on-device encryption in the React Native SDK, token-based authentication, room and role permissions, a compliance audit trail and configurable retention with per-user erasure. It uses a compliance-archive design rather than end-to-end encryption so regulated customers can retain and moderate conversations, and it can run entirely inside your own cloud account.

Glossary

Secure Messaging

Messaging that regulated organisations can trust: encrypted in transit and at rest, gated by access controls, recorded in an audit trail and kept for exactly as long as policy says. The phrase hides a real design choice about who holds the keys.

General definition

Secure Messaging is the buyer’s term for chat that meets the security and compliance obligations of healthcare, finance, government and other regulated sectors. It is not a single technology. A messaging system is secure when several layers work together, and a vendor claiming the label should be able to say which of these it provides:

Encryption in transit: TLS between every client and server, and between servers, so messages cannot be read on the network
Encryption at rest: message stores, attachments, backups and device caches encrypted on disk
Authentication and access control: verified identities, short-lived session tokens, single sign-on where needed, and room or role permissions that limit who sees what
Audit trail: a tamper-evident record of who sent, read, exported or deleted what, available to compliance teams
Retention and erasure controls: keeping messages as long as regulation requires and deleting them when it does not
Data loss prevention: detecting and handling sensitive data shared in the wrong place

The layer that causes most confusion is end-to-end encryption (E2EE). In an E2EE system only the participants’ devices hold the keys, so the server cannot read the content. That is the strongest confidentiality guarantee against the operator, and it is the right design for consumer messengers. It also means the operator cannot archive, search, supervise or moderate the content, which conflicts with the record-keeping duties of regulated firms. The HIPAA Security Rule (45 CFR 164.312) asks for access control, audit controls, integrity and transmission security; it does not require E2EE.

So there are two honest models of secure messaging. The E2EE model protects content from everyone including the provider, at the cost of server-side compliance functions. The compliance-archive model encrypts in transit and at rest but lets an authorised server archive, audit and moderate. Which one is secure depends on the threat model: a journalist protecting a source needs the first; a hospital or a broker-dealer that must retain and supervise communications usually needs the second.

In the Ethora ecosystem

Ethora deliberately implements the compliance-archive model. Traffic is protected with TLS in transit, data is encrypted at rest, the React Native SDK keeps its local message cache encrypted on the device with AES-256 and credentials in the Keychain or Keystore, and access is controlled through short-lived JWT chat tokens, App-level API tokens, room membership and admin panel roles. The server keeps a read-only message archive with configurable retention and per-user erasure, and every relevant action lands in a compliance audit trail with immutable log export.

Ethora does not offer client-side end-to-end encryption, and says so plainly, because its customers in healthcare, finance and insurance need to retain, supervise and moderate conversations. What removes the operator from the trust equation instead is deployment: on a dedicated or self-hosted server the whole stack, keys included, runs inside your own cloud account or data centre, and Ethora signs a DPA and, for US healthcare, a BAA on Enterprise and dedicated plans.

Secure Messaging

General definition

In the Ethora ecosystem

Ship chat features, not chat infrastructure

Talk to our team

Pick a time that works for you