// Trust & Security Report
Brave Software, Inc.
Brave Leo (AI assistant built into the Brave browser), Brave Search, Brave Search API
Certifications held
5
Maturity
Enterprise
Trains on your data
No
Trust center
Yes
// Certification ledger
Each held certification is backed by a verbatim quote from the vendor's own trust or security page. “Not confirmed” means we could not verify it publicly, not that the vendor lacks it.
Verify on trust.brave.app“Compliance: SOC 2 ... Resources > Compliance: SOC 2 Type 2 Report”
Verify on api-dashboard.search.brave.com“ISO standards such as 27001 and 27701 provide guidance for establishing, implementing, maintaining and continuously improving our approach to information security and privacy information management.”
// Privacy & AI training
Trains on customer data
No
Data processing agreement
Offered
Data region
United States (Brave is US-based; Search API subprocessors AWS, Slack, Stripe, Google Workspace all listed as United States). Leo chats are not retained server-side; history is local-device only.
Brave's browser privacy policy states for Leo: 'We don't store or retain prompts, responses, context, or personal data on our servers' and 'We do not use your conversations for model training.' Chat history, when enabled, is encrypted and stored locally on the user's device only. No account or login is required to use Leo. Brave proxies model requests so the underlying model providers do not receive identifying data; the policy states 'We do not collect identifiers that can be linked to you (such as IP address)' and large prompts are cached only temporarily and 'deleted within minutes.' DPA applies to the Brave Search API (developer/enterprise) product per the Trust Center.
// Security controls
Bug bounty platform
HackerOne (hackerone.com/brave). Covers security and privacy issues in current desktop, iOS and Android releases of the Brave browser.
hackerone.comPenetration testing
Third-party penetration testing performed; report listed in Trust Center: 'Web Service Penetration Test Brave Search API Executive Summary Q1 2025'.
trust.brave.appEncryption
Data encryption and encrypted data transmission utilized (Trust Center product-security controls). Local Leo chat history is encrypted on-device.
trust.brave.appTrains on customer data by default
No. 'We do not use your conversations for model training.'
brave.comSecurity contact / disclosure
security@brave.com with PGP-encrypted reports; public 'Report a security issue' link on site.
brave.com// Products & data scope
data: Prompts, conversation context, webpage content (for summaries), and tab titles/URLs are sent to Brave-operated servers per request but not retained. No account required. Chat history is optional and stored locally on-device. Not used for model training.
Built into the Brave browser (desktop, Android, iOS). Uses reverse-proxy anonymization so model providers do not see user identity or IP.
data: Same privacy posture as free Leo (no retention, no training); adds access to additional/larger models and faster responses. Premium uses an anonymous token-based subscription credential unlinkable to identity.
Paid subscription. Supports 'bring your own model' (local or remote endpoints) for additional user control.
data: Developer API powered by Brave's independent web index; used in search products, AI search, AI training, and agentic AI. Covered by SOC 2 Type 2, GDPR, PCI DSS SAQ A, DPA, and penetration testing per the Trust Center.
This is the product the trust.brave.app Trust Center and enterprise compliance attestations specifically cover. Leo is a separate consumer product that consumes Brave Search for richer answers.
// What to watch
- Scope nuance: the Trust Center (trust.brave.app) and the SOC 2 Type 2 / PCI / DPA attestations are formally scoped to the Brave Search API, not to the consumer Leo assistant itself. Leo's assurances (no retention, no training, local-only history) come from Brave's browser privacy policy rather than a Leo-specific audit.
- Leo Premium and some models route through third-party LLM providers via Brave's anonymizing reverse proxy; Brave states providers do not receive identifying data, but the specific provider list/data terms are not enumerated on a single Leo trust page.
- No SOC 2 / ISO certification is published specifically for the Leo product surface.
- ISO 27001 and ISO 27701 are referenced by Brave only as guidance frameworks ('ISO standards such as 27001 and 27701 provide guidance...' on the Brave Search API security page), not as held/attested certifications. Both correctly remain 'unknown' and must not be upgraded to held. HIPAA is not mentioned in any Brave source and remains 'unknown'.
// At a glance
Pricing model
Freemium — Leo is free; Leo Premium is a paid subscription. Brave Search API is usage-priced for developers/enterprise.
Self-hostable
No
// How we verified this
Every certification marked HELD is confirmed against a verbatim quote on Brave Software, Inc.'s own trust, security, or privacy pages. We reject certifications claimed only on third-party aggregators, on a cloud host's behalf, or by a similarly named company.
Last verified 2026-06-27. Compliance changes over time. Always confirm directly with the vendor before relying on any certification for a purchasing or compliance decision.
trust.brave.app