Security, Privacy & Governance

Last Updated: 11 June 2026

DoCoreAI is built for production GenAI systems operating under security, risk, and governance constraints. We observe system behaviour — never model content. By design, we never store prompt or output content; only the telemetry needed to compute cost, efficiency, and ROI.

The Short Version
  • Content-blind by design. We never see or store prompts, responses, or customer payloads.
  • Non-blocking architecture. If DoCoreAI is unavailable, your application keeps working normally.
  • Tenant-isolated. Your telemetry is never visible to other customers, accessible only via your own token.
  • SOC 2 & ISO 27001 alignment are on our compliance roadmap.
  • Configurable retention, with telemetry opt-out and data deletion supported on request.

01Trust Philosophy

DoCoreAI follows a minimal, privacy-first design. We collect only what's needed to understand how your GenAI systems behave in production — without ever accessing or storing prompts, responses, or customer content.

This lets your team operate, monitor, and govern GenAI systems without introducing new privacy or security risk of its own.

02What We Collect — and What We Don't

DoCoreAI is intentionally content-blind. Here's exactly where the line is drawn.

📊
We Collect
  • Token counts (prompt and completion)
  • Request latency, retries, and error signals
  • Model and version identifiers
  • High-level usage and cost metrics
🚫
We Don't Collect
  • Prompt text or prompt bodies
  • Model responses or generated content
  • User inputs or application payloads
  • LLM provider API keys or secrets
  • Personally identifiable information (PII), by default

03Data Flow Overview

Application content flows directly between your system and your LLM provider — completely unchanged. DoCoreAI receives telemetry through a separate, telemetry-only channel.

Your Application Runs the DoCoreAI SDK in-process
Prompts & Responses
(direct, unchanged)
LLM Provider OpenAI · Anthropic · Gemini · Groq · Bedrock · Ollama
Metadata Only
No prompts. No outputs.
DoCoreAI Cloud Tokens · Latency · Cost · Success/Failure

DoCoreAI does not proxy or store LLM requests or responses. Prompt and response content is processed transiently, in-memory, only to compute telemetry metrics — and is never persisted or transmitted.

04Security Controls

🔐
Encryption

All communication uses HTTPS/TLS. We store only non-sensitive operational telemetry — numeric metrics, timestamps, and model identifiers. No customer content or secrets are ever stored.

🔑
Access Controls

Token-based authentication for all clients. Access to production systems is restricted, granted only when explicitly required and for a limited duration. Dashboards are read-only — there are no admin actions that modify or delete customer data.

🧩
Tenant Isolation

Each customer's telemetry is logically isolated and accessible only through their own token and authenticated account. Customers cannot view telemetry belonging to other customers.

05Risk & Reliability Design

Non-Blocking Architecture

DoCoreAI never sits in the execution path of your LLM requests. If DoCoreAI is unavailable, your application continues to function normally.

🛡️
Failure Isolation

Telemetry collection is designed to fail safely — without impacting model execution or your application's availability.

⚙️
Retention & Control

Telemetry retention is configurable per organisation in Account Settings. Telemetry can be disabled for sensitive projects or environments, and data deletion requests are supported.

06Compliance & Audit Readiness

DoCoreAI is designed to align with common enterprise security and privacy expectations as we scale.

📋
On Our Roadmap
  • SOC 2 alignment
  • ISO 27001 control alignment
⚖️
Already In Place
  • GDPR-aligned data minimisation and purpose limitation
  • DoCoreAI acts as a data processor — customers remain data controllers
  • Subprocessors limited to essential infrastructure providers

07AI Governance Enablement

DoCoreAI supports post-deployment oversight of GenAI systems without ever capturing prompts or outputs:

  • Cost and usage trend monitoring
  • Latency and reliability signals
  • Retry patterns and behavioural anomalies
  • Model and version change visibility over time

This gives governance teams oversight without introducing content-level surveillance.

08Vulnerability Disclosure

Found a security issue?

Please report it responsibly to saji.john@docoreai.com. We acknowledge all reports and work toward timely remediation.

09Contact

Security inquiries: info@docoreai.com

Privacy information: see our Privacy Policy

-->
Scroll to Top