If you are deploying Klorn for other people, you are the controller and Klorn is your processor. A data processing agreement is available — and so is the list of everyone the data actually touches, which is the part most subprocessor pages bury.
Email k0820086@gmail.com with your organisation name and the entity that will sign. Klorn is a solo-maintained product, so this is a real exchange with a person rather than a click-through — which also means we can work from your paper if you have a standard form.
Everyone below can, in the course of running the hosted service, process data you put into Klorn. Self-hosting removes every row except the model provider you choose and Google.
| Subprocessor | What it does | What it sees |
|---|---|---|
| Gmail and Calendar APIs, and sign-in | The source of the data — your mailbox and calendar, under the scopes you granted | |
| Render | API hosting, Singapore region | Everything the API processes, in transit and in memory |
| Supabase | Managed Postgres, Seoul (ap-northeast-2) | All stored account, mail and classification data |
| Vercel | Web app hosting | Requests and responses in transit |
| Google (Gemini API) | Model calls | The message text sent for classification or drafting, under API terms that exclude training on submitted data |
| OpenRouter | Model routing | The same, for models reached through it. Bring your own key and this row becomes your chosen provider instead |
| Paddle | Payments and merchant of record | Billing details. No mail content |
| Apple | Push notification delivery (APNs) | Notification payloads on the devices you registered |
Klorn does not sell data, does not use your mail to train models, and does not run third-party analytics or trackers — retention instrumentation is a short allowlist of coarse event names in Klorn's own database, never message content. That is enforced in analytics.ts, not just asserted here.
Stated plainly. Klorn has no SOC 2 report and no third-party audit. If your procurement process requires one, Klorn does not currently clear it, and we would rather you learn that on this page than three calls in. What is available instead is the whole source under AGPL-3.0 and the security page naming the files that enforce each claim.