WorkClaw Sub-Processors
Last updated: May 28, 2026
Workmate Labs, Inc. (“WorkClaw”) engages a small number of trusted third-party service providers (“Sub-Processors”) to help deliver the WorkClaw Platform. Each Sub-Processor listed below may process Customer Data on WorkClaw's behalf in connection with the services it provides.
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 WorkClaw's commitments to its customers.
This page is the authoritative list of WorkClaw 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
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| 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). | All Customer Data at rest, including team and user records, claw configurations, message history, uploaded files, and credentials. | United States (us-east-1, N. Virginia) |
| Vercel Inc. | Hosting and edge delivery of the WorkClaw web application, marketing site, and serverless functions. | HTTP request metadata, application traffic, and content served to end users. | United States |
AI & Large Language Model Providers
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Anthropic, PBC | Large language model inference for in-product AI assistance, including message filtering, intent classification, and setup flows. | Customer prompts and context (messages, file excerpts, configuration) submitted for inference. Anthropic does not retain inputs or outputs for training on the API tier WorkClaw uses. | United States |
| OpenRouter, Inc. | Routing layer for large language model inference across multiple model providers, used for agent ("claw") execution and credit-based metering of usage. | Prompts, tool-call payloads, and model responses generated during claw execution; per-request token-usage metadata for billing. | United States |
Important note on AI processing. When a user interacts with a claw, the content of that interaction (the user's prompt, surrounding context, and any tool inputs) is transmitted to the LLM provider listed above to generate a response. WorkClaw uses only API tiers under which providers contractually agree not to train their models on Customer Data. Customer Data is not used to train any WorkClaw model.
Authentication & Third-Party Access
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| 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. | United States |
| Google LLC (Google APIs) | OAuth-based access to Google Workspace services (Gmail, Drive, Calendar) when a user explicitly connects their Google account to a claw. WorkClaw'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 claw to read or write. | United States |
| Pipedream, Inc. (Pipedream Connect) | 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 claw. | OAuth credentials for connected accounts and the request/response payloads exchanged with the third-party service on the user's behalf. | United States |
Communication & Email Delivery
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Slack Technologies, LLC | Delivery surface for the WorkClaw Slack app. When a workspace installs WorkClaw, Slack relays events, messages, and file references between the user's workspace and WorkClaw. | Slack workspace, channel and user identifiers; message content in channels and DMs where a claw is invited; files shared with a claw; OAuth tokens issued during install. | United States |
| Customer.io | Transactional email delivery for product notifications (contact-form replies, billing notifications, credit top-up confirmations). | Recipient names, email addresses, and the content of transactional messages WorkClaw sends. | United States |
| AgentMail, Inc. | Outbound email delivery for emails composed and sent by a claw on behalf of a user. | Sender and recipient email addresses, email subject and body content generated by a claw, and delivery metadata. | United States |
Payment Processing
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing, subscription billing, and credit top-up transactions. | 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 WorkClaw. | United States |
Analytics & Observability
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| PostHog, Inc. | Product analytics — understanding how users navigate and engage with the WorkClaw Platform. | Pseudonymous user identifiers, page views, feature-engagement events, device and browser metadata, and IP-derived geolocation. | United States |
| Vercel Inc. (Vercel Analytics) | Aggregated, privacy-preserving web traffic and performance analytics for the WorkClaw web application. | Aggregated page views, performance metrics, and referrer information. Vercel Analytics does not use cookies and does not collect personally identifying information. | United States |
| Better Stack (Logtail) | Application log aggregation, alerting, and incident triage. | Structured application logs, including request metadata, service events, error traces, and operational metrics. Logs are scrubbed of customer message content before egress. | United States / European Union (region-configurable) |
Affiliates
WorkClaw 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 WorkClaw protects Customer Data?
- Email support@workclaw.com
- See our Privacy Policy and Security overview for additional detail.