01
The boundary
Accounts, keys, policies, traces, and billing live in our control plane. A Box deployment you place in your cloud runs in your cloud. A Harness sandbox you pin to your network stays there. Data enters our environment on the path you configure, and not on a side channel we add later without telling you.
Customer content is not training data for World models. That rule is also on the privacy page.
02
The call path
A model call enters through Gateway or Harness, then Guard, then the route you set. Guard checks the policy on that key for personal data, secrets, document leakage, and prompt injection. The policy decides whether the call is logged, stopped, or sent on with the sensitive span removed. The decision is written to the trace.
Failover and the semantic cache run inside Gateway. A cache hit is answered from Gateway and is not sent to the provider again.
03
Keys and access
API KEYSShown once. Stored as a hash and a short prefix.
WORKSPACE ROLESSeparate rights to read traces, edit policy, and spend budget.
STAFF ACCESSNamed accounts, logged, limited to the job. Production access is not shared.
LEAKED KEYRevoked when you write to security@ylemlabs.com, or when we see the leak first.
Tell us about a leaked key before you rotate traffic onto it. Rotation is available in the workspace.
04
Sandboxes and tools
Harness runs tool calls in sandboxes. Network and filesystem scope are set per tool. A tool does not receive the workspace key unless you pass it in. Background and scheduled jobs use the same Guard policy as an interactive run.
05
Documents and traces
A Box knowledge base belongs to one workspace. Guard can check a document span you have marked before that span is placed in a model call. Traces are visible to roles that can read them, for the window on the privacy page. You can delete a cache and a knowledge base from the workspace.
06
Transport and storage
The site and the APIs are served over TLS. Traces, knowledge bases, and backups are encrypted at rest. A workspace close deletes customer content on the privacy-page schedule. Billing records follow that page too.
07
Audits
When an audit is finished, its name, scope, and date are added here.
ON FILENo completed audit published yet.
08
Report a vulnerability
Email security@ylemlabs.com. Include the product, the endpoint, and what an attacker could do with the bug. We acknowledge within 3 business days. Give us 90 days to fix it before you publish the details.
A useful report includes a single request that shows the impact. Leave other customers' data alone.
- No denial-of-service tests against the control plane.
- No phishing of staff or customers.
- No access to data that belongs to someone else.
A report sent in good faith under this section is not a breach of the acceptable-use clause in the terms. Out of scope: the behavior of a third-party model, a scanner dump with no demonstrated impact, and a cosmetic issue in a preview feature that holds no production data.
