Legal
Subprocessors
Last updated 2026-11-03 · CS Cloud Ltd
These are the third parties that process personal data on our behalf in providing QueuePower. We give workspace administrators at least 30 days’ notice before adding or replacing one, as set out in the Data processing agreement. To receive those notices at an additional address, write to privacy@queuepower.com.
1. Core subprocessors
Engaged for every workspace.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Vercel Inc. | Application hosting, edge network, scheduled jobs | All application traffic in transit; server logs with PII redacted | United Kingdom (London region). Edge caching of public pages may occur worldwide; customer data is not cached |
| Neon Inc. | Managed PostgreSQL database | All tenant data at rest, with customer email addresses and stored credentials encrypted at the application layer before write | United Kingdom (AWS London, eu-west-2) |
| Clerk Inc. | Authentication, session management, organisation membership | Your team members' names, email addresses, and sign-in metadata. Never your customers' data | United States |
| Stripe Inc. | Subscription billing and payment processing | Billing contact, company name, invoices. Card details are held by Stripe and never touch our systems | United States and European Union |
| Anthropic PBC | Large-language-model inference for ticket triage, drafting, and analysis | Ticket content with names and email addresses replaced by placeholders before transmission. Not used to train models | United States |
| OpenAI, L.L.C. | Text matching (embeddings) that finds a workspace's own related knowledge base articles and past tickets | Ticket text and resolution notes with names and email addresses replaced by placeholders, and public knowledge base article text. Kept by the provider for up to 30 days for abuse monitoring only, then deleted. Not used to train models | United States |
| Resend Inc. | Transactional email (billing alerts, rating requests, platform notices) and, for workspaces with no connected mailbox, replies to their customers | Recipient email address and message body for each email we send | United States |
2. Connected on your instruction
These process data only when a workspace administrator connects the service, and do so under your own agreement with that provider rather than ours. Listed for completeness.
| Provider | Purpose | Data | Location |
|---|---|---|---|
| Microsoft Corporation (Microsoft 365) | Inbound and outbound support email when a tenant connects a Microsoft 365 mailbox | Mail in the connected mailbox, under the tenant's own Microsoft agreement | Per the tenant's Microsoft 365 tenancy |
| Google LLC (Google Workspace) | Inbound and outbound support email when a tenant connects a Gmail / Workspace mailbox | Mail in the connected mailbox, under the tenant's own Google agreement | Per the tenant's Google Workspace tenancy |
| Slack Technologies, LLC and Microsoft Corporation (Microsoft Teams) | Notifications to a channel the workspace connects | The ticket subject and customer name carried in each notification | Per the workspace's own agreement |
| Zendesk, HubSpot, ServiceNow, Halo, or a webhook endpoint of the workspace's choosing | Escalation of tickets that need the workspace's own help desk or CRM, when a workspace connects one | The customer's name and email address, their message, the ticket category, an AI-written summary of the conversation and a list of attachments (type and size, not the files), for escalated tickets only | Per the workspace's own agreement |
3. A note on AI processing
Ticket content sent to Anthropic for AI processing, and to OpenAI for text matching, has customer names and email addresses replaced with placeholders before transmission. Neither uses content submitted through its API to train models. No other subprocessor receives ticket content for AI processing.