To deliver Parker, we rely on a small set of trusted third-party service providers ("sub-processors") that may process customer content or personal data on our behalf. This page lists who they are, what they do, and where they operate. We keep the list current and vet every provider before we bring them on.
What is a sub-processor?
A sub-processor is a third party we engage to help provide the Services — for example, cloud hosting or AI model inference — that may process data your firm submits to Parker. Every sub-processor is bound by contract to protect that data, use it only to provide their service to us, and meet security and confidentiality standards consistent with our own commitments in the Privacy Policy and Security pages.
Current sub-processors
We do not allow any sub-processor to train AI models on your customer content. Content sent to AI providers for inference is processed to complete your task only, and is not retained by them for model training.
| Sub-processor | Purpose | Location |
|---|---|---|
| Amazon Web Services | Cloud infrastructure — each firm's dedicated instance, encrypted storage, and AI model inference via Amazon Bedrock | United States |
| Render | Application hosting and managed PostgreSQL database for the Parker control plane | United States |
| WorkOS | Authentication — email sign-in codes, sessions, and workspace membership | United States |
| OpenRouter | AI model inference (routing to frontier LLMs) under a zero-data-retention, no-training agreement | United States |
| Anthropic | AI model inference (Claude) under a no-training agreement | United States |
| AgentMail | Inbound and outbound email processing for each firm's dedicated Parker inbox | United States |
| HighLevel (LeadConnector) | Demo scheduling, CRM, and support communications on our marketing site | United States |
A more detailed list, including entity details and Data Processing Addenda, is available to customers on request at [email protected].
A note on integrations
Tools you choose to connect to Parker — such as Clio, Google Workspace, and Slack — are not sub-processors. They are services you control and authorize. Parker accesses only the data and scopes you grant, and only to perform the tasks you direct. Your use of those tools is governed by their own terms and privacy policies.
How we vet sub-processors
- We assess each provider's security, privacy, and compliance posture before engaging them.
- We sign data processing agreements that bind them to protect your data and limit its use.
- We grant each provider only the access needed to perform its function.
- We review our sub-processors periodically to confirm they continue to meet our standards.
Changes & notification
As Parker evolves, our list of sub-processors may change. When we add or replace a sub-processor that handles customer content, we will update this page and, where required by your customer agreement, provide advance notice so you have the opportunity to review the change. To be notified of updates, email [email protected] and ask to be added to our sub-processor notification list.
Questions
For questions about our sub-processors, data processing, or to request a DPA, contact [email protected].