Security and non-custodial design

Glider Labs builds Glider Ramp’s route preparation, validation and transaction-review controls. Glider Ramp prepares the request, and the user authorises it in the connected wallet.

Wallet authority

Glider Ramp does not request private keys or recovery phrases. Connection and signing are separate actions. Read each wallet request, including token approvals and spending permissions, before authorising it.

Glider Ramp validation

Glider Ramp checks the selected route and transaction details before requesting approval. A live quote is not a signed transaction. Where an updated quote is required, Glider Ramp checks it before you continue.

Non-custodial does not mean risk-free

Glider Ramp does not hold your wallet’s private keys. After you authorise a transaction, assets and permissions interact with the onchain contracts required by the selected route. Wallet control does not remove contract, network or onchain execution risk.

Validation checks

Validation checks help identify invalid requests before signing. They do not guarantee a successful outcome. Review the transaction, recipient and spending permissions each time you approve a swap.

Before signing

Confirm the source network, asset, amount and destination. Read the transaction and any spending permission shown by your wallet. Reject a request you do not understand, and never share a recovery phrase to obtain support.

See Risk and limitations for the factors that can affect a swap after approval.