Subprocessors
510sec · Last updated 2026-09-22
The third parties that process data on our behalf. We keep this list short on purpose, and we update it before adding a new one.
| Subprocessor | Purpose | Data it can see | Location |
|---|---|---|---|
| Amazon Web Services | Application hosting and storage | All service data at rest and in transit | USA (us-east-2) |
| Square | Payment processing | Buyer email, amount, card details (entered directly with Square — never with us) | USA |
| Email delivery provider | Verification codes and receipts | Recipient address and message content | USA |
| Google (only if you sign in with Google) | Identity verification | Your email address and name from your Google profile | USA |
Optional AI providers
Document generation uses no AI provider. The optional prose-polish feature defaults to a local model, in which case no third party is involved at all. If an administrator of your instance explicitly enables a cloud model, threat-description text — not your full specification, and never source code — is sent to the selected provider:
| Provider | When |
|---|---|
| Anthropic | Only when explicitly selected as the polish backend |
| OpenAI | Only when explicitly selected as the polish backend |
Changes
We will update this page before a new subprocessor begins handling customer data. If you need advance written notice of changes, ask us for it in your agreement.