Skip to content

Trust & Safety

Security

StableAccount is non-custodial by design. This page explains what that means for the safety of your funds — and what you are responsible for.

StableAccount is non-custodial by design. This page explains what that means for the safety of your funds — and what you are responsible for.

Self-custody: access is tied to your login

  • You sign in via Privy, which provisions an embedded wallet. Privy manages the underlying key material within its infrastructure so that transactions can only be authorized through your login. StableAccount never holds, stores, or has access to your private keys or your funds. The security of your account depends on the security of your login method and of Privy’s infrastructure.
  • Each StableAccount is an ERC-4337 smart account (built on ZeroDev Kernel) that you control.
  • Shared accounts are Gnosis Safe multisig smart contracts governed by M-of-N approvals. The Safe — not StableAccount — controls the funds.
  • Earn balances sit in third-party protocols you deposit into directly and can withdraw from subject to available liquidity — also non-custodial.

Because funds are self-custodied, StableAccount itself does not lend out, rehypothecate, or take custody of your balance — and there is no deposit insurance of any kind, because this is not a bank deposit. This does not mean your funds are risk-free: access can still be affected by third-party providers, network conditions, sanctions/compliance screening at fiat partners, or your loss of credentials, and funds can be lost to smart-contract failure or stablecoin depeg. See Compliance & risk.

The tradeoff is real: total control means total responsibility. The rest of this page tells you exactly what that responsibility is — read it before funding your account.

What you are responsible for

Self-custody puts you in control, which also means:

  • You are solely responsible for maintaining access to your login credentials and wallet. If you lose access to your authentication method and any available recovery options, StableAccount cannot recover your funds, reset your keys, or reverse transactions on your behalf.
  • On-chain transactions are generally irreversible. You are responsible for verifying every recipient, address, @handle, amount, network, and asset before you authorize a transaction. StableAccount cannot cancel, reverse, or refund a completed on-chain transaction.

Safety of the software layer

StableAccount is built on independent software (from other companies) that its providers describe as reviewed by outside security auditors. Audits help, but they are not a guarantee — here’s the honest picture:

  • The protocols StableAccount interfaces with (ERC-4337 smart accounts, Gnosis Safe, ERC-4626 vaults, routing contracts) are built and operated by third parties. According to those providers, they have been third-party audited; StableAccount does not itself audit them or verify their audit status. Audits reduce but do not eliminate smart-contract risk. Exploits, failures, or upgrades in these contracts can result in partial or total loss of assets, and StableAccount cannot recover such losses.
  • The service depends on third-party providers (see Third parties). If any provider suffers downtime, discontinues service, or restricts access, your ability to access funds or features may be impaired. StableAccount may also be required to restrict access to comply with law, sanctions, or third-party requirements.

For the full risk picture, see Compliance & risk.

Confidential mode is not anonymity

The optional confidential mode is intended to reduce how much of the counterparty and route of a transfer is readily visible to outside observers, but it does not guarantee anonymity or make a transaction untraceable, and where confidential routing is not available it may run as a public cross-network swap (the app labels this). Do not rely on it to achieve legal anonymity. See Privacy & data.