Personal OS Cloud Bridge Privacy Policy
Personal OS Cloud Bridge is a private integration operated for its owner’s personal use. This policy describes its existing Google-service connections and the read-only Gmail connection being prepared.
Information accessed and purpose
Google Drive. The existing system reads selected files and submissions used for personal planning and maintains designated briefing files. Access is restricted through the configured credentials, file permissions, and application controls.
Google Calendar. The existing system reads availability and selected event information, including event titles, dates, descriptions, and locations, to support planning and event preparation. Separately authorized calendar operations use existing approval and application controls.
Gmail. The new Gmail connection is not yet active. Its prepared authorization request uses the gmail.readonly scope. This permission permits reading Gmail data; it does not permit sending email or modifying the mailbox. The connection checks that the authorized account is the configured owner account.
The intended Gmail use is to identify relevant requests and follow-ups and prepare summaries or proposed actions. This may involve reading message content, participants, dates, and message or thread identifiers. The requested permission is broader than any particular set of messages selected for processing.
Permissions listed in a Google Cloud project are not necessarily the permissions requested or exercised by each connection. The prepared Gmail connection requests only Gmail read-only access; existing Drive and Calendar connections use their own credentials and controls.
AI processing and connected services
Personal OS uses OpenAI services to interpret selected planning information and prepare proposed actions. Information supplied for these purposes leaves the owner’s computer and is processed by OpenAI.
The planned Gmail workflow may supply selected message information to this existing AI processing route. It has not yet been activated or verified end to end.
Planning results and related information may be retained in the owner’s local Personal OS records, Todoist tasks and comments, Google Drive briefing files, and assistant conversations used by the owner. These services process information under their applicable terms and account settings.
The integration does not publish private messages or operational records on this website. This policy does not claim that all processing remains local or that service providers retain no data.
Storage and retention
The prepared Gmail connection stores its authorization credential in a protected location on the owner’s computer after successful consent and account verification.
The existing system retains assignment results, source references, processing receipts, and other operational history. The prepared Gmail evidence component retains message and thread identifiers, observation times, and a content fingerprint rather than returning message bodies as evidence. This component alone does not establish what other processing stages or service providers retain.
Summaries and proposed actions can contain information derived from source material. No universal automatic deletion period has been established for all local records, connected services, conversations, or backups.
Revoking access and removing retained information
The owner can revoke the Gmail connection through the Google Account’s third-party connections controls and stop the corresponding integration. Revocation prevents continued use of that authorization; it does not automatically erase information already retained elsewhere.
Removal of retained information requires reviewing the relevant local records, connected-service records, and assistant conversations separately. Provider-held records and backups are subject to the provider’s controls and retention practices. Immediate or simultaneous deletion from every location is not promised.
For questions about access or retained information, contact carving.roomed_8r@icloud.com.
Changes
This policy should be updated when verified data practices change. Publishing a policy does not authorize additional access or processing.