Workmate Sub-Processors

Last updated: November 13, 2026

Workmate Labs, Inc. (“Workmate”) engages a small number of trusted third-party service providers (“Sub-Processors”) to help deliver the Workmate Platform. The tables below describe platform providers and connected services that may process Customer Data, depending on the features and integrations used.

We perform security and privacy due diligence on every Sub-Processor before engaging them, and we enter into written data-protection agreements that bind them to confidentiality, security, and lawful-processing obligations consistent with Workmate's commitments to its customers.

This page is the authoritative list of Workmate Sub-Processors. To receive notice of changes to this list, please email support@workclaw.com and ask to be added to the Sub-Processor notification list.

Cloud Infrastructure & Hosting

ProviderPurposeData Processed
Amazon Web Services (AWS)Primary cloud infrastructure: application hosting, databases (RDS PostgreSQL), object storage (S3), container orchestration (ECS / ECR), secrets management (SSM Parameter Store), and scheduled job execution (EventBridge Scheduler).Customer Data stored in Workmate-managed AWS infrastructure, including team and user records, Workmate configurations, message history, uploaded files, and credentials.
Vercel Inc.Hosting and edge delivery of the Workmate web application, marketing site, and serverless functions.HTTP request metadata, application traffic, and content served to end users.

AI & Large Language Model Providers

ProviderPurposeData Processed
Amazon Web Services (AWS Bedrock)Default model inference provider for requests routed through OpenRouter. AWS Bedrock runs the selected models and returns their responses through OpenRouter.Prompts, conversation context, tool inputs and results, file content included in model requests, model responses, and usage metadata.
OpenAISecondary model inference provider and image generation; optional hosted agent execution, including hosted workspace environments and file exchange.Prompts, conversation context, tool inputs and results, model responses, images, workspace files uploaded to or generated in hosted environments, and usage metadata, depending on the features used.
Google LLC (Gemini)Secondary model inference provider for AI translation of session content through the Gemini API, only when translation is enabled and used for non-English content.Session content included in translation prompts and the resulting translations. This AI processing is separate from connected Google Workspace services.
Anthropic, PBCSecondary model inference provider for in-product assistance, including message filtering, intent classification, and setup flows; optional managed agent sessions with workspace file exchange.Prompts, messages, configuration, tool inputs and results, model responses, and workspace files uploaded to or generated in managed agent sessions, depending on the features used.
OpenRouter, Inc.Routing layer that sends model requests to AWS Bedrock for inference during Workmate execution, with usage metering and monitoring. OpenRouter routes the requests; AWS Bedrock is the inference provider.Prompts, tool-call payloads, and model responses generated during Workmate execution; per-request token-usage metadata for billing.

AI processing. Depending on the runtime and feature used, AI providers receive prompts, conversation context, tool inputs and results, and relevant file content. Hosted agent services also process workspace files and generated outputs. For inference routed through OpenRouter, OpenRouter forwards requests to models running on AWS Bedrock; AWS Bedrock is the inference provider. Direct OpenAI, Anthropic, and enabled Gemini features use the separate processing paths described above. Provider retention and model-training terms depend on the applicable service and agreement; a restriction on model training does not mean that data is never retained.

Web Search & Browsing

ProviderPurposeData Processed
ParallelWeb search for Workmates through the Parallel Search API, returning ranked sources and excerpts for agent responses.Search queries and objectives, which may include customer-derived information; returned search results, including source URLs, titles, publication dates, and excerpts; and search-request identifiers and usage metadata.
Browser UseAgent web browsing for Workmates when browser capabilities are used.Browser task instructions, visited page content, and browser interaction data, which may include Customer Data used in the browsing task; cookies and session credentials stored in browser profiles to maintain authenticated sessions for sites a team connects.

Authentication & Third-Party Access

ProviderPurposeData Processed
Google LLC (Google OAuth)Sign in with Google through Google OAuth, when selected by the user.Google account identifiers, names, email addresses, profile images, and authentication tokens used for sign-in.
Microsoft Corporation (Microsoft OAuth)Sign in with Microsoft through Microsoft OAuth, when selected by the user.Microsoft account identifiers, names, email addresses, and authentication tokens used for sign-in.
Slack Technologies, LLC (Slack OAuth)Sign in with Slack through Slack OAuth, when selected by the user.Slack account and workspace identifiers, names, email addresses, profile images, and authentication tokens used for sign-in.
Clerk, Inc.User authentication, session management, and team/organization membership.Email addresses, names, profile images, sign-in credentials, OAuth tokens, IP addresses, and device metadata.
Pipedream, Inc. (Pipedream Connect)Optional brokered OAuth and API connectivity for 3,000+ third-party SaaS integrations (e.g. Notion, Linear, Figma, GitHub) when a user explicitly connects an account to a Workmate.OAuth credentials for connected accounts and the request/response payloads exchanged with the third-party service on the user's behalf.

