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 |
|---|---|---|---|
| WooCommerce (the tenant's own store) | The company, if it connects the integration | Orders and revenue figures from the store address the tenant names | Store revenue sync. |
| 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. |
| Klaviyo | The company, if it connects the integration | Marketing metric aggregates | Email and message performance sync. |
| 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. |
| 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. |
| HubSpot | The company, if it connects the integration | CRM record counts | CRM dashboard sync. |
| Shopify | The company, if it connects the integration | Orders and the store address | Order and revenue sync. |
| 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. | |
| Meta | The company, if it connects the integration | Advertising account performance figures | Advertising sync. |
| Slack | The company, if it connects the integration | Chat events the workspace delivers to the tenant's install | Workspace chat connection. |
| Discord | The company, if it connects the integration | Chat events the guild delivers to the tenant's install | Community chat connection. |
| Telegram | The company, if it connects the integration | Chat messages the tenant's bot receives and sends | Chat channel for a company. |
| 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 |
| 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. |
| 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. |
| 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. |
| 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. |
| Resend | Qwrki | Recipient addresses, subjects and message bodies the tenant's workflows queue | Outbound mail. |
| Stripe | Qwrki | Billing contact, subscription and payment metadata for the tenant's own plan | Subscription billing. |
| 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. |
| 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. |
| Telnyx | Qwrki | Voice audio and synthesis text | Voice features by the alternative speech route. Only when the owner selects Telnyx for speech at launch. |
| DataForSEO | Qwrki | Keywords and domains the tenant asks to research | SEO research data, under the platform's shared credential. |
| 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. |
| Railway | Qwrki | All company data the product stores, in the application database, and everything the application handles while it runs | Application and database hosting. |
The list above names who can receive company data. Qwrki has not published processor locations, their own sub-processors or contract terms here.
How Qwrki handles personal data is in the privacy policy.