Legal
Subprocessors
The service providers that process personal data for KazoCode, what each one does and what data it handles.
Updated November 20, 2026
These companies process personal data on our behalf to run the Services. Each is bound by a contract that limits its use of the data to providing its service to us, and requires appropriate security. The Privacy Policy explains what we collect.
Infrastructure
| Provider | What it does | Data it handles |
|---|---|---|
| Neon | Hosts our Postgres database | All account data in our database: account, sessions, devices, synced settings, usage, teams, marketplace records |
| Render | Runs the account server (api.kazocode.app) | All data passing through the account server, and its request logs |
| Cloudflare | Hosts and protects kazocode.app | IP addresses and request details for the website |
| Resend | Sends account emails | Your email address and the content of account emails |
Sign-in and marketplace
| Provider | What it does | Data it handles |
|---|---|---|
| GitHub | Sign in with GitHub, and hosting of marketplace add-on repositories | Sign-in requests and the tokens GitHub issues |
| Sign in with Google | Sign-in requests and the tokens Google issues |
GitHub and Google act as independent controllers for the accounts you hold with them.
Model providers
KazoCode models are run by the model providers we route them to. Before we make a KazoCode model available, we add its provider to this page. Each one may process the prompts, context and responses of requests to its models, and must not train on them.
Changes
We'll update this page before a new subprocessor starts handling personal data. Team owners who want notice of changes, or who want to object to one, can email [email protected].
Updated November 20, 2026