Legal
Sub-processors
These are the third-party services we engage to deliver Neivan. Each is bound by a Data Processing Addendum and limited to processing only the data they need for their role.
Last updated: July 22, 2026 · Subscribe to change notices
| Vendor | Purpose | Data processed | Region |
|---|---|---|---|
| DigitalOcean | Primary cloud hosting (compute, networking, managed cache) | All customer content & telemetry | US |
| Supabase | Managed Postgres + auth for tenant data | Customer accounts, content | US |
| Stripe | Payment processing & billing | Billing contact, card metadata (no PAN) | US |
| Resend | Transactional email delivery | Recipient email, message body | US |
| Sentry | Error monitoring & stack-trace capture | Stack traces, anonymized user IDs | US |
| OpenAI | LLM inference (when "managed" mode is selected) | Prompts + completions for that tenant | US |
| Anthropic | LLM inference (when "managed" mode is selected) | Prompts + completions for that tenant | US |
| Google (Gemini API) | LLM inference (when "managed" mode is selected) | Prompts + completions for that tenant | US |
| Cloudflare | DNS, TLS termination, CDN, DDoS protection | Request metadata, IPs | Global edge |
Change notice
We notify customers at least 30 days before adding a new sub-processor. Account owners are emailed automatically. To subscribe an additional address, write to [email protected].
Objection rights
You may object to a new sub-processor during the notice period. We'll work to provide an alternative; if none is feasible, you can terminate the affected service without penalty per the DPA.