Skip to content
Security and privacy

What we hold and never hold

Port_ can read and cannot move. This is what it keeps about you, what it never has, and how the few sensitive things it holds are kept.

  • A private key, a seed phrase or your funds. Port_ cannot send, sign or approve anything on any chain, and nothing in it will ever ask for a seed phrase.
  • A signature made on your behalf. We never produce one.
  • Your card number. Paddle takes payment as merchant of record and holds the card. We keep your Paddle customer id; the id, status, price and renewal date of your subscription; the card’s brand and last four digits, so the billing page can say which card will be charged; and your receipts.
  • An exchange key we can see is able to trade or withdraw. Where the exchange lets us ask, it is asked what a key can do before anything is written, and a key that can do more than read is refused and never stored. Gate and Crypto.com publish no way to ask, so their keys are accepted, marked unverified, and left to you to check. See Exchange keys.
  • Your account: your email address, the name you give, and a hashed password if you set one.
  • Your sign-ins: the time, IP address and browser of each, so the account stays secure and Settings can show you where you are signed in.
  • Your port: the public addresses you add and everything you attach to them, such as nicknames, notes, groups, pictures, goals, alert rules and your settings. It is stored on our servers so every device you sign in on shows the same port. Nobody outside Port_ can see which wallets are on your account.
  • Exchange connections: the key you pasted, encrypted, plus its last four characters so you can tell your connections apart. Coinbase is connected by signing in to Coinbase instead, and the access it grants is kept the same way, once that sign-in is switched on; it is not yet.
  • Keys you make for the Port_ API: a hash of each key, never the key itself. You see a key once, when you make it.
  • Apps you connect by signing in, such as Claude or ChatGPT: the name the app gave itself and where it sends you back to, what you allowed and when, and the tokens it uses to keep reading. Disconnecting it, or resetting your password, deletes them.

A quick look on a pasted address needs no account. The address is kept in that browser tab for as long as it is open, and addresses you look up without an account are not stored against you.

  • Analytics are off until you turn them on, in Settings › Privacy & your data. When they are on they use no cookies, an anonymous id that lasts only for that tab, and route names rather than addresses.
  • Error reports have every wallet address, token contract, email address, ENS or .sol name and credential replaced before they leave your browser or our server, and no account id travels with them.
  • What you do in the app is recorded against your account, whatever the analytics switch says: which pages you open, and that you added a wallet, took an export or wrote an alert rule. These are event names and counts, never an address, a token, an amount or a name.
  • Our own request counters hold no identity: no account, email, address, IP or device fingerprint, whether or not analytics are on.
  • Exchange credentials are sealed with AES-256-GCM before they reach the database. The key that opens them lives in the server’s environment and nowhere near the data. GCM authenticates as well as encrypts, so a stored row that somebody altered fails to open rather than opening to something else.
  • A server that cannot seal a key refuses it. If the encryption key is missing, connecting an exchange fails with an error rather than storing anything in the clear.
  • A credential is never sent back out. Nothing Port_ answers carries a stored credential, not even to you: a connection is described by its exchange, its label and those last four characters.
  • Backups are encrypted and kept with a different provider from the servers, and purged after 30 days.

Settings › Privacy & your data deletes your account. It leaves the live database at once. A copy of the rows you entered is kept in an archive for 30 days, in case the deletion was a mistake, then purged, and backups older than 30 days are deleted. What the chains themselves record is public and outside anybody’s control: we delete our copy of it, not the chain’s. Taking your data out first is covered in Your data.

The policies are in the app, and they are the version that binds:

Privacy questions and requests go to [email protected].