08 Trust & legal

Subprocessors

Third-party services that process customer data on Jubi's behalf.

Last updated: 2026-10-20 · Pre-launch — pilot scope

Working list. This list reflects subprocessors used in pilot engagements. Subprocessors used at GA may differ; we update this page and notify customer admins of changes that affect customer data at least 30 days before they take effect. Questions: privacy@jubilabs.ai.

What is a subprocessor

A subprocessor is a third-party service that processes customer data on Jubi's behalf to deliver the platform.

Current list

SubprocessorRoleRegion
AnthropicLLM inference (default). Eligible AI requests use approved Zero Data Retention (ZDR) endpoints, subject to applicable provider terms and limited contractual exceptions; no training or fine-tuning.United States
OpenAILLM inference (alternate). Same approved ZDR endpoint restriction, including fallback routes; no training or fine-tuning.United States
CloudflareCDN and DDoS mitigation for the marketing site. Sees visitor IPs and request metadata.Multi-region
Customer-chosen IdPIdentity provider (Authentik, Okta, Azure AD/Entra, Google Workspace, etc.). Authentication assertions only.Customer-controlled

We do not currently use third-party advertising trackers, analytics platforms, or session-replay tools on jubilabs.ai.

ZDR limits provider retention of eligible AI requests; it does not prevent processing or establish data residency. Applicable terms may permit temporary processing, in-memory caching, billing or usage metadata and limited contractual exceptions. Customer-environment application storage is separate. See the Privacy Policy for the company-wide AI standards and integration data handling.

Customer-deployed components

Your data warehouse and identity provider are not subprocessors of Jubi — they are the customer's own systems. Jubi reaches them on the user's behalf and under the user's permissions.

Hosting (managed deployment)

The default managed deployment runs on a single hyperscaler region (chosen at engagement start). The hyperscaler operating that region is also a subprocessor. The current default region for pilot engagements is documented in the engagement-specific addendum, not on this public page.

Notification of changes

Material changes are posted here and emailed to customer admins at least 30 days before they take effect, allowing the customer to object before the change applies to their data.

Privacy: privacy@jubilabs.ai