Providers that may process Reddi customer, client or operational data when the relevant product capability is enabled.
Reddi uses infrastructure and service providers to run the product, deliver emails, process billing, monitor reliability and support optional AI-assisted workflows. Not every provider is used for every workspace or every feature.
| Provider | Purpose | Data category | Region/data location if known | Use |
|---|---|---|---|---|
| Supabase | Database, authentication and private file storage | Firm/user metadata, client metadata, request data, files, audit logs | Project-region dependent; production configuration controls the region | Core infrastructure provider |
| WorkOS | Staff identity, Google/Microsoft sign-in and firm SSO where enabled | Staff user identity, email, organization and authentication event metadata | Provider/account configuration dependent | Identity provider where enabled |
| Vercel | Application hosting and delivery | App traffic, request metadata, logs and runtime telemetry | Deployment-region and function configuration dependent | Core infrastructure provider |
| Resend | Transactional email and reminders | Recipient email, message metadata and reminder/request copy | Provider/account configuration dependent | Email delivery provider where enabled |
| Stripe | Billing and subscription management | Billing contact, customer id, subscription id, invoice/payment metadata | Provider/account configuration dependent | Billing provider where paid plans are enabled |
| Mistral | Optional OCR, document extraction, classification and summary support | Uploaded file content, operational context and extracted snippets where AI/document extraction is enabled | Provider/account configuration dependent | AI/OCR provider where enabled |
| OpenAI | Optional AI-assisted review, structured output and safety evaluation support | Operational context and extracted snippets where AI assistance is enabled | Provider/account configuration dependent | AI provider where enabled |
| Cloudmersive or scanner adapter | Malware scanning and file safety checks | Uploaded file bytes or scanner fixture payloads | Provider/account configuration dependent | File-safety provider where enabled |
| Sentry | Error monitoring and observability | Redacted error/event metadata, environment, route/runtime context | Provider/account configuration dependent | Monitoring provider where enabled |
| PostHog or analytics provider | Product analytics where enabled | Usage metadata, event counts, route/workflow analytics | Host configured by environment | Analytics provider where enabled |
| Inbound email provider / forwarding service | Inbound client reply and attachment routing | Forwarded email metadata, attachments and recipient address | Provider/account configuration dependent | Inbound email provider where enabled |
Data location depends on the configured deployment, Supabase project region, provider account settings and the feature used. Reddi does not claim a specific residency outcome unless it is stated in a customer order form or written agreement.
Reddi may update this list when providers, product features, infrastructure or account configuration changes. Questions about provider use can be sent to support@askreddi.com.
