Glossary

Records Retention

The schedule that says which business records exist, how long each must be kept and when it may be destroyed. Chat messages became records the moment regulators started fining firms for losing them.

General definition

Records Retention is the management of an organisation’s official records across their lifecycle: creation, active use, storage, and finally destruction or permanent archive. It is older than information security and comes from records management, where a retention schedule lists each record series (contracts, invoices, patient charts, board minutes, regulated communications) with the period the law or the business requires. The schedule is the authority for what gets kept; a wider data retention policy covers everything else.

The periods that come up most often in software and messaging contexts:

  • HIPAA: documentation of policies, procedures and required records for six years from creation or last effective date (45 CFR 164.316); retention of the medical record itself is set by state law
  • SEC Rule 17a-4 and FINRA Rule 4511: broker-dealer records for three to six years depending on type, with business communications kept three years and the first two in an easily accessible place; FINRA defaults to six years where no period is specified
  • GDPR: no minimum, but Article 5(1)(e) storage limitation and Article 17 erasure cap how long personal data in a record may be kept once the legal purpose ends
  • Public records laws: messages sent by officials on government business are public records under FOIA and state equivalents, including texts and chat, and must be retained and producible

Messages are now records. Since 2021 the SEC and CFTC have levied well over a billion dollars in penalties on banks and brokers whose staff conducted business over personal messaging apps that were not captured, the so-called off-channel communications cases. The lesson travelled beyond finance: if a conversation decides something, approves something or advises a customer, it belongs in the record and the system that carries it must preserve it, prove it was not altered, and produce it on demand for eDiscovery or a regulator.

That last requirement shapes the storage. Regulated records are often kept on WORM storage that cannot be rewritten during the retention period, or, since the SEC’s 2022 amendments to Rule 17a-4, in a system with a complete audit trail of any change. Either way the record needs an index, a legal hold mechanism that suspends disposal, and a disposal log that shows what was destroyed, when and under which schedule entry.

In the Ethora ecosystem

Ethora treats chat as a record from the start. Messages are written to a read-only server-side archive with retention configured per deployment, so a finance or healthcare operator can hold conversations for the period its regulator sets. The compliance audit trail is exported as immutable logs to S3 in the customer’s account, where Object Lock provides the WORM behaviour records rules expect, and app export produces the data for review or production. The Trust and Safety layer supervises content in flight, which is the other half of what communications rules ask for.

The retention schedule itself is yours. Ethora provides the archive, the retention controls, per-user erasure for the records that privacy law says must go, and the audit trail; your compliance team maps those to the record series and periods in its schedule. On dedicated and self-hosted deployments the archive and the exports live in your own account, so the records never depend on a vendor outliving your retention period.

Get started

Chat and AI built for regulated industries

Ethora gives you audit trails, retention controls, a Trust & Safety layer and dedicated deployments in your own cloud. Talk to our team.

Start Free
Free tier available Enterprise SLA No vendor lock-in