Draft. This page describes how Sewpress really works today, but it hasn't had a lawyer's review yet. Questions: write to us at the address at the bottom.
Sub-processors
These companies run parts of Sewpress for us. Each one handles only what it needs to. We'll update this list, and email business customers, 30 days before adding anyone.
| Company | What for | What it handles | Where |
|---|---|---|---|
| Neon (Databricks) | Database | Account, patterns, release settings, build reports, credits, activity log | EU (Frankfurt, AWS eu-central-1) |
| Cloudflare R2 | File storage | Master files (until deleted), built PDFs and preview images | EU jurisdiction bucket |
| Trigger.dev | Runs the build engine | Master files and built PDFs while a job runs; nothing is kept after | To be confirmed |
| Stripe | Payments and invoices | Name, email, billing address, payment details (we never see card numbers) | EU (Ireland) and United States |
| Resend | Sign-in links and “files ready” emails | Email address, email content | United States |
| Optional “Sign in with Google” | Name, email, profile picture, only if you choose it | United States |
Questions: hello@sewpress.com
Last updated 31 October 2026.