Subprocessors
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
| Subprocessor | Role | Region |
|---|---|---|
| Anthropic | LLM inference (default). Prompts and responses processed for inference only; no training, no retention beyond inference. | United States |
| OpenAI | LLM inference (alternate). Same posture: enterprise endpoints, no training. | United States |
| Cloudflare | CDN and DDoS mitigation for the marketing site. Sees visitor IPs and request metadata. | Multi-region |
| Customer-chosen IdP | Identity 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 jubi.my.
Customer-deployed components
Your own Metabase instance, data warehouse, and IdP 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@jubi.my