Privacy

Data used by the service

• A public EVM address entered manually or obtained from a connected wallet.
• In signature mode, the Web3 identity and authentication session created after signature verification through Supabase Auth.
• Technical web-request data required by hosting and authentication infrastructure to deliver and protect the service.
• Language and interface-brand preferences stored in cookies.

Two access modes

In address-entry mode, the server keeps the selected public address in an HttpOnly session cookie so Portfolio and project navigation can use it. This does not prove ownership of the address.

In signature mode, the service creates a short-lived challenge and asks the wallet to sign a Sign-In with Ethereum message. After verification, access/refresh session tokens are stored in HttpOnly cookies; the refresh session is configured for a maximum of 30 days.

Infrastructure

The current service is hosted on Vercel and uses Supabase for authentication and server-side data infrastructure. The server also uses external blockchain and market-data sources when needed to build portfolio information.

Cookies

• An HttpOnly cookie may store the selected public address in address-lookup mode.
• HttpOnly access/refresh cookies are used for the wallet-authentication session in signature mode and are unavailable to normal page JavaScript.
• Language and brand cookies remember the selected interface preferences.

Not collected for sign-in

• Seed phrase.
• Private key.
• Permission to move assets.
• A blockchain transaction or gas payment solely for authentication.