Subprocessor disclosure
Third-party providers that process or store data in connection with the Orinel application. This list reflects providers integrated in the application codebase. If you deploy to additional infrastructure (e.g. a specific hosting provider), that provider should be added to your own subprocessor list.
Last updated: March 2025
Providers
| Provider | Purpose | Data / location |
|---|---|---|
| Supabase | Database (PostgreSQL), authentication, session storage | Application data and auth data stored in the Supabase project. Region is determined by the Supabase project (see Supabase documentation). |
| Stripe | Payment processing, subscriptions, billing portal | Customer IDs and subscription metadata are stored in our database; payment method and transaction details are held by Stripe. Used when Stripe is configured (STRIPE_SECRET_KEY set). |
| Sentry | Error and performance monitoring (optional) | Only used when NEXT_PUBLIC_SENTRY_DSN is set. Error reports and context may be sent to Sentry. Not used if the DSN is not configured. |
Hosting
The application can be run on any Node.js-compatible host (e.g. Vercel, self-hosted, on-prem). The codebase does not mandate a specific hosting provider. If you use a particular host, that provider is a subprocessor for your deployment and should be disclosed accordingly.
Updates
We do not add subprocessors without updating this page and, where appropriate, our data processing terms. For a signed DPA or current list in another format, contact support or your account team.
Related
- Data handling — Where data is stored
- Security overview
- Compliance