Comma Compliance

Productivity suite

Gmail, Drive, Chat, and Meet. One compliant archive.

Without depending on Google Vault.

Comma captures your entire Google Workspace into an external tamper-proof WORM archive the moment it's created. That archive lives outside your Google environment. WhatsApp, Signal, iMessage, and 40+ other channels land in the same place.

One OAuth admin-consent connection. No per-user enrollment. Every Google Workspace message, file, and record written to an immutable archive.

Get in Touch

Your team runs on Google Workspace. Your clients text on iMessage.

Two different worlds. One compliance obligation.

What Comma does for Google Workspace:

  • Single admin-consent OAuth connection — no per-user setup
  • Captures Gmail, Chat, Drive, and Meet
  • Written to an external WORM archive from day one
  • Stored outside your Google tenant — can’t be touched or altered

Set up your Google Workspace →

The real exposure isn’t inside Google Workspace — it’s outside it:

  • Clients text brokers on iMessage and WhatsApp because that’s what’s already on their phone
  • You can’t force clients to switch to Google Chat to make recordkeeping cleaner
  • Trying to force the switch just pushes conversations off the record entirely
  • Google Vault does its job well — but only inside the Google ecosystem
  • Exam exposure lives outside that ecosystem

FINRA Rule 3110 requires supervisory procedures to cover every channel your team actually uses:

  • Comma captures Google Workspace alongside WhatsApp, Signal, iMessage, and 40+ other channels
  • One archive, one search interface for compliance, one export for examiners
  • No juggling two systems when you’re under a deadline
Comma Compliance archive showing Gmail, WhatsApp, and iMessage messages from multiple contacts in a single unified list with platform icons, business contact badges, and message previews.

Gmail, WhatsApp, and iMessage — one archive, one review queue.

How Comma Captures Google Workspace — and the Apps Beyond

  1. The whole Google Workspace stack, captured in one connection

    • Gmail — every inbound, outbound, CC, BCC, and attachment
    • Google Chat — 1:1 messages, spaces, and shared files
    • Google Drive — files, version history, sharing permissions, external shares
    • Google Meet — meeting recordings, participant lists, duration, and recording links

  2. 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

  3. 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

  4. One archive for every channel — including Bloomberg Chat

    • Google Workspace sits in the same archive as WhatsApp, Signal, iMessage, Bloomberg Chat, and 40+ other channels
    • When employees text clients on personal devices, those messages land next to their Gmail — same review queue, same export
Comma Compliance Files archive showing four Google Drive shared drives with file counts, folder counts, total sizes, and backfill complete status.

Google Drive shared drives as they appear in the Comma Files archive — versioned and custodian-attributed.

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

    Meets SEC, FINRA, and broader regulatory recordkeeping requirements, with a complete audit trail of every record.

  • Cross-channel exam readiness

    Examiners rarely ask only about email. With Comma, Google Workspace records and mobile messaging records are searchable, exportable, and exam-ready from the same interface.

For your IT team

  • One admin-consent flow

    Domain-wide authorization through Google OAuth. No per-user enrollment, no MDM dependency, no client-side agents to deploy.

  • Least-privilege scopes

    Comma requests only the Google API scopes needed for the access tier you choose: directory read, contact discovery, or full mail capture. See the documented permission tiers for every scope and why it is needed.

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 toggle any contact as private — those conversations are excluded from capture entirely. Only business communications are archived.

  • No change to how they work

    Employees keep using Gmail, Chat, and Drive exactly as they do today. No notifications, no new logins, no awareness that anything is different.

FAQ about Google Workspace Compliance Archiving

Does Comma replace Google Vault? Can we keep Vault and use Comma?
For regulated firms with SEC Rule 17a-4 and FINRA Rule 4511 obligations, Comma replaces Google Vault as the books-and-records archive. Vault is an internal retention tool built for litigation holds, not a regulatory-grade external WORM archive. That said, you can keep Vault in place if you choose. Comma operates independently of Vault configuration and captures a separate, immutable copy of every record into its own WORM archive. Any change to Vault retention or holds has no effect on the Comma archive.
Does Comma archive our Gmail?
Yes — every inbound, outbound, CC, BCC, and attachment from Gmail and Google Workspace mail is captured in full, the moment it is received.
What Google Workspace edition do we need?
Comma works with any Google Workspace edition that allows OAuth admin consent (Business Starter and above). You do not need Google Vault or a higher-tier Workspace license to use Comma — Comma provides the regulatory-grade retention layer independently.
Are Google Drive files and Meet recordings included?
Yes. Google Workspace capture covers Gmail, Google Chat, Google Drive, and Meet recordings, all captured through the same admin-consent connection into the same archive.
How quickly can we produce records for an SEC or FINRA exam?
Records are retrievable directly from the Comma platform within minutes. No support ticket, no Google API query to script. Cross-channel, including non-Google channels like WhatsApp and Signal, from the same interface.
Can we revoke Comma's access?
Access can be revoked from the Google Admin console. Existing records in the Comma archive are unaffected — but revocation stops future capture, which should be coordinated with your compliance team before disconnecting.

See how Comma archives Google Workspace.

A 20-minute walkthrough: one admin-consent connection, real capture across Gmail, Chat, Drive, and Meet, and exam-ready export.

Get in Touch Pricing

Related reading

Other channels we support

WhatsApp Compliance Archiving

WhatsApp archiving via the official Business API — full message capture including attachments, voice notes, and group chats.

See solution →

iMessage Compliance Archiving

Point-of-delivery iMessage capture. No iCloud dependency, no MDM. Built for BYOD.

See solution →

All 40+ Channels

Google Workspace is one of 40+ channels Comma archives. WhatsApp, Signal, iMessage, Bloomberg Chat, and more — all from one platform.

See all channels →