How Jubi handles your data, in one place.
Every document a security reviewer or procurement team is likely to ask for. If something you need isn't here, email security@jubilabs.ai and we'll send it.
How we secure your data, and how to report a problem.
The architecture and the controls that sit on top of it. How vulnerability reports reach us. The per-request model that gates every AI call.
Infrastructure, identity, application security, operations, BCP/DR, incident response, customer security features. Each control marked active / in-build / roadmap.
ReferenceHow Guardian sees every AI request — Mode 1 (BYOAI) and Mode 2 (Jubi agents) pipelines, R1–R5 risk catches, audit coverage.
PolicyScope, safe-harbour conditions for good-faith research, and our coordinated-disclosure expectations. Reports go to security@jubilabs.ai.
DisclosureThird-party services that process customer data on Jubi's behalf. Material changes notified at least 30 days before they take effect.
What we collect, how we use it, what AI is allowed to do with it.
The data notices, plus the AI-specific commitments: no training on your data, where inference runs, how grounding works.
What data Jubi collects, the legal bases under PDPA Malaysia and the EU GDPR, your rights as a data subject, and how to exercise them.
PolicyModels we use, training and retention, inference residency, Article 22 GDPR, EU AI Act framing, sensitive-use restrictions, customer responsibilities.
AgreementPublic summary of the DPA attached to a customer engagement: roles, security measures, transfers, breach handling, audit rights, TOMs annex.
NoticeWhat cookies the marketing site sets and why. No advertising trackers, no cross-site profiling, no session-replay tools.
Site terms and pre-engagement documents.
These cover the marketing site and the pre-sales materials. Customer engagements run on the signed Master Service Agreement, not on these public versions.
Use of jubilabs.ai and pre-engagement materials. Includes warranty disclaimers, limitation of liability, IP, indemnification, dispute resolution, and governing law.
PolicyWhat customers and end-users may not do with Jubi: bypass Guardian, exfiltrate data, target other tenants, use the platform to harm individuals.
TargetsOperational uptime and incident-response targets today, with a contractual SLA expected in customer engagements at GA.
StatementWCAG 2.2 AA target, current conformance posture (partial), known limitations, and how to report accessibility issues.
Compliance roadmap
What we have. What we're working on. What's deliberately not in scope. We don't list certifications we don't hold.
Need a security questionnaire filled in?
We respond to CAIQ, SIG-Lite, VPAT/ACR, and customer-supplied formats. Email security@jubilabs.ai with the package and we'll indicate timing on receipt.