The page opens by saying data privacy and security are LiteLLM's top priority
The page opens with a general statement that LiteLLM treats the privacy and security of your data as its top priority and handles the data you share with it with the highest level of diligence. The statement names no specific measure, data type or user group. The concrete statements come in the sections that follow, and several of those sections address self-hosted users only.
Supporting quotations
safeguarding your data privacy and security is our top priority
handle it with the highest level of diligence
Not stated here
The opening sentence refers to "the data you share with us" but does not say what data that is or which users share it. The sections that follow say a self-hosting user sends no data to LiteLLM servers except through telemetry that the user points there.
Legal Rights & Agreement Rules · Context
The security, privacy and cookie sections address self-hosted LiteLLM users only
Three sections of this page carry headings that limit them to self-hosting: the Security Measures section is headed for self-hosted instances, and both the Collection of Personal Data section and the Cookies section are headed "For Self-hosted LiteLLM Users". The page has no matching section describing data or cookie handling for anyone who uses a service that LiteLLM hosts. The later sections on vulnerability reporting, vulnerability scanning and the legal and compliance questions carry no self-hosted label.
Supporting quotations
Self-hosted Instances LiteLLM
For Self-hosted LiteLLM Users:
For Self-hosted LiteLLM Users:
Qualifications & exceptions
Applies to people who run the LiteLLM software on their own infrastructure.
The vulnerability reporting, scanning and legal and compliance sections are not labeled self-hosted.
Not stated here
The page does not say how data or cookies are handled for a person who uses a LiteLLM-hosted service or the LiteLLM website.
Data Access & Collection · Company practice
Self-hosting sends no data or personal data to LiteLLM servers, except telemetry you point at them
For people who self-host the software, the page says no data or telemetry is stored on LiteLLM servers unless the user points the usage telemetry HTTP endpoint at them. It also says no personal data is collected or transmitted to LiteLLM servers, and that data generated or processed stays entirely within the user's own infrastructure. The second and third sentences are written without the telemetry exception, so the telemetry exception stated in the first sentence and explained in the telemetry card is the one stated limit on the page.
Supporting quotations
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
No personal data is collected or transmitted to LiteLLM servers when you self-host our software.
Any data generated or processed remains entirely within your own infrastructure.
Qualifications & exceptions
Only when you self-host the software.
Exception: usage telemetry the user points at LiteLLM servers by setting its HTTP endpoint.
Not stated here
The page does not say whether telemetry that a user chooses to send to LiteLLM could contain personal data. The list of telemetry fields is on a linked page that this document does not supply.
Data Access & Collection · User right or choice
Usage telemetry is off by default for self-hosters and has no default endpoint
The page says 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 an endpoint that points there. The page refers readers to a separate Usage telemetry page for every field the telemetry can collect.
Supporting quotations
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
for every field it can collect
Qualifications & exceptions
Only when you self-host LiteLLM.
Telemetry is sent only after you turn it on and set an endpoint that points at LiteLLM servers.
Not stated here
"Aggregate counts" is not defined here. The text of the linked Usage telemetry page is not supplied here, so this card cannot say which fields the telemetry collects.
Data Access & Collection · Company practice
LiteLLM says its cookies are used only to keep Admin UI users logged in
For self-hosted users, the page says LiteLLM uses minimal cookies, solely to let Proxy users access the LiteLLM Admin UI. It says the cookies are not used for advertising, tracking or any purpose beyond maintaining the login session, that the only cookies used are essential for authentication and session management for the app UI, and that LiteLLM does not use third-party cookies.
Supporting quotations
LiteLLM uses minimal cookies, solely for the purpose of allowing Proxy users to access the LiteLLM Admin UI.
We do not use cookies for advertising, tracking, or any purpose beyond maintaining your login session.
The only cookies used are essential for maintaining user authentication and session management for the app UI.
LiteLLM does not use any third-party cookies.
Qualifications & exceptions
Applies to self-hosted LiteLLM users, in the cookies section headed for them.
Applies to the cookies that let Proxy users reach the LiteLLM Admin UI.
Not stated here
The page does not say what cookies, if any, the LiteLLM website or a LiteLLM-hosted service sets.
Retention & Deletion · Company practice
Login cookies are stored in your browser and expire on browser close, logout or after 24 hours
The page says the cookies are stored in your web browser after you log in. It also says session cookies expire when you close your browser, log out, or after 24 hours. The sentence lists the three events without stating that the earliest one controls.
Supporting quotations
These cookies are stored in your web browser after you log in.
Session cookies expire when you close your browser, logout or after 24 hours.
Qualifications & exceptions
Applies to the Admin UI login cookies of self-hosted users.
The cookies are stored in your browser after you log in.
Not stated here
The page does not say whether the three expiry events are alternatives where the earliest controls, or whether a browser left open is still cut off at 24 hours.
Sharing & Disclosure · Company commitment
Cookie data stays in your infrastructure, is held as a JWT and is not accessed or shared for other purposes
The page says cookie data remains within your own infrastructure. It says the Admin UI reads the cookie to authenticate your login session, that the cookie is stored as a JWT and is not accessible to any other part of the system, and that LiteLLM does not access or share this cookie data for any other purpose.
Supporting quotations
Cookie data remains within your own infrastructure.
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.
Qualifications & exceptions
Applies to self-hosted LiteLLM users.
LiteLLM's commitment is limited to "any other purpose" than the authentication use described.
Not stated here
The page does not say what purpose, if any, LiteLLM itself accesses the cookie data for, since the cookie stays in the user's infrastructure.
Security & Safeguards · Procedure
The page gives support@berri.ai for security inquiries and krrish@berri.ai for incidents and questions
The page tells readers to contact support@berri.ai for security inquiries. The vendor information section separately gives krrish@berri.ai as the point of contact for security incidents and for general security-related questions. Vulnerability reports have their own route, described in the vulnerability reporting card.
Supporting quotations
For security inquiries, please contact us at
Point of contact email address for security incidents:
Point of contact email address for general security-related questions:
Qualifications & exceptions
The support@berri.ai address appears in the self-hosted security measures section; the krrish@berri.ai addresses appear in the vendor information list.
Not stated here
The page does not say how the two addresses differ or which one to use for a given kind of question.
Security & Safeguards · Procedure
Vulnerability reports go preferably to GitHub Security Advisories, with email as a slower fallback
The page says the canonical vulnerability disclosure policy is the security.md file in the LiteLLM repository, which includes information about the bug bounty. It says the preferred way to report a vulnerability is a private report through GitHub Security Advisories. If you cannot use GitHub, emailing support@berri.ai with the same details works, but may be triaged more slowly. In the vendor questions, the page answers Yes to whether a vulnerability disclosure policy is in place.
Supporting quotations
The canonical vulnerability disclosure policy lives in
which includes information about our bug bounty
The preferred channel for reporting a vulnerability is to file a private vulnerability report through
If you cannot use GitHub, emailing support@berri.ai with the same details works in a pinch, though may be triaged more slowly.
Does the vendor have a vulnerability disclosure policy in place?
Qualifications & exceptions
The security.md file is named as the canonical policy; this page summarizes it only in part.
Email is a fallback for people who cannot use GitHub.
Not stated here
The security.md file is linked but not supplied here, so the bug bounty terms and any differences from this page are unknown.
Security & Safeguards · Restriction or exception
All vulnerability reports must include a video or screen recording of the full exploit
The page says that, to combat low-quality AI spam, all vulnerability reports require a video or screen recording that demonstrates the full exploit. The wording says all reports, so it covers the GitHub route and the email fallback described on the same page.
Supporting quotations
in order to combat low-quality AI spam, all vulnerability reports require a video or screen recording of you demonstrating the full exploit
Qualifications & exceptions
Stated as a requirement for all vulnerability reports, with the stated aim of combating low-quality AI spam.
Not stated here
The page does not say what happens to a report that arrives without a video or screen recording. The linked security.md policy is not supplied and could add or change requirements.
Security & Safeguards · Company practice
LiteLLM runs grype security scans on all built Docker images
The page says LiteLLM runs grype security scans on all built Docker images and shows a current status line of passing with no high or critical severity vulnerabilities found. In the vendor questions it answers Yes to performing vulnerability scans and says regular scans are conducted as detailed in the Vulnerability Scanning section.
Supporting quotations
LiteLLM runs grype security scans on all built Docker images.
Current Status: ✅ Passing. 0 High/Critical severity vulnerabilities found.
Does the vendor perform vulnerability scans?
Yes, regular vulnerability scans are conducted as detailed in the Vulnerability Scanning section.
Qualifications & exceptions
The scanning described is for built Docker images.
The status line is a point-in-time statement.
Not stated here
The status line has no date, so the time it describes is unknown. "Regular" is not defined, and the page does not state a scan frequency or say whether anything other than Docker images is scanned. The CI/CD link the page cites is not supplied.
Security & Safeguards · Company practice
LiteLLM says it holds SOC 2 Type II and makes its report available through its Trust Center
In answer to whether the vendor has been audited or certified, the page says SOC 2 Type II and that the current report is available through the LiteLLM Trust Center.
Supporting quotations
Has the Vendor been audited / certified?
SOC 2 Type II. Our current report is available through the LiteLLM Trust Center.
Qualifications & exceptions
The report is reached through the LiteLLM Trust Center, not on this page.
Not stated here
The page does not say which product, entity or period the report covers, or what conditions apply to getting the report. The Trust Center is linked but not supplied.
Security & Safeguards · Company practice
LiteLLM says it has an information security management system and uses CodeQL
In answer to whether an information security management system has been implemented, the page says Yes, with CodeQL and an ISMS covering multiple security domains.
Supporting quotations
Has an information security management system been implemented?
and an ISMS covering multiple security domains
Not stated here
The page does not list the security domains the ISMS covers or name a standard it follows.
Security & Safeguards · Company practice
LiteLLM says it logs key events such as authentication, creation and updates through audit logs
In answer to whether logging of key events (authentication, creation and update changes) occurs, the page says Yes and points to audit logs documentation. The page's description of LiteLLM Enterprise also lists audit logs among its features.
Supporting quotations
Is logging of key events - auth, creation, update changes occurring?
Yes - we have
audit logs
Qualifications & exceptions
The question concerns key events: authentication, creation and update changes.
Not stated here
The page does not say whether audit logs are available in the free self-hosted software or only in LiteLLM Enterprise, or whether they are on by default. The documentation link, which refers to switching audit logs on, is not supplied.
LiteLLM says it has an incident management program and shares its Incident Response Policy on request
In answer to whether it has an established cybersecurity incident management program, the page says Yes, and that its Incident Response Policy is available upon request.
Supporting quotations
Does the Vendor have an established Cybersecurity incident management program?
Yes, Incident Response Policy available upon request.
Qualifications & exceptions
The policy is provided only on request.
Not stated here
The page does not say who may request the policy, how to request it, or what it contains. The policy is not supplied.
Legal Rights & Agreement Rules · Context
The vendor information names Berrie AI Incorporated as the legal entity and lists a signer
The vendor information list gives the legal entity name as Berrie AI Incorporated. It also lists a signer by name, Krish Amit Dholakia, with a contact email.
Supporting quotations
Legal Entity Name: Berrie AI Incorporated
Signer Name: Krish Amit Dholakia
Signer Email:
Not stated here
The page does not say that this entity operates the LiteLLM website or any hosted service, or what the signer signs on behalf of.
Charges & Financial Obligations · Context
The page lists invoicing, AWS Marketplace and Azure Marketplace as procurement options
Under Procurement Options, the page lists three ways to buy: invoicing, AWS Marketplace and Azure Marketplace.
Supporting quotations
Invoicing
AWS Marketplace
Azure Marketplace
Not stated here
The page gives no prices, terms or eligibility for these options and does not say which LiteLLM product each covers.
Account & Service Control · Context
LiteLLM Enterprise is described as offering SSO/SAML, audit logs, spend tracking, team management and guardrails
A closing panel describes LiteLLM Enterprise as offering SSO/SAML, audit logs, spend tracking, multi-team management and guardrails, built for production. It links to a separate Enterprise page.
Supporting quotations
LiteLLM Enterprise
SSO/SAML, audit logs, spend tracking, multi-team management, and guardrails, built for production.
Not stated here
The page does not say which of these features are absent from the self-hosted open-source software, and the Enterprise page is not supplied.