Your data, for your personal workflow.

PersonalOS Calendar is a personal Windows and Obsidian automation program. This page describes its Google integrations and local data handling.

Calendar data

The program uses event titles, start and end times, all-day status, descriptions, event IDs, links, and location information when available to create requested events, query schedules, check duplicates, and verify results. A created event description may include the user's original scheduling instruction. Schedule summaries may be written to local Obsidian notes.

Calendar authorization uses https://www.googleapis.com/auth/calendar.events. The current workflow uses it for event creation and querying; this scope can authorize additional event operations.

Drive metadata

The Drive integration requests https://www.googleapis.com/auth/drive.metadata.readonly to retrieve file and folder names, IDs, parent relationships, web links, size, modification time, and checksums when available. It follows configured processed-file folder paths to identify the correct file.

This Google scope permits account-wide metadata access; the program limits its automatic lookup workflow to configured folders. This API integration does not read file contents or upload, modify, or delete Drive files. Separate user-authorized local file operations may manage files through Google Drive for desktop.

Storage and use

OAuth credentials, including access and refresh tokens, are stored in the user's local Windows environment. Calendar and Drive tokens are kept separately. Notes, processing records, file references, and metadata are stored locally as needed for the workflow. The program does not automatically publish them to this website. Any configured Obsidian or Google Drive synchronization remains subject to those services and the user's settings.

Sharing and retention

Data is used for the requested personal automation and is not sold to third parties. Requests needed for Calendar and Drive integration are sent to Google. Local notes and processing records remain until the user removes them under their file-management rules; revoking access does not delete existing local records.

Your control

You can revoke the program's access in your Google Account connections. Further authenticated access requires valid authorization. You can also manage local credentials and records in your own environment.