Privacy for Gig Finder Local Calendar
This page describes the private, owner-operated desktop integration between the locally installed Gig Finder workspace and a selected Google Calendar.
When Google Calendar data is accessed
Access begins only after the owner explicitly starts the local desktop authorization flow and signs in through Google. The software verifies the selected account and calendar before it treats the connection as usable.
The implementation can read the selected calendar’s list entry and event records. For an event, the local integration may retain the summary, start and end information, event status, transparency, all-day dates where present, provider-supplied timezone metadata, and provider identifiers or version information needed to reconcile later reads.
Local storage and credentials
Calendar observations, local holds, review records, and audit receipts are stored in the local Gig Finder Operations database on the owner’s machine. The local calendar ledger remains separate from provider observations.
The refresh credential is stored through Windows DPAPI outside that Operations database. The application does not place the refresh token in ordinary calendar receipts or tool responses.
No fixed retention period is represented by this page. Local records can remain until they are changed or removed through the owner’s installed workspace or data-management process.
Data sent to Google
The desktop integration communicates with Google OAuth and Google Calendar endpoints to authorize the local connection, verify the selected account and calendar, refresh short-lived access, and perform the requested calendar operation. The static pages in this folder contain no sign-up form, analytics script, or OAuth credential form. A host that publishes these files can have its own server logs and policies.
Google’s handling of data is governed by Google’s own terms and privacy materials. This page describes Gig Finder’s local integration behavior, not Google’s services.
Disconnecting or revoking access
The owner can revoke Google access through the Google Account security controls. If a refresh credential is rejected, unavailable, or no longer matches the verified account or calendar, the local runtime changes that connection to a reconnect-required state and stops using it. Revoking access does not itself state that previously stored local calendar records are erased.