Last updated: March 24, 2026
This list identifies subprocessors Nopi engages to support the Service. It may be updated periodically as services evolve.
| Subprocessor | Purpose | Data categories | Transfer context |
|---|---|---|---|
| Supabase | Database and authentication infrastructure | Account data, workspace content, task metadata | Cross-border processing may apply depending on service region configuration |
| Vercel | Hosting and delivery for website/dashboard components | Operational logs, request metadata | Cross-border processing may apply based on edge/hosting routing |
| Stripe | Payment processing and billing workflows | Billing identifiers and transaction metadata | Cross-border processing may apply under Stripe terms |
| PostHog | Product analytics (consent-gated) | Event metadata and usage analytics | Configured with EU host by default; transfer context may still vary |
| Google (GTM / Analytics) | Marketing analytics and tag management (consent-gated) | Web usage and attribution signals | Cross-border processing may apply under Google terms |
Material subprocessor updates are reflected on this page. For contract-level notice requirements, contact hello@nopi.me.
Nopi evaluates subprocessors for security posture, reliability, and privacy controls before use. Reviews include service necessity, data scope minimization, and contractual safeguards appropriate to the processing role.
This page summarizes core subprocessors used for platform operation and analytics. Region-specific hosting patterns, optional features, and future integrations may result in updates to this list.