Security
Last updated June 22, 2026
Relic ingests your code, tickets, and conversations to build memory for your team. This document describes how that data is processed, isolated, and deleted. For security questions or to report a vulnerability, contact [email protected].
Model training
Relic processes your repositories and conversations for a single purpose: to extract facts, such as ownership and technical decisions. Each fact is stored in your knowledge graph with a reference to its source.
Your source code and messages are never used to train any model. This applies without exception.
Tenancy and deployment
Your knowledge graph runs as a dedicated, single-tenant database. It holds only your data, and every query is scoped to your organization.
By default, Relic operates this in our managed environment. For teams that require it, we support on-premise deployment within your own infrastructure. To discuss deployment requirements, book a call.
Data retention and deletion
Disconnecting a source removes every fact derived from it. When a team member is removed, the memory scoped to them is deleted with them.
You may request complete deletion of your data at any time, and we will remove all of it. To initiate a request, contact [email protected].
Infrastructure and access
All data is encrypted in transit (TLS 1.2 or higher) and at rest (AES-256). Access is scoped per organization, with strict isolation between customers. Credentials and secrets are stored encrypted and are never held in plaintext.
If your security team maintains a vendor questionnaire or controls checklist, we are glad to complete it. Contact [email protected] to begin a review.
For any question this document does not cover, contact [email protected] or book a call.