Roles confirmed in the current architecture
| Provider | Confirmed role | Boundary note |
|---|---|---|
| Cloudflare | Public request transit and application delivery. | Cloudflare is in the public network path. Boundry therefore does not claim exclusively in-region network transit. |
| Clerk | Account identity, sessions, and organisation membership. | This is central control-plane processing, outside the regional communication database. |
Review still required
The provider review for regional compute, storage, delivery, observability, support, backups, and downstream vendor chains remains incomplete. Boundry will publish provider entities, purposes, data categories, processing locations, and change terms only after those details are checked against executed agreements and production configuration.
Cloudflare, Clerk, Laravel Cloud, AWS, and relevant downstream providers are included in that review. Naming a provider here does not assert that every service offered by that provider handles Boundry data.
Outside the Boundry boundary
Recipient mailbox providers
Email delivery necessarily hands a message to infrastructure chosen by the recipient or their organisation. Its location and retention are outside Boundry's control after delivery handoff.
Customer-selected destinations
Customers choose their own webhook endpoints and downstream systems. Those destinations are not Boundry subprocessors.
Questions and corrections
Send questions or corrections to privacy@boundry.dev.