Communication & Email Delivery

ProviderPurposeData Processed
Customer.ioTransactional email delivery, newsletter subscriptions, lead nurturing, and campaign communications, including product and billing notifications.Names, email addresses, company and company-size information, subscription preferences, lead and campaign events, marketing attribution, and the content of messages Workmate sends.
AgentMail, Inc.Optional hosted agent inboxes and inbound and outbound email delivery for Workmates.Sender and recipient email addresses, inbound and outbound email subjects and bodies, attachments, inbox and thread identifiers, and delivery metadata.

Payment Processing

ProviderPurposeData Processed
Stripe, Inc.Payment processing, subscription billing, and credit top-up transactions (Account Information only).Cardholder name, billing address, last four digits of payment card, subscription status, and transaction history. Full payment card numbers are submitted directly to Stripe and are not stored by Workmate.

Analytics & Observability

ProviderPurposeData Processed
PostHog, Inc.Product and website analytics, user profiles, marketing attribution, and session replay to understand how users navigate and engage with Workmate.User identifiers, names, email addresses, company and team/profile attributes, page URLs, feature-engagement events, marketing attribution, device and browser metadata, and IP-derived geolocation. Where session recording is enabled, recordings may include visible page content and non-password input values; password inputs are masked.
Vercel Inc. (Vercel Analytics)Aggregated, privacy-preserving web traffic and performance analytics for the Workmate web application.Aggregated page views, performance metrics, and referrer information. Vercel Analytics does not use cookies and does not collect personally identifying information.
Better Stack (Logtail)Application log aggregation, error monitoring, tracing, alerting, and incident triage.Structured application logs, request metadata, service events, error details and stack traces, tracing data, and operational metrics. Diagnostic data may include customer identifiers or content present in logged events and errors; redaction varies by code path.

Customer-Connected Services

Customer-connected services, including Google Workspace, Microsoft 365, Slack, and services reached through Pipedream, receive data when an enabled integration reads, writes, or exchanges it within the permissions granted by the user or organization. These services are disclosed separately from Workmate's platform Sub-Processors because they may operate under the customer's own agreements; listing them here does not mean every connected service acts as Workmate's sub-processor in every context.

ProviderPurposeData Processed
Google LLC (Google APIs)OAuth-based access to Google Workspace services (Gmail, Drive, Calendar) when a user explicitly connects their Google account to a Workmate. Workmate's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Google Workspace APIs are not used to develop, improve, or train generalized or non-personalized AI / ML models.Google account identity, OAuth access and refresh tokens, and the Google Workspace content the user explicitly directs the Workmate to read or write.
Microsoft Corporation (Microsoft 365)Connected Outlook mail, Microsoft Teams communication, and SharePoint document access through Microsoft Graph, according to the permissions granted by the user or organization.Account and tenant identifiers, OAuth credentials, email messages and attachments, Teams conversations and shared files, and SharePoint documents and metadata accessed or exchanged through enabled integrations.
Slack Technologies, LLCDelivery surface for the Workmate Slack app. When a workspace installs Workmate, Slack relays events, messages, and file references between the user's workspace and Workmate.Slack workspace, channel and user identifiers; message content in channels and DMs where a Workmate is invited; files shared with a Workmate; OAuth tokens issued during install.

Processing Locations

Processing locations depend on the service, account configuration, and applicable agreement. A provider's headquarters does not establish where Customer Data is processed, and this list is not a commitment to a single processing region. Contact support@workclaw.com for processing-location details for the services used by your organization.

Affiliates

Workmate may also engage its corporate affiliates (entities under common control with Workmate Labs, Inc.) as Sub-Processors. Any such affiliate is bound by the same data-protection terms that apply to the third-party Sub-Processors listed above.

Changes to This List

We may update this list from time to time as our services evolve. When we add a new Sub-Processor that will process Customer Data, we will update this page and, where required by contract or applicable law, provide advance notice to affected customers so they have an opportunity to object before the new Sub-Processor begins processing.

Contact

Questions about our Sub-Processors, our Data Processing Addendum, or how Workmate protects Customer Data?