Privacy
Last updated: September 2, 2026
This is product copy that needs legal review before a public launch. It describes the data flows visible in the Coworkers.dev codebase. Coworkers.dev, or the operator of Coworkers.dev, may update it when those flows change.
Information the application handles
The application handles the information needed for the features you choose to use:
- Account information, including an email address, name where supplied, and authentication records.
- Content you create or provide, including bot instructions, messages, tasks, memories, files, routines, and support communications.
- Connection data you add, such as API keys, OAuth tokens, model-provider settings, and browser-session data. The application is designed to encrypt stored OAuth tokens and other stored credentials.
- Technical and diagnostic data produced when you use the website or application, such as device push tokens, session information, timestamps, and service logs needed to operate or investigate a problem.
Google sign-in
Google sign-in is available only when an operator enables and configures it. Coworkers.dev uses the Google identity token and verified email returned during sign-in to authenticate your account. The mobile app requests an ID token with offline access disabled. Coworkers.dev does not use Google account data for other purposes based on the application code reviewed for this page.
How information is used
The application uses this information to authenticate accounts, provide the bots, routines, connections, notifications, and workspace features you request, and maintain and troubleshoot the service. It does not contain code to sell personal information or use your content for third-party advertising.
Service providers and integrations
Information can be sent to providers you or the operator configure to complete a requested feature. Those providers can include an AI model provider, a connected application, a sandbox or computer provider, and a push-notification service. The public website can also send website analytics to PostHog when its analytics key is configured. Each provider handles information under its own terms and privacy notice.
Retention and deletion
The mobile application has an account-deletion action. Its confirmation describes deletion of the account, bots, conversations, memories, files, and saved connections. Account deletion also clears the local mobile session. Some provider-held information and service logs may follow their own retention settings. The codebase does not state a general retention schedule, so Coworkers.dev does not promise one here.
Security limits
Coworkers.dev includes access controls and encryption for certain stored credentials, but no software or service can guarantee absolute security. Protect your account credentials and any connection credentials you choose to add.
International processing
If the website analytics integration is enabled, the default configured endpoint is PostHog's United States endpoint. Other processing locations depend on the service providers and deployment selected by you or the operator.
Contact
Questions about this notice can be sent to contact@coworkers.dev.