Security

Security Model

Last updated: 19 September 2026

PoolPort is a non-custodial tool. Your seed phrases and private keys are the highest-value secret in the flow, and the design of the Service assumes they will be treated as such: they never leave your browser, and no server we operate ever receives them.

1. What runs where

All key material — mnemonics, private keys, and derived signing objects — exists only in your browser's memory for the duration of a preview or migration. Nothing is written to disk, localStorage, sessionStorage, or IndexedDB. Refreshing the page clears everything.

The only things that leave your browser are:

2. How to verify

You do not need to trust our word for this. The Service is designed to be independently verifiable:

3. Threat model

We defend against the following:

We do not defend against:

4. Sponsorship key handling

To sponsor gas on wallets that cannot pay for their own migration, the operator holds funded wallets on several chains. Those keys live in Cloudflare's encrypted secret store, are only accessible to the worker at request time, and are never included in the client bundle or served to a browser.

The sponsor wallets are operationally separate from the fee wallets that receive the migration fee. Sponsor keys are hot wallets with a small float, topped up periodically and never used to hold revenue.

5. Reporting a vulnerability

If you believe you have found a security issue, please email security@poolport.xyz. Do not open a public issue, and do not test against wallets holding funds you do not control.

We will acknowledge reports within 72 hours and aim to have a fix or mitigation deployed as soon as reasonably possible. If you would like credit in a future release note, tell us how you want to be named.

6. Operational practices