Photo: Jason Dent / UnsplashWallet register · keplr.app
Is Keplr safe? What its terms and incident record say
No score publishedLast reviewed 0 recorded incidents
In short, from the documents
Is Keplr safe?
Keplr's terms disclaim custody but do not settle who holds key material. No party is disclosed as able to block an address. No primary-source incident is recorded, which is not proof of none. Its terms name no gambling rule. Liability is excluded for all loss.
Keplr: keys held by you, or split between you and the provider; who can block an address: none disclosed in the documents read; gambling clause: not disclosed; 0 primary-source incidents recorded. From its own terms, documents last checked . Not a rating. Drawn by the CryptoGuardz Register Desk from the record.
This page answers the short questions. The full Keplr entry quotes every clause behind them.
Disclosure:CryptoGuardz has no commercial relationship with Keplr and earns nothing if you install it.Every statement below is read from a document Keplr publishes or from a public record, and each carries the date it was read.Corrections go to the corrections page.
Keplr review: the documents
This is a review of the documents Keplr publishes, not a test of the product: no transaction was signed and no code audit was read. The contracting party named is Togra Corporation; on jurisdiction the record says: Not stated as incorporation. The custody position comes from the Keplr Terms of Use, effective 12 November 2025, read 2026-10-07. The record quotes 7 clauses across 6 topics, and 3 sub-service clauses where the app hands a swap, purchase or staking to another party. Keplr's terms disclaim custody but do not settle who holds key material. A cloud or hosted backup is offered, and by the record it changes who holds key material. 2 clauses let the provider suspend or withdraw access to the app; the keys stay yours, the interface does not. Liability is excluded for all loss. Its terms name no gambling rule. 7 points could not be verified and are listed below.
Has Keplr been hacked?
No primary-source incident was found for Keplr in this collection: no company disclosure, no public vulnerability register entry and no regulator action. That is not proof that none happened. It is the absence of a search result, and a forum post or a press report is not recorded here until a primary source confirms it.
Real support never asks for a seed phrase. The recovery phrase restores the whole wallet on any device, so whoever is given it can move everything it controls, and no support agent needs it to answer a question. What Keplr stores, by the record: Not a backup of a phrase. For credential-based login (Google, Apple and other SSO), the help centre says Web3Auth generates a private key by distributed key generation and stores it encrypted on the device; the terms describe Keplr and Keyshare Nodes verifying credentials and cooperating to generate signatures.
Support links reached from ads or direct messages are the commonest drain. A search ad, a reply to a public complaint or a direct message offers help, the link opens a page that looks like keplr.app, and the page asks you to “validate” or “sync” the wallet by entering the phrase. Once it is typed in, the wallet is emptied and nothing in the terms gives a way back.
If money has already gone, the next message offering to get it back is the commonest second loss. The FBI, the FTC, the CFTC and the UK FCA warnings about it are quoted on crypto scam recovery: what is real.
What we could not verify
The gaps in this record, as the record states them. A point listed here was looked for and not confirmed; it is neither a finding for Keplr nor against it.
Togra Corporation's place of incorporation and registered address. The terms give neither.
The operators of the Keyshare Nodes, how many there are, and what share Keplr itself holds.
Whether the Web3Auth social login described in the help centre and the Keyshare Node architecture in the terms are the same product.
The liability cap sentence verbatim. Retrieved only with an omission.
Whether Base, Polygon, BNB Chain or other register chains are supported. Not named in the documentation retrieved.
Named on-ramp providers and default RPC providers. Not named in the terms or privacy policy.
Documented incidents. No primary-source incident was located. Absence here is absence of a search result, not evidence of no incident.
Compiled by the CryptoGuardz Register Desk from the Keplr record, first published 2026-10-07, last reviewed 2026-10-07. Quotations are verbatim from the document named beside them. Corrections: corrections.
