Glossary
FINRA Compliance
Capture it, keep it, supervise it. For US broker-dealers every business communication, including chat, must be retained in tamper-resistant storage and reviewed under written supervisory procedures.
General definition
FINRA Compliance for communications is the set of obligations that the Financial Industry Regulatory Authority (FINRA) and the Securities and Exchange Commission (SEC) place on US broker-dealers to record, retain and supervise what their registered persons say to customers and to each other about the business. FINRA Rule 3110 requires a supervisory system with written procedures for reviewing incoming and outgoing correspondence and internal communications. FINRA Rule 4511 requires firms to make and preserve books and records in accordance with Securities Exchange Act Rule 17a-4, and sets a default retention of six years where no period is specified. FINRA Rule 2210 governs the content of communications with the public.
SEC Rule 17a-4 is the retention rule. Rule 17a-4(b)(4) requires originals of all communications relating to the business, sent or received, to be kept for at least three years, the first two in an easily accessible place. Rule 17a-4(f) sets the conditions for electronic storage: either non-rewriteable, non-erasable (WORM) media or, since the 2022 amendments, an audit-trail alternative that records every change. FINRA Regulatory Notice 17-18 confirmed that text messages and chat are communications subject to these rules whenever they are used for business.
The off-channel messaging cases made this concrete. Between 2021 and 2024 the SEC and the Commodity Futures Trading Commission charged dozens of firms whose employees discussed business in personal WhatsApp, iMessage and text threads that were never captured, with combined penalties exceeding two billion dollars. The lesson was not that chat is forbidden, but that any channel staff actually use must be one the firm can archive and review. A messaging platform used by a broker-dealer therefore needs:
- Capture: every message, edit, deletion, attachment and participant change recorded server-side, not only on the device
- Retention: a message archive that meets the 17a-4 timelines, with records exportable to a WORM or audit-trail store and to a designated third party
- Supervision: lexicon and pattern review, flagged-message queues and escalation, with evidence of who reviewed what
- Legal hold: the ability to suspend deletion for matters under investigation
In the Ethora ecosystem
Ethora is chat infrastructure a financial services app can build on, not a registered compliance archive, and it is designed so the firm keeps control of the record. Every message passes through the server, where a read-only archive database stores the conversation with configurable retention. The compliance audit trail can be exported as immutable logs to S3 in your own account, where your bucket retention and object lock settings supply the WORM or audit-trail layer that 17a-4(f) asks for. On a dedicated server or self-hosted deployment the whole stack, including the archive, runs in infrastructure the firm owns.
Supervision maps to the Trust and Safety system: stop words, regular expressions and AI auto-moderation can flag or quarantine messages that match your lexicon (guarantees, pressure selling, moving a conversation off-channel) and report them to your surveillance tooling by message bus, API or email. Ephemeral messages and end-to-end encrypted rooms, which defeat server-side archiving, are off by default and controlled by the app owner. Mapping these controls to your written supervisory procedures and your 17a-4 designated third party arrangement is work your compliance team and counsel own.