Sub-processors
Sub-processors handling customer data
ProductionLens engages a small number of sub-processors to operate the service. Each processes a defined category of data, in a defined region, under a published DPA. We update this list when our sub-processor footprint changes.
Sub-processors list
| Sub-processor | Purpose | Data categories | Region | DPA |
|---|---|---|---|---|
| Supabase | Postgres database, authentication, file storage | Account, project, transaction, audit-log, uploaded source documents | ap-south-1 (Mumbai, India) | Supabase DPA |
| Vercel | Hosting & edge delivery of the web application | Request metadata; static assets. No customer database content stored at the edge. | Global edge; primary region US-East as fallback | Vercel DPA |
| Upstash Redis | Rate limiting and ephemeral key-value cache | Anonymised request fingerprints (IP hash, route). No persistent customer data. | ap-south-1 if env-configured; US-East fallback otherwise | Upstash Redis DPA |
| Sentry | Error telemetry and performance traces | Stack traces, request URL, user-id (UUID, no PII), browser metadata | EU (Frankfurt) | Sentry DPA |
| Cloudflare | DNS resolution (DNS only — no proxy / WAF for app traffic) | DNS queries (no application payload) | Global anycast | Cloudflare DPA |
Stay informed of sub-processor changes
Email security@reyatech.com and we will add you to the notification list. We notify subscribers at least 30 days before adding a new sub-processor that handles customer data.
Related: Security posture · Data Processing Addendum
Information current as of 2026-05-21.