Subprocessors
Last updated 16 October 2026
These are the third parties that process customer data on our behalf, what each one does, and where it runs. This list is generated from the providers the application is actually configured to talk to, and an automated test fails the build if the two ever disagree — so it cannot quietly go stale.
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Neon | Managed PostgreSQL. Holds every workspace record. | All customer data except uploaded files. | Singapore |
| Amazon Web Services (S3) | Private object storage for files attached to records. | Uploaded files and their metadata. | ap-southeast-1 (Singapore) |
| Amazon Web Services (SES) | Transactional email delivery, and bounce and complaint feedback. | Recipient address, subject and message body. | us-east-1 (United States) |
| DigitalOcean | Application hosting. | Data in transit and in application memory; request logs. | Singapore |
| Stripe | Subscription billing and payment processing. | Billing contact and payment details. Card numbers never reach kitset.io. | United States and Ireland |
| Cloudflare (Turnstile) | Telling people from scripts on the sign-in, sign-up and password-reset forms. | The visitor's IP address and browser signals on those forms. No workspace data. | Global network |
What this list does not include
Tools we use to run the company that never receive your workspace data — source control, our own email, accounting — are not subprocessors of yours and are not listed.
Notice of changes
We will update this page before a new subprocessor begins processing customer data, and notify workspace Owners by email at least 30 days in advance. If you have a reasonable objection on data protection grounds, tell us at [email protected] within that period and we will work with you to resolve it; if we cannot, you may terminate the affected subscription and receive a pro-rata refund for the unused term.
How they are engaged
Each provider is engaged under a written contract requiring it to process data only on our instructions, to keep it confidential, and to apply appropriate security. Where a provider is outside the jurisdiction the data originates from, transfers rely on that provider's standard contractual clauses.
Related
What is not on this page
If you register a webhook endpoint through the Developer API, kitset.io sends data to a server you nominated. That destination is not a subprocessor and is not listed here: a subprocessor is a party we choose to perform part of the service on our behalf, and we are answerable for it. A webhook destination is a party you choose, receiving data on your own instruction. We give no notice before you add one, because you are the one adding it, and what happens to data after it arrives is between you and its operator. The data processing addendum sets the distinction out in full.