Purpose and current use
PACE (Composable-PACE 2026) is a privately operated, single-user application for preserving and retrieving the operator’s authorized information. Google Personal is its canonical personal-calendar source. Its separate Gmail connection reads the approved personal mailbox. This page describes those Google integrations, not a public sign-up or commercial service.
PACE can save and reopen captured calendar records and Gmail messages. Complete history, attachment coverage, timely updates and uninterrupted unattended access remain under evaluation.
Google access
PACE requests Google Calendar read-only and Google Drive read-only access. Calendar read-only access can expose calendar details and events, including private-event fields available to the authorized account. PACE restricts its provider requests to explicitly configured calendars and verifies the primary account before acquisition.
Drive read-only is broader than an attachment-only permission: it can permit viewing and downloading accessible Drive files. The current calendar provider uses official file IDs supplied by admitted event attachments to request metadata and eligible binary bytes; it does not crawl Drive, follow event links or export native Google Workspace documents. These implementation limits do not reduce the breadth of the OAuth permission itself.
Gmail read-only access can expose all messages, bodies, attachments, labels and mailbox metadata available to the authorized account, including material PACE excludes during ingestion. PACE admits the approved personal account’s received, sent and archived messages, with resumable available-history capture. It excludes current Spam, Trash and draft messages before new capture. These selections do not narrow Google’s permission boundary or erase earlier retained copies.
PACE does not send, modify or delete Gmail messages, calendar events or Drive files through these providers. Calendar selection can exclude explicitly configured structural busy-copy records without changing Google.
Local preservation and limits
Calendar API records, captured message originals, eligible attachment bytes, source information and revisions are stored in the operator’s private local PACE storage. Gmail credentials are separate from Calendar/Drive credentials and restricted to the local owner. Retained records and backups may outlive source changes, disconnection or revocation.
Saved calendar records use Google’s API representation. Saved Gmail originals are the complete RFC2822 bytes decoded from Google’s RAW response, rather than a claim about an unseen SMTP or mailbox container. Attachments or text extraction may be unavailable or unsupported; complete coverage is not established.