Subprocessors
The outside services that can receive company data from Qwrki, what each one receives, and who chose it. This list is the same register Qwrki admins see on the Connected data page, so the two always agree.
Where company data goes
| Processor | Chosen by | Company data it receives | Why | Where it runs |
|---|---|---|---|---|
| WooCommerce (the tenant's own store) | The company, if it connects the integration | Orders and revenue figures from the store address the tenant names; Order notes, statuses and refunds the tenant approves an AI Employee to write to the store | Store revenue sync and approved order writes. | Not published yet |
| WordPress (the tenant's own site) | The company, if it connects the integration | Site content counts, and articles the tenant chooses to publish | Content counts sync and article publishing. | Not published yet |
| Klaviyo | The company, if it connects the integration | Marketing metric aggregates | Email and message performance sync. | Not published yet |
| Stripe (the tenant's own account) | The company, if it connects the integration | Card payment figures the tenant's account reports; Customers' names, email addresses and phone numbers, when an admin imports them; Invoice number, amount and currency, when a customer pays an invoice by card (Pay now) | Card payments sync, customer import and Pay now card payments. | Not published yet |
| Xero | The company, if it connects the integration | Accounting reports and the organisation scopes the grant carries | Profit and loss sync and the organisation picker. | Not published yet |
| HubSpot | The company, if it connects the integration | CRM record counts | CRM dashboard sync. | Not published yet |
| Shopify | The company, if it connects the integration | Orders and the store address | Order and revenue sync. | Not published yet |
| The company, if it connects the integration | Analytics, Search Console and advertising figures for the company account; Mailbox and drive content, but only for a member's own private Google row | Marketing performance sync, and a member's own Google account where they connect one. | Not published yet | |
| Meta | The company, if it connects the integration | Advertising account performance figures | Advertising sync. | Not published yet |
| Slack | The company, if it connects the integration | Chat events the workspace delivers to the tenant's install | Workspace chat connection. | Not published yet |
| Discord | The company, if it connects the integration | Chat events the guild delivers to the tenant's install | Community chat connection. | Not published yet |
| Meta Platforms (Messenger) | The company, if it connects the integration | Messenger messages customers send to the company's Page and the replies; The customer's Page-scoped id | Messenger chat for a company's Page. | Not published yet |
| Telegram | The company, if it connects the integration | Chat messages the tenant's bot receives and sends | Chat channel for a company. | Not published yet |
| Slack, Discord, Microsoft Teams or Google Chat (whichever service the pasted webhook URL belongs to) | The company, if it connects the integration | Usage warning titles and snippets, integration alert titles and snippets and website chat handoff case links while the tenant has a single company, as the tenant already sees them in Qwrki | Posts usage warnings, and content decay alerts, integration alerts and counts of the business events you turn on only while your organisation has a single company; each website chat handoff you turn on also posts with a link to its case; never a person's name or message text, and never an alert about a member's private connection, to the pasted incoming webhook. A notifications webhook is connected | Not published yet |
| Meta Platforms (WhatsApp), carried by Telnyx | The company, if it connects the integration | Chat messages the company's WhatsApp number receives and sends, and the WhatsApp number itself | WhatsApp channel for a company's phone number. | Not published yet |
| GitHub | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Stripe | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Notion | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| TinyFish | The company, if it connects the integration | Search queries and page addresses the company's AI employees send through the TinyFish server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Linear | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Intercom | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| monday.com | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Atlassian | The company, if it connects the integration | Tool arguments the company's AI employees send through the connected server, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| WPVibe | The company, if it connects the integration | What the company's AI employees ask of its WordPress sites through the WPVibe relay, and the results it returns | Outside tools the company's AI employees can call once a company connects them. Only when a company connects the server from the Qwrki catalogue. | Not published yet |
| Resend | Qwrki | Recipient addresses, subjects and message bodies the tenant's workflows queue | Outbound mail. | Not published yet |
| Stripe | Qwrki | Billing contact, subscription and payment metadata for the tenant's own plan | Subscription billing. | Not published yet |
| Cloudflare | Qwrki | AI feature prompts and drafts, with gateway logging of prompts disabled in code; Voice audio and synthesis text, when Cloudflare speech is selected; Form attestation tokens for bot protection | AI features, voice features and bot protection. | Not published yet |
| Anthropic | Qwrki | AI feature prompts and drafts, sent through the Cloudflare AI gateway | AI model provider for AI features. Only when the model table routes an AI job to one of this provider's models. | Not published yet |
| OpenAI | Qwrki | AI feature prompts and drafts, sent through the Cloudflare AI gateway | AI model provider for AI features. Only when the model table routes an AI job to one of this provider's models. | Not published yet |
| Qwrki | AI feature prompts and drafts, sent through the Cloudflare AI gateway | AI model provider for AI features. Only when the model table routes an AI job to one of this provider's models. | Not published yet | |
| Cloudflare R2 | Qwrki | Files the company uploads, stored under the company's own key prefix; Nightly database backup copies, which hold all company data, once the backup service is deployed | File storage and database backups. | Not published yet |
| Telnyx | Qwrki | Voice audio and synthesis text | Voice features by the alternative speech route. Selected for live-call speech at launch (Conversation Relay). | Not published yet |
| DataForSEO | Qwrki | Keywords and domains the tenant asks to research | SEO research data, under the platform's shared credential. | Not published yet |
| Sentry | Qwrki | Scrubbed error events, with secrets and tokens stripped in code before sending | Error observability for the cell's own project. Only when the error reporting DSN is set. | Not published yet |
| Railway | Qwrki | All company data the product stores, in the application database, and everything the application handles while it runs | Application and database hosting. | United States (us-west2) |
| Groq | Qwrki | AI feature prompts and drafts | AI features, as an outside model host. Only when the company switches on outside AI providers and Qwrki has opened this host for that feature after its evaluation. No feature uses it today. | Not published yet |
| Cerebras | Qwrki | AI feature prompts and drafts | AI features, as an outside model host. Only when the company switches on outside AI providers and Qwrki has opened this host for that feature after its evaluation. No feature uses it today. | Not published yet |
Where a processor's location is shown, it is the location Qwrki has confirmed. Rows that say Not published yet are still being confirmed.
How Qwrki handles personal data is in the privacy policy.