CamplaxThe owner must confirm the legal entity, service region, data categories, contract/DPA status, and transfer mechanism for every provider below. Remove any provider that is not enabled in production, and add any production provider not listed.
Current technical provider inventory
| Provider / product | Expected purpose |
|---|---|
| Cloudflare | Camplax control-plane hosting, DNS/SSL, edge delivery, object storage, queues, and related platform services. |
| Fly.io | Customer application compute. |
| Prisma Postgres | One customer application database per app and database-management operations. |
| GitHub | Repository connection and deployment-source integration when a customer connects a repository. |
| Resend | Transactional account, verification, recovery, and operational email when production email delivery is enabled. |
| OpenRouter | AI gateway and support-assistant model routing only when a customer or Camplax feature invokes an AI model. |
| Stripe | Payment-related features when payment processing is enabled for the relevant product flow. |
How we manage changes
Camplax will update this page before or at the time it adds a material subprocessor, subject to any contractual notice period. A customer with a valid data-processing agreement may object through [[privacy or legal contact email]]; the final data-processing addendum must state the review and objection process.
Data location and transfers
Data residency depends on the enabled provider, customer configuration, and region. Camplax must not promise a country, region, or transfer safeguard until it has documented the actual production configuration and contractual mechanism. See the Privacy Notice for the broader handling explanation.