Effective October 16, 2026 · Automation (Google Ops)
Privacy policy
This policy describes the Google user data used by an independently operated personal automation application. The public information pages do not require account authorization.
Operator and use
The account owner operates this application for personal Google Workspace workflows. Questions and data-handling requests: alsoabel@gmail.com.
What Google data is accessed
- Gmail: message contents and metadata, threads, labels, settings, forwarding and native filters.
- Calendar: event details, invitations, availability and itineraries.
- Drive and Sheets: selected documents, attachments, folders, spreadsheets and operational audit records.
- Apps Script: automation triggers, project execution information, diagnostic state and account identity.
How information is used
Authorized functionality includes reviewing and labeling email, managing reviewed Gmail rules, surfacing pending responses, reconciling calendar events, filing selected records and monitoring automation health. Google user data is not sold or used for targeted advertising.
Processing and service providers
Primary processing occurs in the owner's Google Workspace services and Google Apps Script. Separately authenticated Cloudflare services may transport authorized management requests. Some optionally enabled advisory classification workflows may transmit minimized email-derived information through Cloudflare infrastructure or configured model processors. External processing requires its own configuration and approval; publication of this page does not authorize any additional provider.
Storage, retention and deletion
Gmail and Calendar records remain in the owner's Google account except where expressly configured workflows modify them. Selected files, logs and automation state may be stored in Google Drive, Sheets and Script Properties, with limited operational metadata in connected infrastructure. Retention depends on workflow configuration and owner-controlled deletion rather than one universal fixed retention period. The owner can delete associated Google records, disable workflows and revoke OAuth access. Provider backups or audit records may follow their own retention controls.
Security and access controls
Private operations use Google authorization and separately secured credentials where applicable. The public information pages have no user-data API access and do not expose Google account contents, tokens or administrative controls. The operator aims to minimize data disclosure and unnecessary content logging. Review access at Google Account connections.
Policy updates and requests
This policy should be revised when material processing or provider changes occur. Contact alsoabel@gmail.com for questions, access, retention or deletion requests.