Trust
Sub-processors
- Effective:
- Last updated:
1. Purpose, scope and provider roles
This page identifies the external providers and customer-connected source platforms used by the Worql service. It supplements our Privacy Policy and Data Processing Addendum.
A service provider Worql uses to process customer information on its behalf may be a sub-processor under an applicable DPA. A platform connected by the customer (such as GitHub, Jira or Slack) may instead be that customer's independent provider, and its role depends on the data flow and contract. Listing a provider does not establish that every provider has the same legal role, hosting location or data-processing agreement.
2. Service providers used by Worql
| Provider | Function | Categories of customer data potentially processed | Processing location |
|---|---|---|---|
| Clerk | Identity, OAuth sign-in, session management | Name, email, account identifiers, provider claims | Provider-managed; check contractual region terms |
| Stripe | Subscriptions, checkout and billing portal | Billing contact, payment and subscription metadata; Stripe holds payment details | Provider-managed; check contractual region terms |
| Anthropic (Claude API) | Assisted SoW assembly, document interpretation, commercial evidence assessment and advisory analysis | Customer prompts and briefs, submitted SoWs and contracts, connected-source text, some repository content and diffs, change-request text and acceptance criteria | API provider-managed; no region restriction established in the application |
| Voyage AI | Embeddings for matching evidence to acceptance criteria | Acceptance criteria, milestone descriptions and evidence text, including selected Jira, Slack and GitHub-derived text | API provider-managed; no region restriction established in the application |
| Neon | Hosted PostgreSQL | Account, engagement and other application data | Configured primary database: AWS us-east-1 |
| Upstash | Redis rate limits and ephemeral state | Rate-limit identifiers and counters | Configured application region: AWS us-east-1 |
| Resend | Transactional mail and, when enabled, inbound engagement mail | Sender/recipient addresses, message body, headers, attachment-related data | Provider-managed; inbound region not independently established |
| Vercel | Application hosting, request logs, cookieless analytics, private Vercel Blob storage | Request metadata, transiting customer data and privately stored source documents, compliance attachments or email files | Hosting and Blob locations depend on the deployed configuration |
Anthropic receives connected-source or submitted-document material only when a feature calls its API. Voyage AI can receive criterion and evidence text for similarity calculations. Worql does not itself use those calls to authorize a scope change, accept work or move money. Contractual retention, training and residency restrictions must be verified against the provider agreement; an application integration alone is not evidence of a zero-retention or United States-only commitment.
3. Customer-connected platforms and conditional sources
These systems are separate from the hosted providers above. A customer authorizes access to them through an app installation or source credentials. Some integrations also send limited engagement evidence back to the source platform.
| Platform | When connected | Information Worql reads or sends |
|---|---|---|
| GitHub | Authorized GitHub App installation and repository binding | Source files, PR diffs and metadata, issues, commits and contributor identities; Worql may publish a check result or link back under the granted app permissions |
| Atlassian Jira and Confluence | Forge app installed and linked by authorized administrators, or Jira API-token connection | Issue fields and changes, titles, descriptions, acceptance criteria, account identifiers, referenced tickets and requested Confluence page text; selected delivery results can be displayed in Jira |
| Slack | Worql Slack app, selected engagement channel and required party consents | Messages, edits/deletions, author IDs, reactions, threading context and shared-file metadata; message text can be processed by evidence-matching systems |
| Linear | Customer-authorized API-token integration, where configured | Referenced ticket identifier, title, status, description and assignee information |
| Inbound engagement email | Per-engagement address enabled and Resend receiving configured | Sender/recipient information, subject, body, headers and attachments; stored via the email and application-storage providers above |
Customer-connected platform privacy notices and processing contracts may also apply. Uninstalling or disconnecting one of these integrations stops authorized future collection through it; previously recorded commercial evidence, consent events and relevant audit history are not automatically erased. For deletion requests, see the Privacy Policy.
4. Notice, objections and historical disclosure correction
Under the DPA and the published sub-processor notice practice, customers on covered plans are entitled to at least 30 days' advance notice of new or replacement sub-processors and an opportunity to object.
Correction published October 20, 2026: Earlier public lists did not fully describe the Jira/Confluence, Slack, inbound email, Voyage AI and expanded Anthropic processing paths. Some of those integrations and embeddings were used before this correction. Publishing their names now does not mean an earlier 30-day notice was sent. We are preserving the customer's rights under applicable contracts, including objections and available remedies; affected customers may request the historical details by emailing privacy@worql.app.
For future additions or replacements, Worql must use the contractual advance-notice procedure, including notification to the relevant billing contacts where required, before making the change effective. A public version-date change alone is not proof that the notice was delivered.
5. Historical versions and contact
Prior public versions can be requested for audit or contract review. Contact legal@worql.app to request the version applicable to a past date. For processing location, an executed DPA, a sub-processor objection or a data-subject request, contact privacy@worql.app.