Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.adrian.secureagentics.ai/llms.txt

Use this file to discover all available pages before exploring further.

Self-hosted Adrian runs entirely in your environment. Secure Agentics does not receive or store any data from self-hosted deployments. The sections below describe how data is handled on the hosted backend, plus prompt-injection defences that apply to both deployments.

​
Data handling and PII

Adrian runs two layers of PII redaction on data sent to the hosted backend.
  • SDK-side regex PII filtering. Runs inside your process before any data leaves it. Replaces matches with placeholder tags such as [EMAIL REDACTED] and [PHONE REDACTED], preserving the detection signal without exposing the underlying value. Sub-millisecond identification and drops data from ever leaving the target environment.
  • Server-side LLM sweep. Runs during processing on the hosted backend prior to storing, catching items regex cannot (names, contextual PII).
The SDK-side regex layer also runs in self-hosted deployments and acts as defence-in-depth even when data never reaches Secure Agentics.
Events stored by the hosted backend may be used for product improvement. You can opt out of longer-term data storage and product improvement in your account settings.

​
Prompt injection defences

These controls apply to hosted deployments only.
  • Inference isolation. The classifier model runs in an isolated environment with no tool, MCP, or internet access, bounding the blast radius if it is ever compromised.
  • Data spotlighting. Untrusted input from agents and frontends is structurally separated from instructions so it cannot impersonate them.
  • Output contract. The classifier’s output is constrained to a strict format - anything else is rejected, blocking attempts to leak the system prompt or bypass classification.