Effective 15 September 2026
Subprocessors
The complete list of third parties that process data on KesherSuite's behalf. This page is updated before a new subprocessor is engaged, and account holders are notified by email.
A subprocessor is a third-party service that processes data on my behalf in order to deliver KesherSuite. This page lists every one, what it receives, and where it operates. It is referenced by thePrivacy Policy and forms part of it.
Each row states its status. A service that is integrated in the codebase but not switched on in the live deployment is listed as such rather than omitted, so that the list does not become wrong on the day it is enabled.
| Provider | What it does | What it receives | Where | Status |
|---|---|---|---|---|
| Google Cloud Platform Data terms | Application hosting, database, file storage, long-term storage of the marketing site's own usage measurements, and the key management service that protects encrypted fields | All application data and uploaded files | Singapore (asia-southeast1) | Active |
| Anthropic Data terms | Large language model powering the AI builder and configurable agents | Prompts, app configuration documents, and record or file contents you explicitly direct an agent to | United States | Active |
| OpenAI Data terms | Alternative large language model provider, and image generation where used | Prompts, app configuration documents, and record or file contents you explicitly direct an agent to | United States | Active |
| Cloudflare Data terms | Bot and abuse protection on the signup form (Turnstile) | IP address and a challenge token | Global edge network | Active |
| SendGrid (Twilio) Data terms | Transactional email — address verification, password reset, security and billing notices | Email address and message content | United States | Active |
| Stripe Data terms | Payment processing and subscription billing | Billing contact details and payment information, collected by Stripe directly | United States | Not yet enabled — paid plans are not live |
| Sentry Data terms | Error and exception tracking | Error traces, which may incidentally contain user identifiers | United States | Not yet enabled |
The AI providers
Anthropic and OpenAI receive more of your content than any other subprocessor, so their terms are set out directly rather than left to a table row.
Both state in their business API terms that data submitted through those APIs is not used to train their models. Those terms are linked above. I do not use your content to train any model.
Where you prefer your AI usage to run under your own agreement with a provider, KesherSuite supports connecting your own Anthropic or OpenAI API key. Requests are then billed to your account and governed by your contract with that provider rather than mine.
Not subprocessors
Two categories are named here precisely because they appear to belong in the table and do not:
- HaveIBeenPwned is queried when you set a password, to check it against known breach corpora. No personal data reaches it. The check uses k-anonymity: only the first five hexadecimal characters of the password's SHA-1 hash are sent, a prefix matching many thousands of passwords, and the comparison completes on my server. Neither the password nor its full hash leaves the server.
- Connectors and outbound endpoints you configure — Slack, HubSpot, Xero and the rest — are not my subprocessors. Connecting one instructs KesherSuite to send data to a service you hold your own relationship with, under your own agreement with that vendor. Which services receive data, and what they receive, is determined by your configuration rather than by me.
Changes
This page is updated before a new subprocessor is engaged, and account holders are notified by email. You may object to a new subprocessor on reasonable data protection grounds. Where an objection cannot be resolved, you may cancel without penalty and the unused portion of your term is refunded.
Questions: xc.keshersuite@gmail.com