Business conversations that happen on personal WhatsApp, Signal or SMS are invisible to the organisation, and regulated firms have paid billions of dollars for failing to keep them. In financial services the issue has been driven by enforcement: US regulators fined large banks and brokers for staff using unapproved messaging apps on personal phones, and UK rules require firms to stop staff using devices the firm cannot record. Outside finance, the same gap breaks eDiscovery, incident investigation and insider risk monitoring. This guide explains the record-keeping requirements that drive the problem, the technical options for capturing messages, how to design a policy people will follow, and how to measure compliance. It is for security, compliance and records teams. For hardening the messaging apps themselves, see the Securing Messaging Apps Guide. This guide summarises regulatory requirements and is not legal advice.
Status checked 27 October 2026 against the regulators' own pages cited below. Enforcement priorities can change; confirm current requirements with counsel.
Key takeaways
- The obligation follows the content, not the app. FINRA states that business-related communications must be retained whether sent through the firm's platform or a third party's, and that a firm may not permit a type of electronic communication it cannot retain.
- Enforcement has been large and repeated. The SEC fined 16 firms over $1.1 billion and the CFTC 11 firms over $710 million on 27 September 2022, and the SEC was still announcing off-channel settlements in January 2025.
- UK firms must prevent unrecordable devices. FCA SYSC 10A.1.7R requires reasonable steps to stop relevant calls and messages on private equipment the firm cannot record or copy.
- Approved channels must be easier than unapproved ones. Bans without a captured alternative push staff back to personal apps; provide a captured channel for every client-facing need.
- Retention is a records system problem. Captured messages need tamper-evident storage, defined retention periods, legal holds and tested retrieval, not just a backup.
What "off-channel" means and why it matters
Off-channel communications are business messages sent through channels the organisation has not approved and cannot capture: personal text messages, consumer WhatsApp or Signal, personal email, direct messages on social platforms. The SEC's September 2022 release described employees who "routinely communicated about business matters using text messaging applications on their personal devices" from January 2018 through September 2021, with most messages never kept. The CFTC's parallel action named personal text messages, WhatsApp and Signal, used by staff including senior and supervisory employees, in breach of the firms' own policies.
The risk is not limited to regulated finance:
- Legal and eDiscovery: messages that exist but cannot be collected create disclosure and preservation problems. See the eDiscovery and Legal Hold Guide.
- Security investigations: social engineering, fraud and data exfiltration that happen over personal apps leave no trace in corporate logs.
- Insider risk: moving deal or customer data to a personal messaging account is a common exfiltration path. See the Insider Data Theft Guide.
- Data protection: personal data in uncontrolled apps cannot be found for access requests or deleted on schedule.
Record-keeping requirements that drive the issue
| Regime | Requirement (as stated by the regulator) | Retention |
|---|---|---|
| SEC Rule 17a-4(b)(4) (US broker-dealers), as explained by FINRA | Keep originals of communications received and copies of communications sent relating to the business as such, including email, instant messages and business-related social media, internal or external, on the firm's or a third party's platform | At least three years, the first two in an easily accessible place |
| SEC Rule 17a-4 electronic recordkeeping systems | Preserve records either with a complete time-stamped audit trail of modifications and deletions, or exclusively in non-rewriteable, non-erasable (WORM) format; verify completeness, support download in usable formats, keep a backup | Full retention period of the record |
| FINRA Rule 4511 | Make and preserve required books and records in a format that complies with Rule 17a-4 | Six years where no other period is specified |
| FINRA Rule 3110 | Supervisory systems and written procedures reasonably designed to meet record-keeping obligations, reviewed and tested (Rule 3120) | Not applicable |
| CFTC recordkeeping and supervision (US swap dealers and FCMs) | Maintain, preserve and produce required records, including business communications, and diligently supervise | As set in CFTC rules; check the applicable rule |
| FCA SYSC 10A (UK MiFID investment firms, full-scope UK AIFMs and others in scope) | Take all reasonable steps to record relevant telephone conversations and keep copies of electronic communications on firm-provided or approved equipment (10A.1.6R); stop relevant communications on private devices the firm cannot record (10A.1.7R); written policy, training, register of approved devices, periodic reviews (10A.1.15R) | Five years, extendable to seven if the FCA requests (10A.1.14R) |
Two enforcement details are worth knowing. The 2022 SEC settlements required firms to retain compliance consultants to review their policies for electronic communications on personal devices and how they handle employee non-compliance. In the January 2025 release (12 entities, $63.1 million combined), the SEC noted that one self-reporting firm received a significantly reduced penalty. Firms outside these regimes should check their own sector's rules; this table is not exhaustive.
Capture options compared
There are four broad ways to bring mobile and chat messages into a records system. Most organisations combine two or more.
| Approach | How it works | Strengths | Weaknesses |
|---|---|---|---|
| Corporate platform only (Teams, Slack, corporate email) | Business messaging happens on enterprise tools with native retention | Simple, native retention and eDiscovery, no extra vendor | Clients and counterparties often insist on WhatsApp or SMS; staff drift back to personal apps |
| Corporate number with carrier or app-level capture | A firm-issued number or business messaging app routes SMS and voice through a capture service | Covers client SMS; works on managed or BYOD phones with a separate number | Only covers the captured number; personal number remains unmonitored |
| Captured consumer-app variants | A modified or business edition of a consumer app archives messages to the firm | Meets clients where they are | Depends on a third party's app and its terms; must verify completeness and edits/deletions are captured |
| Managed device with work profile | Business apps run in a managed work container on a corporate or BYOD phone; personal apps stay outside | Clear separation of personal and business data; supports remote wipe of work data | Does not capture personal apps; separation only works if policy forbids business use outside the container |
Whichever approach is used, verify that captured records include edits and deletions, attachments and voice notes where relevant, and participants' identities. The SEC's audit-trail alternative to WORM means the archive must show who changed or deleted a record and when.
Native platform retention is not automatic. In Microsoft 365, for example, Teams messages are covered only by retention policies scoped to the Teams chats and Teams channel messages locations, not by Exchange mailbox policies. Microsoft also documents that messages from users in another Microsoft 365 organisation are stored in that tenant, so your policies cannot delete them there, and that guest messages held in shadow mailboxes are not supported by retention policies. Check equivalent behaviour for whatever platform you use. See the Data Retention and Secure Deletion Guide.
Designing the policy
A policy that only says "do not use WhatsApp" fails. Effective policies have these parts:
- Scope: which roles are covered (all staff, or registered and client-facing staff), and what counts as a business communication. Under FCA SYSC 10A.1.8R this includes communications intended to lead to a transaction even if none follows.
- Approved channels list: a short register of approved channels and devices for each use (internal chat, client chat, client SMS, voice). SYSC 10A.1.15R expects a register of approved devices.
- Prohibition and redirection: business communications on unapproved channels are forbidden; if a client contacts a member of staff on an unapproved channel, the staff member must move the conversation to an approved channel and capture what was received (for example by forwarding it into the archive), following a written procedure.
- Attestation: periodic attestation that staff have complied, as a supervisory record.
- Consequences: consistent, documented discipline. The SEC undertakings specifically examined how firms addressed non-compliance.
- Privacy notice: staff and, where required, clients are told communications are recorded. SYSC 10A.1.11R requires client notification before services begin.
Templates that help: the BYOD Policy Template, the Acceptable Use Policy Template and the Data Retention and Disposal Policy Template.
Large regulated firms: need capture for every approved channel, surveillance (lexicon and behavioural review) over captured content, and supervisory testing under rules such as FINRA 3120. Smaller or unregulated organisations: can usually standardise on the corporate chat platform, set retention policies, forbid business use of personal apps, and focus on eDiscovery readiness.
Implementation: a phased rollout
- Inventory channels in use. Survey staff confidentially and review client contact patterns to learn which apps are actually used for business, and by whom. The point is to find demand, not to punish.
- Map obligations. With legal and compliance, record which regimes apply, to which roles, and the retention periods (for example three years for 17a-4(b)(4) communications, five to seven under SYSC 10A).
- Pick and pilot capture. Select approaches for each need (client SMS, client chat, internal chat, voice). Pilot with one desk, verify capture of edits, deletions and attachments end to end, and test retrieval as if for a regulator request.
- Configure retention and holds. Set retention policies on every approved channel, confirm WORM or audit-trail storage where required, and confirm legal holds suspend deletion.
- Roll out by risk. Client-facing and senior staff first; the 2022 actions involved supervisors and senior managers as well as junior staff.
- Train and attest. Short, role-specific training on approved channels and the redirection procedure; quarterly or annual attestation.
- Test and review. Sample captured records against expected activity, review exceptions, and report to the management body. Rollback here means keeping the previous channel available until the new capture is proven.
Where identity fits
Captured channels depend on knowing who sent a message. Tie every approved messaging account to a managed corporate identity with MFA, remove access at leaver time (a leaver's personal WhatsApp history with clients cannot be revoked; a corporate account can), and keep the device register linked to the user directory. Shared desk accounts and bot or integration accounts that post into chat need named owners so their messages can be attributed. See the Mobile Device Management Security Guide.
Detection and measurement
- Capture coverage: percentage of in-scope staff with every approved channel captured and verified in the last test.
- Volume anomalies: client-facing staff whose captured message volume is far below peers, which can indicate business moving off channel.
- Off-channel indicators in captured content: surveillance hits for phrases such as "text me", "WhatsApp me" or "call my cell" in email and chat.
- Attestation completion: percentage of staff attesting on time, and number of self-reported exceptions.
- Retrieval time: time to produce all communications for a named person and date range, measured in a test.
- Exception handling: number of off-channel incidents found, and time to close with documented action.
Responding when off-channel use is found
Discovery usually comes from a surveillance hit, a client complaint, a litigation request or a self-report. Handle it as a records incident with a defined procedure rather than an ad hoc HR matter.
- Preserve first: instruct the individual not to delete anything, and where a legal hold applies, extend it to the personal device content in scope. Deleting messages after discovery turns a record-keeping lapse into a spoliation problem.
- Collect the business content: agree with legal how business messages will be exported from the device or app, with a chain of custody record, while respecting the privacy of personal content.
- Assess scope: which clients, counterparties and colleagues were involved, over what period, and whether others on the thread also used unapproved channels.
- Decide on reporting: legal and compliance decide whether a regulator notification or self-report is appropriate. The SEC's January 2025 release shows self-reporting was treated favourably in at least one case.
- Fix the cause: if the person used a personal app because no approved channel met the need, that is a programme gap to close, not only a conduct issue.
- Record the outcome: keep the decision, the discipline applied and the remediation as supervisory evidence.
| Finding | Typical response | Owner |
|---|---|---|
| Isolated client message received on a personal app, forwarded promptly | Confirm capture, no further action beyond logging | Line supervisor |
| Repeated business use of a personal app by one person | Preserve and collect, conduct review, retraining, documented discipline | Compliance with HR |
| Team-wide or senior use of an unapproved channel | Formal investigation, legal assessment of reporting, programme remediation | Compliance, legal, senior management |
| Off-channel use linked to fraud or data theft | Security incident response in addition to the records process | Security incident lead |
Common failure patterns
- Policy without a tool: banning personal apps while offering no captured way to reach clients who use them. Staff comply in training and ignore it in practice.
- Senior exemptions: managers who expect to use personal phones. Regulators specifically noted supervisors and senior staff among the users.
- Capture that misses edits and deletions: an archive that stores only the latest version cannot meet an audit-trail requirement.
- Retention policies on the wrong location: assuming email retention covers chat, or forgetting new channel types, as the Microsoft Teams example shows.
- Never testing retrieval: discovering during a regulator or court request that exports are incomplete or unreadable.
- Treating it as a one-off project: new apps, new roles and new client preferences appear; the register and tests need a review cycle.
Framework mapping
| Framework | Reference | How it applies |
|---|---|---|
| NIST SP 800-53 Rev 5 | SI-12 Information Management and Retention | Retaining business messages per legal requirements |
| NIST SP 800-53 Rev 5 | AC-19 Access Control for Mobile Devices; PL-4 Rules of Behavior | Approved devices and staff rules for channels |
| NIST SP 800-53 Rev 5 | AU-9 Protection of Audit Information; AU-11 Audit Record Retention | Tamper-evident storage and audit trails for archives |
| NIST CSF 2.0 | GV.OC-03; GV.PO-01; PR.DS-01 | Legal requirements understood, policy established, stored records protected |
| ISO/IEC 27001:2022 Annex A | 5.33 Protection of records; 5.14 Information transfer | Records protection and rules for transferring information |
Practitioner checklist
- List the record-keeping regimes that apply to each role, with retention periods.
- Publish a register of approved channels and devices for each communication need.
- Provide a captured channel for client SMS and chat if clients use them.
- Verify capture of edits, deletions, attachments and identities end to end.
- Apply retention policies to every chat location, not just email, and confirm legal holds work.
- Write and train a redirection procedure for messages received on unapproved channels.
- Run periodic attestations and surveillance for off-channel indicators.
- Test retrieval for a named person and date range at least annually.
- Report coverage, exceptions and actions to senior management.
Standards and references
- US SEC: Press release 2022-174, SEC charges 16 Wall Street firms with widespread recordkeeping failures
- US SEC: Press release 2025-6, twelve firms charged with recordkeeping failures
- US CFTC: Press release 8599-22, recordkeeping and supervision failures
- FINRA: Books and Records key topic
- UK FCA Handbook: SYSC 10A.1 Recording telephone conversations and electronic communications
- Microsoft Learn: Learn about retention for Microsoft Teams
- NIST: SP 800-53 Rev. 5 Security and Privacy Controls
Related NHI Mgmt Group resources: Securing Messaging Apps Guide · eDiscovery and Legal Hold Guide · BYOD Policy Template · Insider Threat Programme Guide. This guide summarises regulatory record-keeping requirements and is not legal advice.