Skip to content

DraftThis text describes what the system does today, derived from the code, and is pending legal review.

Security

How your account and your data are protected today. Only what the system already does.

Non-custodial and read-only

PortCodex only reads public addresses. It does not store private keys or recovery phrases, does not connect to your wallet and signs nothing on your behalf: it cannot move your funds. If you paste something shaped like a private key or a recovery phrase when adding a wallet, the server rejects it.

Where the data is

The database, the API and background jobs run on a Netcup server in the European Union; the identity provider is in Ireland (Supabase). The web application and this site are static files served by Vercel, a US company; your account data goes from the browser straight to the API, without passing through Vercel. The database can only be reached from the internal network of that server, and the connection to the identity provider is encrypted with TLS. What each provider receives is set out on the Privacy page.

The session

When you sign in, your browser receives a single __Host- cookie with HttpOnly, Secure and SameSite=Strict: the page's code cannot read it and another site cannot make it travel. The database stores only its fingerprint, not the cookie itself, and ending a session cuts it off on the next request. Every request made with your session that changes something also requires an anti-CSRF token.

Signing in

Every sign-in asks, besides your password, for a one-time code: the one sent to your email or, if you turned on the authenticator app, the one from the app. We email you about every new sign-in and every password change, and also when a change of your email address is requested. Administration of the service also requires a TOTP code from an authenticator app.

Security headers

This site and the application are served over HTTPS only (HSTS), with a content security policy that allows only their own scripts and styles, without unsafe-inline, and they cannot be embedded in another page. The API answers with the tightest possible policy (default-src 'none') and forbids caching its responses.

What is done with your personal data, and how to close your account, has its own page: Privacy