Scope of this notice
This notice describes the current privately operated, single-user PACE Google Calendar, Drive and Gmail integrations. It does not describe every future PACE source, model or feature, or all practices of the website hosting this notice. There is no public account-creation service described here.
Information read and purpose
The operator authorizes Calendar read-only and Drive read-only scopes. The Calendar scope can expose authorized calendar information and event fields, including titles, descriptions, attendees, organizers, location, dates, times, recurrence/instance information, cancellation status, visibility and private fields returned by Google. PACE preserves the returned raw event API representation for personal retrieval, preparation and source-grounded continuity. It does not invent fields or expand a busy-only response into unavailable details.
Calendar requests are limited to an explicit private list of calendars and a verified primary account. The intended history begins on 1 January 2026 and extends twelve months forward. Complete acquisition of that window remains under evaluation.
Drive read-only access is broad and can permit viewing/downloading files accessible to the authorized Google account, not only calendar attachments. The provider’s current use is narrower: official file-ID attachment metadata and eligible binary bytes, with size, checksum and before/after version checks. It does not follow fileUrl, htmlLink, description or conference links. Native Workspace exports, shortcuts and inaccessible/restricted or unsupported files are not silently treated as full originals.
The separate Gmail grant is read-only. It can expose all mail, message bodies and attachments, labels, thread and message identifiers and mailbox metadata available to the authorized account. PACE uses captured correspondence for the operator’s personal retrieval and source-grounded continuity. Received, sent and archived mail are eligible, without a historical cutoff. Current Spam, Trash and drafts are excluded before new capture; exclusion does not erase previously preserved records. Available-history capture, changes and full attachment coverage remain under evaluation.
Storage, credentials and access
PACE stores captured calendar records, Gmail message originals, eligible attachment bytes, revisions and source information in private local operator-controlled storage. Backups may retain copies. Separate provider credentials, including refresh tokens, are restricted to the local owner; access tokens are refreshed in memory.
Local owner restrictions and source/account access checks protect ordinary application access. PACE does not promise application-level encryption of its stored information, credentials or backups. Operating-system or volume encryption is a separate configuration and is not established by this notice. Same-user administrative or authorized assistance access is not prevented by these application checks.
The Google providers communicate with Google over HTTPS. Routine failures are reported without Google response bodies or authorization secrets. Saved calendar and Gmail records and attachments contain authorized source information; they are not anonymous diagnostics.
Operator inspection and disclosure boundary
The operator and specifically authorized operational or assistance tools may inspect selected local records or private receipts for verification, troubleshooting and retrieval. This can involve selected source content as well as metadata; it is not limited to anonymous diagnostics. These tools and any disclosure to them require the applicable operational authority. This notice does not itself authorize new external disclosure.
The current Google providers send authorization and acquisition requests to Google and returns data to the local PACE owners. Those provider implementations do not implement advertising, sale of Google data, a public sharing endpoint or model-training transfer. This limited code statement is not a comprehensive assurance about every operator tool, website service or future PACE model/data practice. Any broader use needs separate review and applicable permission before it is enabled.
Retention, revocation and removal
PACE preserves originals and distinct revisions for later retrieval. A source event or message changing, being cancelled or being deleted does not automatically erase the retained PACE record. Revoking Google access or disconnecting acquisition stops permitted future API access once effective; it does not remove existing local originals, metadata, credentials or backups.
The operator must separately stop or reconfigure acquisition and manage credential removal and any disposition of local records and backups. A self-service deletion interface and automatic deletion when Google access is revoked are not provided. No deletion deadline, indefinite retention guarantee or backup-erasure guarantee is offered by this notice.
Authorization and completeness limits
Google authorization can expire or be revoked. Google’s Testing mode imposes a seven-day refresh-token limitation for these scopes. Production audience is distinct from Google verification and does not guarantee permanent tokens. Refresh-token rotation currently requires explicit reprovisioning rather than silent credential replacement.
PACE can save and reopen captured calendar records and Gmail messages. Complete historical coverage, attachment acquisition, timely updates, changes, source-status reconciliation and durable unattended access remain under evaluation. A bounded inspection finding no attachment does not establish that the source contains none.
Questions
For questions about this private integration, use the support contact shown on PACE’s Google authorization screen.