EFFECTIVE OCTOBER 1, 2026

Privacy policy

Big Sal’s Personal Assistant is a personal, owner-operated planning tool run by Lascelles McCarthy III. This policy explains its Google Calendar access. The public information pages do not ask visitors to connect a Google account.

What the assistant accesses

With the owner’s Google authorization, the assistant may request two separate Calendar permissions: one to see events on calendars the owner owns, and one that Google describes as permission to see, create, change, and delete events on calendars the owner owns. The assistant’s current implementation limits its Calendar operations to the primary calendar. It requests event IDs, status, availability, and start and end times for an approved time window; it does not request event titles, descriptions, attendees, or locations during the planning read.

The current write flow creates one owner-reviewed event at a time. It can also check the ID of a previously approved event to determine whether an uncertain write succeeded. The software does not currently offer general event editing or deletion, even though Google’s write permission is broader than these implemented actions.

How the data is used

Calendar timing and availability are used to show conflicts and suggest planning options to the owner. The assistant accesses Google Calendar only for a request the owner has reviewed and approved with a passkey. It does not use Calendar data for advertising, profiling, or training a general AI model. Calendar data is not sent to the separate AI content-drafting service.

Storage and security

Google refresh credentials are stored in a protected, locally operated credential vault on the owner’s machine. Short-lived access tokens are used to make the approved Google request. Read results are returned to the owner’s browser for the current request; the assistant does not keep a general copy of the owner’s calendar. To prevent duplicate actions and support review, it retains approval evidence, request details for approved writes, event identifiers, outcomes, and audit records on the owner’s machine. These records can include the time and title of an event the assistant created. The records are not public.

Sharing and retention

The assistant sends OAuth and Calendar requests to Google to provide the described features. It does not sell or share Google Calendar data with advertisers, data brokers, or other outside services. Locally stored credentials and operational records remain until the owner removes them or retires the system; no automatic deletion period is currently configured for those records. Revoking Google access stops future Google requests using that grant but does not itself erase existing local audit records or events already created in Google Calendar.

Your choices

The owner can decline any individual read or write approval. The owner can also revoke this app’s Google access in Google Account connections. To ask about locally stored data or request its removal, contact lascellesmccarthyiii@gmail.com. Removal requests must be reconciled with records needed to confirm past calendar actions.

Google data policy

The use of information received from Google Workspace scopes will adhere to the Google API Services User Data Policy and the Limited Use requirements.

Questions about this policy: lascellesmccarthyiii@gmail.com.