Calendar connection privacy

Effective October 5, 2026

This notice explains how ClearLobby handles information when you connect Google Calendar, Microsoft Outlook, or Apple Calendar to its legislative calendar features. Contact shruthika@clearlobby.com with calendar privacy questions or deletion requests.

Information used

When you authorize Google or Microsoft, ClearLobby receives your provider account identifier, email address, granted permissions, and access and refresh tokens. Tokens are stored encrypted and let ClearLobby synchronize without asking you to sign in for each update. ClearLobby stores the identifier of its dedicated calendar, source-to-provider event mappings, your calendar preferences, and synchronization status.

Google Calendar

New Google connections request permission to create secondary calendars and manage events in those calendars. ClearLobby writes legislative meeting titles, times, locations, official agenda notes and links, and relevant tracked-bill information into its dedicated ClearLobby Legislative Calendar. This feature does not import your primary Google calendar or use Google Calendar information to train AI models. Earlier connections may still have a broader Google permission; you can revoke that grant in your Google Account and reconnect to authorize the current permission.

Microsoft Outlook

Direct Outlook connections request account identity, calendar read/write access and offline access for automatic synchronization. Microsoft grants permission covering user calendars; this is not limited by Microsoft to the ClearLobby calendar. ClearLobby restricts its application operations to the dedicated calendar it creates and its own event mappings. It does not enumerate your calendars, import personal meetings, or check availability. Access tokens remain capable of broader calendar access, so these restrictions are application safeguards rather than a Microsoft-enforced single-calendar permission. You can instead use a private subscription without granting Microsoft account access; Outlook controls its refresh timing. Legacy credentials remain disabled and require fresh authorization.

Apple Calendar

ClearLobby supplies a private subscription link shared by the Outlook and Apple options without collecting your Apple credentials. Anyone with that link can retrieve the personalized legislative feed. Keep it private. Resetting the link invalidates the old one, and disabling the subscription stops future feed retrieval. Apple controls refresh timing.

Use and sharing

Calendar information is used to provide and maintain the requested integration, synchronize your selected legislative events, show connection status, and investigate failures. Legislative event details selected for synchronization are sent to your chosen calendar provider. ClearLobby's hosting and infrastructure providers process data to operate the service. Other people may see events according to the sharing settings you choose in your calendar provider. Connecting a calendar does not grant other ClearLobby workspace members access to your personal primary-calendar meetings.

Retention and control

Disconnecting in ClearLobby stops synchronization and clears usable OAuth credentials. Previously written events remain in your provider calendar. Calendar identifiers and event mappings are retained to prevent duplicates when you reconnect. You can also revoke Google access at https://myaccount.google.com/permissions or revoke Microsoft access in your Microsoft account. Contact the address above to request deletion of retained connection metadata.

Security and limitations

Connections use HTTPS and encrypted stored tokens. Account and workspace authorization restrict access in ClearLobby. No system can guarantee uninterrupted operation; provider revocation, expired permissions, or administrative restrictions may require reconnecting. ClearLobby does not sell Google user data, use it for advertising, or transfer it for unrelated purposes. Its use and transfer of Google API information adheres to the Google API Services User Data Policy, including Limited Use requirements.

Optional action suggestions

ClearLobby prepares neutral action playbooks from official public Washington bill records using OpenAI. Bills for that work are selected by a public-catalog queue independently of customer bill interests, tracking, priorities, usage, and workspace requests. Only allowlisted public bill excerpts, public bill identifiers, session and version, and recorded public event times are sent for this purpose. Refreshing your suggestions does not call the model or enqueue the bills you track.

ClearLobby matches and ranks those public playbooks against your tracked bills and saved issue priorities inside its own service. Your selected bill interests, organization and client identities, positions, priorities, strategy, private notes, existing task text, contacts, meetings, reports, and connected Google, Microsoft, and Apple calendar information are excluded from the action-suggestion provider requests. Public playbooks can be reused across workspaces; private matches, edits, decisions, and accepted actions cannot. This feature does not send communications, decide your position, or add an action until you review and accept it. Workspace AI opt-in and role permissions remain required for refreshing your suggestions; these controls do not override customer agreements.

Public-record requests use the OpenAI API with response storage disabled. This setting is not a promise of zero provider retention; provider abuse monitoring, applicable contracts, and account settings can still govern retention. See OpenAI’s API data controls. ClearLobby stores private drafts, supporting source excerpts, review decisions, and accepted tasks in the authenticated workspace. Private input and output content is not included in application audit messages or shared public caches. Browser review drafts are scoped to the signed-in user and workspace in session storage; recovery is available for 24 hours, and expired entries are removed on the next review. Browser storage may remain until that review or the browser session ends. Dismissal hides a suggestion rather than deleting its decision history; contact ClearLobby for workspace data deletion requests.

Action-suggestion supplement effective October 19, 2026. Calendar permissions and the calendar information commitments above are unchanged.

For privacy questions or deletion requests, email shruthika@clearlobby.com.

Google API Services User Data Policy