Your team runs on Google Workspace. Your clients text on iMessage.
Two different worlds. One compliance obligation.
Google Vault does its job well, but only inside the Google ecosystem. The real exposure is outside it: clients text brokers on iMessage and WhatsApp because that’s what’s already on their phone. You can’t force them to switch, and trying to just pushes conversations off the record entirely.
FINRA requires oversight of every channel your representatives use, not just the convenient ones. Comma captures Google Workspace alongside WhatsApp, Signal, iMessage, and 40+ other channels. One archive, one search interface, one export for examiners.
Set up your Google Workspace →
What this means for your team
For your compliance team
Gmail captured at delivery
Every email is written to the Comma archive the moment it is received — including blind copies most archiving solutions miss. Inbound, outbound, CC, BCC, and attachments in full. Continuous capture, not a scheduled sync.
Comma controls the archive
Records are written to WORM storage Comma controls, outside your Google environment. Your own admins cannot modify retention, alter classifications, or shorten holds on the archived copy.
Regulator-ready storage
Designed against SEC, FINRA, and broader recordkeeping requirements, with a complete audit trail of every record.
For your IT team
You control the connection
Comma connects through a single admin-consent authorization granted from your Google Admin console. You can revoke access at any time from the same console. No support ticket, no waiting on Comma. Existing archived records are unaffected by revocation.
Least-privilege scopes, fully documented
Comma requests only the API scopes required for the access tier you choose. Every scope is documented: what it does, why it's needed, and what Comma never requests. Your security team can review the full list before you go live.
For your employees
Nothing installs on their device
Comma operates at the Google Workspace level, not on employee phones or laptops. No app to install, no MDM profile, no battery drain.
Personal conversations stay private
Employees can designate personal contacts as private according to your firm's communication policy. Approved personal conversations are excluded while business communications remain archived.
No change to how they work
Employees keep using Gmail, Drive, and Chat exactly as they do today. No notifications, no new logins, no disruption to their day-to-day workflow.
Google Workspace Meets Every Other Channel — In One Archive
The whole Google Workspace stack, captured in one connection
- Gmail — every inbound, outbound, CC, BCC, and attachment
- Google Drive — files, version history, sharing permissions, external shares
- Google Chat — 1:1 messages, spaces, and shared files
- Google Meet — meeting recordings, participant lists, duration, and recording links
Set up once, managed centrally
- A single Google Workspace admin authorizes Comma once for the entire domain
- Refresh tokens are stored securely and can be revoked from the Google Admin console at any time
Immutable by design
- Records are written to WORM storage that Comma controls, independent of your Google environment
- No dependency on Google Cloud Storage Bucket Lock — immutability is built into Comma's archive, not bolted onto Google's
Ready to see how Comma handles your entire comms stack?
File Archiving
Google Drive
Every file your team creates, shares, or stores in Drive is preserved in full, not just the latest version.
What Comma archives:
- Files and folders across My Drive and shared drives
- Version history — every edit, not just the final copy
- Sharing permissions and external share events
- Custodian attribution — who created it, who modified it
Shared drives are captured at the organization level, not per user. If a file lives in a shared drive, it’s in the archive regardless of which team member last touched it.
Meet Recording
Google Meet
Meet recordings flow through the same admin-consent connection as Gmail and Drive. No separate setup.
What Comma archives for every recorded meeting:
- Full recording file
- Participant list and session duration
- Recording link
Scheduled and instant meetings, both included. Google Meet lets users start meetings on the fly, not just from calendar invites. Comma captures both, as long as your Google Workspace plan includes recording.
Recurring meetings. Recurring meetings share one Meet link, but Google generates a separate recording for each occurrence. Comma captures each session as its own record, so a weekly standup builds a sequential archive over time.
One platform boundary worth noting. Google Meet only allows the host to record. If your team joins a meeting hosted by an external organization, that recording belongs to the host (worth noting in your supervisory procedures). For every meeting your team hosts, scheduled or on the fly, Comma captures the full record.
FAQ about Google Workspace Compliance Archiving
Does Comma replace Google Vault? Can we keep Vault and use Comma?
Does Comma archive our Gmail?
What Google permissions does Comma request?
What Google Workspace edition do we need?
Are Google Drive files and Meet recordings included?
How quickly can we produce records for an SEC or FINRA exam?
Can we revoke Comma's access?
What happens to our records if we stop using Comma?
Archive all of Google Workspace — not just Gmail.
Comma unifies Google Workspace alongside WhatsApp, iMessage, Signal, and 40+ other channels in one archive. Multi-entity setup and dedicated implementation available for large Google deployments.
Related reading