Privacy Policy
Updated 19 September 2026
Merchant accounts, hosted checkout and payment-linked escrows are covered by the Payments Privacy notice. Those services store account and payment records; the account-free description below applies to the standalone wallet interface.
This page explains the standalone escrow interface, its forms and notification service, and the public records created when you use it.
Wallet access and escrow forms
The standalone escrow interface uses a self-custodied wallet rather than a merchant account. Escrow forms also ask for party names, contact emails and agreement details. These are self-declared details, not verified identities. We never need your wallet private key or recovery phrase.
What we collect
The escrow notification service stores pending invitations, subscriptions and delivery state in Cloudflare KV and sends messages through Resend. Both parties receive updates about the escrow from the moment it is created, because money is at stake; no confirmation step is required, and every email carries an Unsubscribe link that stops them with one click. The app also keeps wallet preferences and transaction recovery hints in browser storage.
Like any website, our host (Cloudflare) may process standard technical request data such as IP address and browser type for security and to serve the site. We do not use this to build profiles of you.
On-chain data is public and permanent
Escrows run on the public networks supported by the app. Wallet addresses, amounts, token types and escrow events are visible to others and cannot be erased by Vaultion. Treat any wallet address you use as public.
Deal terms are public; dispute evidence depends on the method
Deal terms are not private and not encrypted. On Ethereum, Base, Arbitrum and TRON, the deal title and description you enter are pinned to IPFS through Pinata, unencrypted, and linked from the escrow so the applicable reviewers or jurors can read them. Anyone with the link can read them, and IPFS content can be copied and retained independently. Do not enter anything in the title or description that you are unwilling to make public. If an agreement must stay private, keep the on-site description generic and keep the full text between the parties.
Dispute evidence: on Vaultion-assisted escrows, the statements and files you submit are stored privately in our evidence store and are readable only by the two parties (after a wallet signature) and by Vaultion's reviewers. They are not published to IPFS or the blockchain; only a cryptographic fingerprint of the evidence set is recorded with the ruling. On Kleros escrows, evidence is pinned to IPFS through Pinata and is public, because Kleros jurors must be able to read it.
Party names and contact emails entered in the escrow form are not published to IPFS or the blockchain. They are stored for escrow notifications and are not shown publicly.
Third-party services
Using Vaultion involves your wallet and RPC providers, the selected blockchain, Cloudflare hosting and storage, Pinata/IPFS, Resend for escrow notifications, and the dispute process selected for that escrow. Kleros applies only where it is offered and selected. These services have their own terms and privacy practices.
Your control
You choose which wallet to connect and what agreement or evidence to submit. Funds committed to escrow are governed by its contract and dispute terms. Contact [email protected] about access, corrections, notification preferences or deletion of service records; we verify your authority before disclosing or changing them. Public blockchain and independently replicated IPFS records cannot be deleted by Vaultion.
Changes
We may update this policy as the product changes. Material updates will be reflected here with a new effective date.
Contact
Questions about privacy? Email [email protected].
