Open Coworker
Legal

Privacy Policy

Effective: July 14, 2026 · applies to opencoworker.app, the downloadable app, and OpenCoworker Cloud

Open Coworker is built local-first: your work stays on your machine. This policy explains exactly what leaves it, when, and why — for this website, the downloadable app, the optional OpenCoworker Cloud account, and the services you choose to connect, including your Google account. “We” are the maintainers of the Open Coworker project.

01The short version

  • The app runs on your computer. Sessions, files, memory, API keys, and connection tokens are stored on your device — not on our servers.
  • We collect no telemetry and run no analytics, in the app or on this site.
  • Content is sent off your machine only in three cases: to the model provider you configure, to services you connect (at your direction), and — if you sign in — the minimal account data OpenCoworker Cloud needs to work.
  • We don’t sell data, show ads, or use your data to train AI models.

02This website

opencoworker.app is a static site hosted on GitHub Pages. We run no analytics and set no tracking cookies. GitHub may log standard technical data (such as IP addresses) under GitHub’s privacy statement.

03The app on your machine

Everything the app produces lives locally: your conversations and sessions, files it reads or writes, its memory, your settings, the API keys you enter, and the access tokens for services you connect. Deleting the app’s data folder (or uninstalling) removes them. We cannot see, access, or recover any of it.

04Your model provider

The app works with an AI model you supply — a commercial provider you hold an API key for (such as OpenAI, Anthropic, or Google), or a local model on your own hardware. When you give the coworker a task, the relevant conversation content — which can include text from files, emails, calendars, and other sources the task touches — is sent to your chosen provider to generate the response. That transfer happens at your direction, to serve your request, and is governed by your agreement with that provider. With a local model, nothing leaves your machine at all.

05OpenCoworker Cloud (optional)

The app works without an account. Signing in to OpenCoworker Cloud adds managed connections (one-click OAuth for services like Google, Slack, and GitHub). If you sign in, we store the minimum needed to operate your account:

  • Identity: your email address and name, via our sign-in provider (Auth0), plus an internal account ID.
  • Connection metadata: which services you’ve connected and when — e.g. “Google, connected July 2026” — so the app can show and manage your connections.

What we deliberately do not store server-side: your conversations, your files, and — see the next section — the access tokens for your connected services or any content from them.

06Connected services and our OAuth broker

When you connect a service (Google, Slack, GitHub, Microsoft, HubSpot, and others), the sign-in handshake runs through our connection broker at api.opencoworker.app. The broker’s only job is to complete the OAuth exchange: it passes the service’s tokens through to the app on your device, where they are stored. The broker is stateless — it does not keep your tokens or any content from your connected services. From then on, the app on your machine talks to the connected service directly.

For inbound messaging (for example, mentioning the coworker in Slack), events are forwarded through our relay to the app on your device in real time. The relay passes messages through; it does not store their content.

07Google user data

Connecting your Google account is optional, and each Google connector asks for its own consent — connecting Calendar never grants Gmail access, and vice versa. This section describes our use of Google user data for all Google connectors.

What we access

  • Gmail — read messages (gmail.readonly) and send messages (gmail.send), so the coworker can summarize, search, and answer questions about your email, and send email you compose or approve.
  • Google Calendar — read and manage events (calendar), so the coworker can check your schedule and create or update events you ask for.
  • Google Drive — read-only access to files (drive.readonly), so the coworker can read documents you point it at.

How we use it

Google user data is used solely to provide the features you invoke, on your device. The app fetches your Google data directly from Google’s APIs to your machine. When a task you request involves that data — “summarize this morning’s email” — the relevant content is included in the prompt sent to the model provider you configured, at your direction, to serve that request. We do not use Google user data for advertising, and we do not use it to train AI or machine-learning models — neither generalized nor personalized.

Where it’s stored

Your Google access tokens are stored on your device only. Gmail, Calendar, and Drive content is processed on your device and is never stored on — and never transits — our servers. The broker (section 06) touches tokens only during the initial sign-in exchange and does not retain them.

Who we share it with

No one, with two exceptions, both under your control: the model provider you configured (as described above), and actions you explicitly direct — for example, an email the coworker sends on your behalf goes to its recipients. We never sell Google user data, never share it for advertising, and no human at Open Coworker reads it (we couldn’t — it isn’t on our servers).

OPEN COWORKER’S USE AND TRANSFER OF INFORMATION RECEIVED FROM GOOGLE APIS WILL ADHERE TO THE GOOGLE API SERVICES USER DATA POLICY, INCLUDING THE LIMITED USE REQUIREMENTS.

Revoking access

Disconnect any Google connector in the app’s settings at any time — this deletes the tokens from your device. You can also revoke Open Coworker’s access from your Google Account security settings.

08Retention and deletion

  • On your device: data stays until you delete it — remove individual sessions and connections in the app, or delete the app’s data folder to remove everything.
  • OpenCoworker Cloud: account records are kept while your account exists. To delete your account and its records, contact us (section 12); we’ll complete deletion within 30 days.

09Security

All connections between the app, the broker, and connected services use HTTPS/TLS. Tokens and keys on your device are stored in files restricted to your OS user account. The broker holds no databases of tokens or content — what doesn’t exist can’t leak. No method of storage or transmission is 100% secure, but keeping your data on your device, under your control, is the strongest default we know how to ship.

10Children

The Services are not directed to children under 13 (or the equivalent age in your jurisdiction), and we do not knowingly collect personal information from them.

11Changes to this policy

When we change this policy, we’ll post the new version here with a new effective date. For material changes affecting Google user data, we’ll be conspicuous about it — a notice on this site and in the app’s release notes.

12Contact

Privacy questions or deletion requests: email rohit@opencoworker.app, or open an issue on GitHub.