workgraph is local-first software for capturing and organizing personal work context. The application stores captured events and connector data locally on the user's device unless the user explicitly chooses otherwise.
Information workgraph accesses
When a user connects a third-party service, workgraph requests only the access needed for the enabled connector. Connected services may include Slack, Google Calendar, Gmail, Microsoft Calendar, Microsoft Mail, Notion, Jira, Azure DevOps, and other services the user chooses to enable.
How information is used
workgraph uses connected account data to create local work events, help restore context, and show activity through local commands such as today and resume. workgraph does not sell user data or use connected account data for advertising.
How information is stored
Connector credentials, captured events, and user settings are stored locally in the user's workgraph home directory, normally under ~/.workgraph. User settings are stored in ~/.workgraph/settings.json. Connector credential files are written with local-user-only file permissions when supported by the operating system.
Data sharing
workgraph does not share connected service data with third parties. Captured data remains local unless the user explicitly exports it, commits it, shares it, or configures another tool to read it.
Optional AI providers
Core workgraph capture, storage, memory, today, and resume behavior does not require an LLM provider. If a user configures an LLM profile, workgraph may send selected task context to the configured model endpoint for that user-requested LLM command. Managed settings can disable hosted LLM providers or restrict approved model destinations for managed deployments.
Connected service data
workgraph uses connected service data only to create local work events, restore context, and support user-requested local workflows. Each connector should request the narrowest practical read-only access for the behavior the user enables.
For an IT-readable summary of Slack scopes, managed settings, local storage, and enterprise review boundaries, see the workgraph Slack and Enterprise Compliance page.
Mail data
When a user enables a mail connector, workgraph may read message metadata and full message content for mail the user can access. Mail data is used to create local work context records, connect conversations to projects, and help restore relevant work context. workgraph does not modify, send, delete, or label email.
Notion data
When a user enables the Notion connector, workgraph may read Notion workspace, page, database, block, user, and comment data that the user authorizes through Notion's OAuth flow and page picker. Notion data is used to create local knowledge and work context records, connect documents to projects, and help restore relevant work context. workgraph does not sell Notion data, use Notion data for advertising, or use Notion data to train non-personalized AI or machine learning models.
OAuth token relay
For Google OAuth, workgraph uses a limited token relay hosted on Cloudflare Workers to complete OAuth token exchanges. During initial connection, the local app sends the authorization code, PKCE code verifier, redirect URI, client ID, and grant type to the relay. During token refresh, the local app sends the refresh token, client ID, and grant type to the relay. The relay adds the Google OAuth client secret, forwards the request to Google, returns Google's token response, and does not store or log OAuth codes, tokens, request bodies, calendar data, or mail data.
For Notion OAuth, workgraph uses a limited token relay hosted on Cloudflare Workers because Notion public OAuth connections require a client secret when exchanging authorization codes and refresh tokens. During initial connection, the local app sends the authorization code, redirect URI, client ID, and grant type to the relay. During token refresh, the local app sends the refresh token, client ID, and grant type to the relay. The relay adds the Notion OAuth client secret, forwards the request to Notion, returns Notion's token response, and does not store or log OAuth codes, tokens, request bodies, page data, database data, or workspace content.
Google API data
workgraph's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
User control
Users can disconnect a connector, delete local connector credentials, or remove local workgraph data from their device. Google account access can also be revoked from the user's Google Account security settings. Notion access can also be revoked from the user's Notion workspace connection settings.
Contact
For privacy questions, contact the workgraph project maintainer through the repository or project channel where workgraph was obtained.