Compliance

Every route is screened.

Compliant privacy: the destination is unlinked from your wallet, but every deposit is screened by a partner exchange and every request passes a geo gate. These rules are enforced in code, not in a policy PDF.

Geo-block

Requests from CU, IR, KP, SY, RU, BY and the occupied regions of Ukraine are refused at the edge (Vercel x-vercel-ip-country / region). Enforced before any quote.

Tor exit nodes

Best effort: upstream Tor signals are refused. A header check cannot see every exit; partners run their own screening on the deposit.

Per-order cap

Each private order is capped by the partner's quote max, and by a PROPOSED cap of $60,000 equivalent.

Partner screening

Every private route goes through a partner exchange that runs AML / OFAC screening on the deposit. Flagged deposits are held by the partner for KYC or refunded.

No pooled funds, no custody, no exceptions

SEALED never holds funds. Your transaction goes from your wallet to a bridge contract and then to a partner deposit address. There is no shared pool, no mixing, no SEALED-controlled key.

No pooled funds, no custody, no exceptions.

A route moves your funds from your wallet straight to a one-time partner deposit wallet on Robinhood Chain. The partner clears through a screened exchange and delivers. At no point is there a shared pool, a SEALED-controlled key, or a way for us to move funds. That is the whole design, and it is why this is not a mixer.

Blocked countries

CU · IR · KP · SY · RU · BY

+ Crimea, Donetsk, Luhansk, Kherson, Zaporizhzhia regions

Enforcement point

edge proxy · before any route

Vercel x-vercel-ip-country / region headers. API answers 451.

Partner screening

AML · OFAC · on every deposit

Flagged deposits are held for KYC or refunded by the partner.

reading route