Data Privacy and Security
Data Privacy and Security
At LiteLLM, safeguarding your data privacy and security is our top priority. We recognize the critical importance of the data you share with us and handle it with the highest level of diligence.
- The page opens by saying data privacy and security are LiteLLM's top priority Security & Safeguards
Security Measures
Self-hosted Instances LiteLLM
- The security, privacy and cookie sections address self-hosted LiteLLM users only Legal Rights & Agreement Rules
- No data or telemetry is stored on LiteLLM Servers when you self-host, unless you point usage telemetry's HTTP endpoint at them as described below
- Self-hosting sends no data or personal data to LiteLLM servers, except telemetry you point at them Data Access & Collection
- For installation and configuration, see: Self-hosting guide
- Telemetry: Usage telemetry is off by default when you self-host LiteLLM. If you turn it on, it keeps aggregate counts in your own database or sends them to the HTTP endpoint you set. There is no default endpoint, so nothing reaches LiteLLM servers unless you set one that points there. See Usage telemetry for every field it can collect
- Usage telemetry is off by default for self-hosters and has no default endpoint Data Access & Collection
For security inquiries, please contact us at support@berri.ai
- The page gives support@berri.ai for security inquiries and krrish@berri.ai for incidents and questions Security & Safeguards
Collection of Personal Data
For Self-hosted LiteLLM Users:
- The security, privacy and cookie sections address self-hosted LiteLLM users only Legal Rights & Agreement Rules
- No personal data is collected or transmitted to LiteLLM servers when you self-host our software.
- Self-hosting sends no data or personal data to LiteLLM servers, except telemetry you point at them Data Access & Collection
- Any data generated or processed remains entirely within your own infrastructure.
- Self-hosting sends no data or personal data to LiteLLM servers, except telemetry you point at them Data Access & Collection
Cookies Information, Security, and Privacy
For Self-hosted LiteLLM Users:
- The security, privacy and cookie sections address self-hosted LiteLLM users only Legal Rights & Agreement Rules
- Cookie data remains within your own infrastructure.
- LiteLLM uses minimal cookies, solely for the purpose of allowing Proxy users to access the LiteLLM Admin UI.
- LiteLLM says its cookies are used only to keep Admin UI users logged in Data Access & Collection
- These cookies are stored in your web browser after you log in.
- We do not use cookies for advertising, tracking, or any purpose beyond maintaining your login session.
- LiteLLM says its cookies are used only to keep Admin UI users logged in Data Access & Collection
- The only cookies used are essential for maintaining user authentication and session management for the app UI.
- LiteLLM says its cookies are used only to keep Admin UI users logged in Data Access & Collection
- Session cookies expire when you close your browser, logout or after 24 hours.
- LiteLLM does not use any third-party cookies.
- LiteLLM says its cookies are used only to keep Admin UI users logged in Data Access & Collection
- The Admin UI accesses the cookie to authenticate your login session.
- The cookie is stored as JWT and is not accessible to any other part of the system.
- We (LiteLLM) do not access or share this cookie data for any other purpose.
Security Vulnerability Reporting Guidelines
We value the security community's role in protecting our systems and users.
The canonical vulnerability disclosure policy lives in security.md in the LiteLLM repository, which includes information about our bug bounty.
- Vulnerability reports go preferably to GitHub Security Advisories, with email as a slower fallback Security & Safeguards
The preferred channel for reporting a vulnerability is to file a private vulnerability report through GitHub Security AdvisoriesGitHub. If you cannot use GitHub, emailing support@berri.ai with the same details works in a pinch, though may be triaged more slowly.
- Vulnerability reports go preferably to GitHub Security Advisories, with email as a slower fallback Security & Safeguards
Please note that in order to combat low-quality AI spam, all vulnerability reports require a video or screen recording of you demonstrating the full exploit.
- All vulnerability reports must include a video or screen recording of the full exploit Security & Safeguards
Vulnerability Scanning
- LiteLLM runs grype security scans on all built Docker images.
- LiteLLM runs grype security scans on all built Docker images Security & Safeguards
- See grype litellm check on ci/cd.
- Current Status: ✅ Passing. 0 High/Critical severity vulnerabilities found.
- LiteLLM runs grype security scans on all built Docker images Security & Safeguards
Legal/Compliance FAQs
Procurement Options
- Invoicing
- The page lists invoicing, AWS Marketplace and Azure Marketplace as procurement options Charges & Financial Obligations
- AWS Marketplace
- The page lists invoicing, AWS Marketplace and Azure Marketplace as procurement options Charges & Financial Obligations
- Azure Marketplace
- The page lists invoicing, AWS Marketplace and Azure Marketplace as procurement options Charges & Financial Obligations
Vendor Information
Legal Entity Name: Berrie AI Incorporated
- The vendor information names Berrie AI Incorporated as the legal entity and lists a signer Legal Rights & Agreement Rules
Point of contact email address for security incidents: krrish@berri.ai
- The page gives support@berri.ai for security inquiries and krrish@berri.ai for incidents and questions Security & Safeguards
Point of contact email address for general security-related questions: krrish@berri.ai
- The page gives support@berri.ai for security inquiries and krrish@berri.ai for incidents and questions Security & Safeguards
Has the Vendor been audited / certified?
- LiteLLM says it holds SOC 2 Type II and makes its report available through its Trust Center Security & Safeguards
- SOC 2 Type II. Our current report is available through the LiteLLM Trust Center.
Has an information security management system been implemented?
- LiteLLM says it has an information security management system and uses CodeQL Security & Safeguards
- Yes - CodeQL and an ISMS covering multiple security domains.
- LiteLLM says it has an information security management system and uses CodeQL Security & Safeguards
Is logging of key events - auth, creation, update changes occurring?
- LiteLLM says it logs key events such as authentication, creation and updates through audit logs Security & Safeguards
- Yes - we have audit logs
Does the Vendor have an established Cybersecurity incident management program?
- LiteLLM says it has an incident management program and shares its Incident Response Policy on request Security & Safeguards
- Yes, Incident Response Policy available upon request.
Does the vendor have a vulnerability disclosure policy in place? Yes
- Vulnerability reports go preferably to GitHub Security Advisories, with email as a slower fallback Security & Safeguards
Does the vendor perform vulnerability scans?
- LiteLLM runs grype security scans on all built Docker images Security & Safeguards
- Yes, regular vulnerability scans are conducted as detailed in the Vulnerability Scanning section.
- LiteLLM runs grype security scans on all built Docker images Security & Safeguards
Signer Name: Krish Amit Dholakia
- The vendor information names Berrie AI Incorporated as the legal entity and lists a signer Legal Rights & Agreement Rules
Signer Email: krrish@berri.ai
- The vendor information names Berrie AI Incorporated as the legal entity and lists a signer Legal Rights & Agreement Rules
LiteLLM Enterprise
- LiteLLM Enterprise is described as offering SSO/SAML, audit logs, spend tracking, team management and guardrails Account & Service Control
SSO/SAML, audit logs, spend tracking, multi-team management, and guardrails, built for production.