Details on the August 2026 Metabase security incident, its impact on Privy, and our response.
Privy team
|Aug 10, 2026

On August 6th, 2026, the Privy security team was notified of a security incident affecting one of our service providers, Metabase, which we use for analytics and customer support.
The Privy security team completed its initial investigation into the impact of the Metabase breach for Privy users and began notifying affected Privy customers that same day.
Privy wallet infrastructure and authentication systems were not affected in this breach. Privy systems are fully segregated to protect all user assets, with wallet infrastructure run on cryptographically verifiable hardware separate from any other Privy system.
Our investigation determined that the attacker accessed customer and end-user email addresses and small subset of developer-set custom metadata fields, not tied to any particular Privy customer.
Upon notification, we immediately suspended connections from Metabase, rotated all connection credentials out of an abundance of caution, reviewed administrative access, and conducted a comprehensive investigation using Metabase’s forensic information and our own logs. We subsequently notified all affected customers directly with findings specific to their applications.
Because email addresses were involved, this incident may increase the risk of phishing, targeted social engineering, or other unsolicited communications.
Customers should remain cautious about unexpected emails, messages, and login prompts. Privy will never ask customers or end users to provide private keys, wallet seed phrases, or authentication credentials.
Although the vulnerability was in a third-party service, we are fully responsible for our dependencies and for limiting the data and access available through our integrations. We are further reducing the data fields and permissions available to analytics and support services, strengthening controls for third-party data connections, and adding further monitoring for unusual activity and anomalous query activity.
You can check your email for “Security update regarding Metabase” for details specific to your application, or request a copy of the full incident report by reaching out to security-support@privy.io.