Sub-processors
Last updated: June 5, 2026
Quillon uses the following sub-processors to provide the service. Quillon will give at least 30 days' notice before engaging a new sub-processor.
| Sub-processor | Purpose | Region |
|---|---|---|
| Hetzner | Application, database, and background-job hosting (compute, Postgres, Redis) | United States (Ashburn, Virginia) |
| Cloudflare | DNS, marketing site (Pages), edge, email routing, encrypted off-site database backups (R2) | Global |
| Stripe | Payment processing | US / Global |
| Anthropic | Large-language-model analysis of customer signal data | US |
| Resend | Transactional email delivery | US |
Read-only integrations you connect
These are systems you already operate. Quillon reads from your own account using credentials you provide — you remain the controller of that relationship. They are listed here for transparency, not because Quillon sub-processes your data through them.
| Integration | What Quillon reads | Region |
|---|---|---|
| Mixpanel | Quillon reads per-user event counts and last-event time from your own Mixpanel project to compute churn-risk signals (read-only; no event content transferred) | United States (or EU / India per your project residency setting) |
| Close | Quillon reads contact, opportunity, and activity metadata from your own Close CRM account to enrich customer health (read-only; no write-back to Close, and no email or call content is read) | United States |
Any additional read-only integrations will appear in the table above as they ship — you remain the controller of any system you connect.