Last updated July 21, 2026. Seal uses the providers below to run the service. We share only the data each one needs for its purpose, and we require appropriate safeguards for data processed outside your country.
| Provider | Purpose | Location | Data |
|---|---|---|---|
| Fly.io | API hosting and compute | United States | Service data in transit and in memory |
| Supabase (Postgres) | Primary database — approvals and audit log | United States (AWS) | Account, approval payloads, and audit events |
| Stripe | Billing and payments | United States | Customer and subscription identifiers |
| Resend | Transactional email (approval notifications) | United States | Recipient email and notification content |
| Slack | Approval delivery, for orgs that connect it | United States | Approval content delivered to connected workspaces |
| Vercel | Dashboard and marketing site hosting | United States | Request metadata for the web apps |
| Plausible | Cookieless, aggregate website analytics | European Union | Aggregate page metrics — no personal profiles |
Changes
We update this list as our infrastructure changes. If your organization needs advance notice of new subprocessors, request it with your Data Processing Agreement.
Contact
Questions about our subprocessors: hello@useseal.dev.