Photo: Jason Dent / UnsplashRegister entry · safepal.com

Is SafePal safe? What its own terms say

No score publishedLast reviewed 2026-10-07First published 2026-10-076 sources

Hacked, support scams, fees: is SafePal safe? The incident and support page.

Disclosure: CryptoGuardz has no commercial relationship with SafePal, earns nothing if you install it, and has not contacted the company or given it notice of this entry. Every statement below is either a verbatim quote from a document SafePal publishes or a statement about a public record, and both carry the date they were read. Corrections go to the corrections page.

5 clauses quoted verbatim · 4 sub-service clauses · 6 recorded gaps · 1 primary-source incident · no numeric score

1. What this means for you

Consequences first, in the conditional, each one produced by a clause in a document SafePal publishes itself. Every line links to that clause, quoted in full and dated. None of them is a claim that SafePal can move your coins on chain: the terms disclaim that power and this register takes them at their word on it.

2. What this entry records, and what it does not

This register publishes no number for a wallet. The payout score on the casino register has five defined components and a published arithmetic; no equivalent instrument exists here. What follows is a field-by-field account of what was read, where and when.

3. What we could not verify

Every entry carries this section. The gaps are published because a reader deserves the limits of the check as well as its results.

4. Who you are contracting with

The binding document names a company. It does not name a jurisdiction of incorporation, which is a different and smaller gap: a reader can find the counterparty but not the register it sits in.

5. The custody claim, and what the binding document says

What SafePal says in the place a user reads, against what it says in the place that binds a user.

SafePal sells hardware wallets (S1, X1) and a software wallet app. For the hardware wallets the device holds the keys; for the software app the keys are on the user's phone. The binding document is the SafePal Terms of Service, which covers the app and website and does not describe the hardware wallets or use the word non-custodial; it disclaims backup, discovery and recovery of keys.

Provider holds key material: no. Asserted from section 9.2 of the terms, which states SafePal will not store a backup of, nor be able to discover or recover, private keys or mnemonic words.

6. Recovery, and where the terms and the marketing differ

No difference found between the terms and the marketing on key storage. Whether the software app offers any cloud backup was not checked against the help centre.

7. The app is not the wallet

4 clauses, each one a place where the product routes a user to a counterparty the user never contracts with by name, under terms the user never opens. The count is of recorded clauses and not of distinct companies: two entries can name the same counterparty and each still be a separate thing the terms permit.

8. Withdrawing your access to the interface

Your keys are yours. The software you reach them through is licensed, and the licence can be withdrawn. 1 clauses are recorded on this point.

9. Who can block an address

SafePal claims no power to block an address in the documents read. No clause in the documents read discloses that another party in the stack can freeze or blacklist an address either. That is an absence of disclosure, not a guarantee that no such party exists.

10. What the terms say about gambling

Position recorded: not disclosed. No clause naming gambling, betting, casinos or wagering was found in the documents read. That is an absence in the documents, not a permission, and the general prohibition on unlawful use still applies.

No clause naming gambling, betting, casinos or wagering was found in the SafePal Terms of Service, last updated 5 September 2024. Searched safepal.com, retrieved 2026-10-07.

The card side of the same question is on the card register, and the casino side on KYC on withdrawal.

11. Chains it names

Of the eight chains this register filters on, SafePal names 6: Bitcoin, Ethereum, BNB Chain, Tron, Polygon, Solana. Not named on the pages read: TON, Base. Networks named on the SafePal Extension page. TON is not listed: the only TON source found is a SafePal blog post of 17 November 2022 announcing future compatibility in Q4 2022, which is a forward-looking statement and was not counted. Base was not confirmed. Per-device support for the S1 and X1 hardware wallets was not checked.

12. Liability, amendment, arbitration and where you can use it

The liability clause excludes liability for all loss rather than capping it at a figure. It is the clause that decides what the rest of the document is worth.

What the provider states it processes, and who it passes it to. Recorded because a wallet that never touches a key can still see every address you hold.

13. Public record

Matters of public record, taken from primary sources and stated with them. Both of the records below were disclosed by the provider itself or entered in a public vulnerability register, rather than found in the press.

14. Who should avoid SafePal

Anyone who needs a named party to be answerable for a loss. The liability position is excludes liability for all loss, and the terms disclaim responsibility for every third-party service the app routes you into.

Related entries

Or read the whole wallet register, the card register, the same method applied to exchanges and to crypto casinos, the clause library at clause watch, or how this register works.

15. Sources

• SafePal Terms of Service, last updated 5 September 2024 · retrieved 2026-10-07
• SafePal Privacy Policy, last updated 16 August 2026 · retrieved 2026-10-07
• SafePal homepage · retrieved 2026-10-07
• SafePal Extension page, supported networks · retrieved 2026-10-07
• SafePal blog, TON support announcement, 17 November 2022 · retrieved 2026-10-07
• SafePal blog, Unauthorized Access To A Subset Of Customer Order Information, 16 August 2026 · retrieved 2026-10-07

Compiled by the CryptoGuardz register team. First published 2026-10-07, last reviewed 2026-10-07. Every quotation on this page is verbatim from the document named beside it. Research and drafting are AI-assisted and reviewed by a named editor before publication. Corrections: corrections.