User Data Policy & Privacy Standard
Effective Date: October 2026 • Architecture Compliance: GDPR, CCPA, SOC2 Type II Principles
1. Purpose and Philosophy
Agent Observability Dashboard was designed on the principle of data minimization. We provide telemetry streaming and operational oversight for autonomous agents without intercepting or analyzing your proprietary prompt engineering or underlying model weights.
2. Information We Collect and Process
We process only data strictly necessary to provide the real-time observability service:
- Account Identity: Operator name and registered email address used exclusively for authentication.
- Cryptographic API Token: A randomly generated 64-character token used to enforce isolated tenant workspaces.
- Task Metadata: High-level goal titles and structured step progressions registered by the agent.
- Result Summaries: Brief diagnostic text emitted by the agent upon task completion.
3. Tenant Isolation & Cryptographic Boundary
Each user account is siloed behind an individual token. When an agent calls the REST API or connects to the WebSocket stream, our connection manager filters all events in real time. No user can view, listen to, or inspect another operator's active agent stream.
Cryptographically isolated workspaces per API token.
Zero commercialization or third-party ad profiling.
End-to-end encryption across HTTPS and WSS protocols.
4. Zero Commercialization Policy
5. Data Retention & Tenant Isolation
To maintain peak operational velocity and privacy, each operator workspace is isolated behind strict cryptographic boundaries. Telemetry is stored in an encrypted volume with atomic persistence guarantees and can be deleted individually by the operator at any time.
6. Data Controller Contact
For data erasure requests, compliance audits, or data portability inquiries, contact the security office directly at: