billed monthly, in advance
| Workloads | Gmail · My Drive · Shared Drives · Contacts · Calendars · Tasks |
|---|---|
| Cadence, Gmail | 12 passes per day |
| Cadence, My Drive and Shared Drives | 3 passes per day |
| Cadence, Contacts / Calendars / Tasks | 1 pass per day |
| Encryption | AES-256 at rest; TLS/SSL in transit |
| Custody | Held independently of your Google tenant |
| Restore unit | A single email · a single file · a mailbox · an entire account |
| Export | Supported, for legal hold and handover |
| Billing unit | Per licensed user, per month |
The whole working surface
An account in full, comprising Gmail, My Drive, Shared Drives, Contacts, Calendars, and Tasks, including the shared drives holding all the material that no single person owns.
Google is extremely good at keeping the service reachable, and reachability was never the exposure. The exposure is a hijacked session, a departing employee with a grievance, a mis-scoped script, or an ordinary person deleting exactly the wrong folder, and every one of those actions is replicated to all of your devices, perfectly, within seconds.
How it runs
High-frequency automated capture, tuned to how quickly each workload actually changes:
- Gmail, 12 passes per day. Roughly a two-hour recovery point on the system carrying most of your institutional memory.
- My Drive and Shared Drives, 3 passes per day.
- Contacts, Calendars, and Tasks, daily.
Restores are granular from the outset: locating one email is the same operation as restoring an entire account, simply scoped smaller.
Cadence is a security control, not a specification flourish
Data is encrypted with AES-256 at rest and TLS in transit, and the vault is not part of your Google tenant, so a super-administrator compromise there does not reach back into the history. The same principle applies everywhere in this catalog: the copy has to sit outside the blast radius, or it is decoration.
Then there is frequency. Twelve passes a day place roughly two hours between any incident and the last clean copy of the mailbox. Recovery point is not a sentence in a policy document. It is arithmetic on the interval between captures, and this line keeps that interval shortest on the workload carrying the most history.
Getting it back
Search and restore a single item, restore a full account after a departure or a takeover, or export data for legal hold. Restores return to where they belong, and the granular path means the usual request, which is a single deleted thread, does not require touching anyone else's mailbox.
Where this line stops
Billing is per licensed user, per month, and the cadence figures above are the maximums for each workload. This is not a continuous mirror, and it is not intended to be. If you also operate Microsoft 365 somewhere in the business, that tenant requires its own line; nothing here reaches across suites.