What we never hold, and never see

Funds

We never take custody of your assets. Not at any point in a transfer, and not on either route.

On the contract-less route your funds go to the routing provider's deposit address, and the destination asset is delivered to the address you named. BlockSquad isn't a hop in that path. There's no balance here to lose, freeze or misappropriate.

On the smart-contract route your wallet signs a transaction against the router directly. There's no intermediate account, and no approval left behind that would let us move funds later.

Identity

There's no registration, so there's no name, email address, password or identity document to collect. Nothing is asked, so nothing is stored, so nothing can be breached or handed over.

What does exist is a recovery key, generated locally in your browser. It's a lookup handle for your own transfer history and it controls no funds whatsoever. Anyone holding it can see which transfers were made from that browser. Nobody holding it can move anything.

Order links are capabilities

An order id is a hash of the provider's transfer id combined with your recovery key. Holding the link is the proof that you're entitled to read that order, which is what lets an order page work with no login.

So treat an order URL like a receipt you wouldn't post publicly. Anyone with the link can read that transfer's status and amounts. They still can't move funds, redirect a delivery, or reach anything else in your history.

In the browser

The site sends HSTS, stops the browser second-guessing declared content types, and withholds camera, microphone, geolocation and payment permissions it has no use for. It also restricts who's allowed to frame it.

Referrer information is trimmed to the origin whenever you navigate to another site. That one is deliberate: order URLs are capabilities, and this keeps them out of a Referer header sent to a third party.