Data Processing, Privacy, and Compliance
Olly is designed with security and compliance as foundational principles. It inherits the same technical and organizational controls that protect the rest of the Coralogix platform, including access controls, data segregation, and audited security programs aligned with ISO 27001 and SOC 2 Type II.
Architecture and data flow
Security and compliance are built into how Olly works. Every query is authenticated, uses only the data needed to answer the question, and is processed inside Coralogix-managed infrastructure. Your data never leaves your security boundary.
When you ask Olly a question:
- Authenticate — Olly verifies your Coralogix identity and applies your permissions before doing anything.
- Fetch minimally — Olly retrieves only the telemetry relevant to your question. It does not access Block-tier data or Frequent Search.
- Build context — Your question, a minimal slice of telemetry, and internal policy guardrails are assembled into a context window.
- Generate privately — The context is sent to your selected model provider inside a private, Coralogix-managed deployment — not a public shared endpoint.
- Stay inside Coralogix — Nothing is written outside your existing infrastructure. Any queries, dashboards, or alerts Olly generates live in your account under your existing access controls.
By default, Olly uses a private Azure OpenAI deployment inside Coralogix's own Azure virtual network. You can also select Claude (AWS) — in every case, inference runs inside an enterprise deployment with contractual data protection. Learn more in Model selection.
Data categories and minimization
Olly uses the minimum data required to answer each question.
Data that may be processed:
- Telemetry — logs, metrics, and traces
- Resources — alerts, dashboards (when a URL is shared explicitly via the @ context menu)
- Account context — service names, applications, subsystems, environments, fields, and other configuration metadata
- User interactions — prompts, follow-up questions, Olly's responses, and optional feedback signals
Note
When you use the @ button to reference a Coralogix resource — such as a dashboard, alert, or saved query — its relevant metadata is included in the context window sent to the model provider. Only resources you explicitly select are included.
Identity and access
Olly operates as the logged-in Coralogix user and inherits their permissions. Every query runs within the scope of the user's Coralogix roles, teams, and policies.
- Olly respects role-based permissions and policies configured in Coralogix
- Olly cannot access data outside the teams and permissions associated with the current user
- If a user cannot see specific data in the Coralogix UI, Olly cannot access it either
Activation
Olly is disabled by default and must be explicitly activated by a user with the relevant Coralogix permissions in Settings, then Account Preferences, then AI-Powered Capabilities. When AI capabilities are disabled, Olly is not available to any team member. Learn more in Enable Olly.
Tenant isolation and regional data residency
Olly operates within the same multi-tenant isolation model and regional boundaries as the Coralogix platform.
Tenant isolation
- Customer data is segregated using logical separation (per-customer keys) and physical separation by region
- Olly cannot access telemetry from a different tenant
Regional alignment
- Olly does not execute multi-region queries — within any given chat, Olly generates answers only from data within the same region
- For GPT, Olly processes data in Microsoft Azure regions that correspond to the customer's selected hosting region
- For Claude, Olly processes data in AWS regions that correspond to the customer's selected hosting region
Data protection and network security
Olly inherits Coralogix's technical and organizational measures for protecting customer data.
Platform-level protections:
- Data in transit is protected with TLS 1.2 or above
- Data at rest is encrypted using AES-256
- Coralogix isolates services in hardened VPCs and uses firewalls, security groups, and intrusion detection solutions
Azure OpenAI protections:
- The deployment runs inside Coralogix's own Azure VNet, not a public shared endpoint
- Data sent to Azure OpenAI is encrypted in transit and at rest
- Azure OpenAI does not use customer data to retrain or fine-tune models
Data retention and deletion
- Olly does not store data externally — no prompts or telemetry are held outside Coralogix infrastructure
- Telemetry that Olly analyzes is stored and retained according to your existing Coralogix retention settings
- For security and observability, Olly may log user prompts, timestamps, references to telemetry used as context, and resulting actions — these logs are stored under the same encryption and audit frameworks as other platform logs
- GPT and Claude do not store cached contents
- User sessions are stored as artifacts to allow access to session history for the duration of the subscription term
Governance and admin controls
- Olly is disabled by default and must be explicitly activated in Settings, then Account Preferences, then AI-Powered Capabilities
- Olly is governed by the Coralogix Master Subscription Terms and Addendum and the AI Tools Acceptable Use Policy
Model providers and data use
Olly supports two enterprise model providers. The active provider is selected per user in the chat interface. Learn more in Model selection.
| Provider | Infrastructure | Fast mode model | Focus mode model | Data use |
|---|---|---|---|---|
| GPT (default) | Microsoft Azure (Coralogix VNet) | GPT-5 mini | GPT-5.1 | Not used for training |
| Claude | AWS (Coralogix VPC) | Haiku 4.5 | Sonnet 4.5 | Not used for training |
- Microsoft Azure and AWS act as subprocessors for model inference under contractual data protection obligations and signed Data Processing Agreements
- Customer prompts and completions are not used to train foundation models
- For GPT and Claude, model deployments run inside Coralogix-managed VPC infrastructure — OpenAI and Anthropic cannot directly access or store your data
Compliance frameworks
Olly runs inside the same security and compliance boundary as the Coralogix platform.
Coralogix maintains third-party certifications and assessments, including:
- SOC 2 Type II
- ISO/IEC 27001, 27017, 27018, 27701
- ISO/IEC 42001:2023 (AI management)
- PCI DSS v4
- GDPR and CCPA alignment
- HIPAA compliance (subject to BAA)
- DORA and EU-US Data Privacy Framework support
AI-specific safeguards
Olly includes safeguards against prompt injection, data exfiltration, and misuse:
- Olly is restricted to Coralogix APIs and data stores and cannot directly access external systems or arbitrary networks
- Integrations (such as Slack) are mediated through Coralogix backends with additional permissions and validation
- Internal system prompts restrict Olly to allowed actions
- Requests are subject to rate limits to reduce abuse and denial-of-service risk
- Coralogix AI security tooling detects patterns that look like prompt injection, jailbreak attempts, or unusual data access