Comma Compliance Archiver

Comma Compliance Archiver is the on-device capture client for Comma Compliance, the regulated-communications archival platform used by broker-dealers, RIAs, insurance firms, and other organizations subject to SEC, FINRA, and FCA recordkeeping requirements. Comma Compliance Archiver is distributed privately and is intended for installation by an authorized administrator on fully managed, company-owned Android devices. End users do not subscribe or self-install outside of their organization's deployment program. Capture requires a fully managed (device-owner) Android Enterprise device. Once a device is enrolled, Comma Compliance Archiver captures SMS, MMS, and RCS messages sent and received on the device and forwards an encrypted copy to the organization's Comma Compliance tenant so the messages can be supervised, reviewed, and retained per the firm's policy. Coverage includes long multipart SMS, MMS media, and RCS 1:1 and group conversations with attachments and message edits. RCS is the gap in most archiving stacks; Comma covers it in the same capture as ordinary SMS and MMS. The archiver reads messages the phone's default messaging app has already stored. It does not intercept anything in transit. Designed for compliance, not surveillance: - Operates only on devices enrolled by an authorized organization. - Retains business messaging only; non-messaging activity is out of scope. - Messages are encrypted on the device before they leave it, sent over TLS, and held encrypted at rest in the tenant. - A persistent notification names the organization doing the archiving, so capture is visible to the person using the phone and is never hidden. - A plain-language rationale screen explains what is captured before any message access is requested. Two enrollment paths are supported: - Managed deployment via the organization's EMM or MDM. One reusable fleet token is delivered as managed configuration and each phone enrolls itself with no user interaction. Single-use per-device tokens are also available. - Self-serve OAuth enrollment, for organizations that allow the end user to authorize their own enrolled device. Sign-in runs in a Chrome Custom Tab, with no embedded WebView and no in-app password handling. Archiving is enabled by the organization, never by the individual. An administrator turns on message archiving for the team in the Comma Compliance tenant. An employee cannot enable it unilaterally, and cannot bind a device to a membership that is not their own. For administrators: full documentation, EMM deployment recipes, and the supervisor experience are at https://docs.commacompliance.com -Setup guide: https://docs.commacompliance.com/getting-started/rcs-android-setup -Platform coverage: https://commacompliance.com/platform-integrations -Consumer messaging archiving: https://commacompliance.com/consumer-messaging-compliance-archiving -Encrypted messaging compliance: https://commacompliance.com/encrypted-messaging-compliance -Comma Compliance: https://commacompliance.com -Privacy policy: https://commacompliance.com/privacy-policy Comma Compliance Archiver is published privately. Public install attempts will not provision a usable client. Android and Google Messages are trademarks of Google LLC. RCS is a standard of the GSMA. Comma Compliance is neither affiliated with nor endorsed by these companies.