Subprocessors
Infrastructure and service providers used to operate FileDigest document preparation, billing, storage, processing, email, monitoring, and analytics.
FileDigest uses a small infrastructure stack to operate the product. These providers process data only as needed to provide the service.
Last updated: April 29, 2026.
Core providers
| Provider | Purpose | Data involved |
|---|---|---|
| Vercel | Web app hosting, serverless routes, analytics, deployment logs | Account/session metadata, request logs, public-site analytics |
| Supabase | Authentication, Postgres metadata, private object storage | Account metadata, job metadata, uploaded files, generated outputs |
| Modal | Document-processing engine | File contents during processing and generated extraction output |
| Stripe | Subscriptions, checkout, billing portal, invoices | Billing/customer metadata, payment status, invoices |
| Resend | Transactional email | Recipient email address and email content |
| Sentry | Error monitoring and release diagnostics | Error traces, environment metadata, non-sensitive operational context |
Data categories
Depending on the workflow, subprocessors may process account metadata, billing metadata, job metadata, operational logs, uploaded source files, and generated outputs. FileDigest aims to keep document access scoped to the services required to process, store, monitor, bill, and deliver the product.
Regions
The current production stack is configured in European regions where available. Some providers may process operational metadata in their standard global infrastructure. Contact support for region, DPA, or enterprise procurement questions.
Contact
For subprocessor, DPA, or deletion questions, contact support@filedigest.app.