Gizlilik.

What we store

• Wallet addresses and their $BRICS balance history, read from public chains.
• What you sign: linked wallets and your tower name, with the signed message.
• One strictly necessary session cookie, brics_session, while you are signed in. It lasts 14 days.
• A few product events of our own, like a renamed tower, tied to your holder id.
• If you turn on notifications, the address your browser's push service gives us, or in the iOS or Android app, that install's push token. Turning them off deletes it.

What we don’t

No names, emails, phone numbers, ID documents, advertising IDs or outside trackers. There is no cookie banner because there are no optional cookies.

Your browser keeps one small note of its own, brics.wallet, when you sign in with a phone or email wallet: which kind of wallet it was, so the dashboard can find it again after a reload. It never leaves your browser and is cleared when you sign out.

What is public

Towers, tower names and the $BRICS balances behind them are public, because that is what lets anyone check a tower against the chain.

Linked wallets are public. A tower shows the wallets it is built from, so wallets linked to one holder are published together and anyone can see they belong to the same holder. That is what lets anyone check every tower against the chain. If you need a wallet kept apart from your others, do not link it.

What stays private: your Telegram and push settings. They are only ever shown to you.

Processors

Vercel hosts the site, Fly.io the API and Neon the database. Robinhood Chain RPC providers receive the queries needed to run the protocol. Errors may go to Sentry without personal data.

Connecting a wallet

A wallet in your browser talks to this site directly. Two optional ways to connect go through others:

• WalletConnect (run by Reown) carries the connection between this site and a wallet app on your phone, end to end encrypted. Opening the connect sheet on the dashboard reaches its relay to prepare a connection code. The relay sees your device's IP address and when encrypted messages pass, not what they say. Reown's privacy policy applies.
• The email wallet (Reown, with Magic for key management) makes a wallet from your email address. Reown receives your email and keeps the wallet's key under its own privacy policy and terms. Brics never receives your email and never holds the key; it sees your wallet address and the messages you sign, as with any wallet.

The email wallet is contacted only when you pick it. A browser that never opens the connect sheet contacts neither.

Notifications, only if you turn them on: in the iOS app they go through Apple Push Notification service, in the Android app through Google's Firebase Cloud Messaging, and in a browser through that browser's own push service (Google, Mozilla, Apple or Microsoft). Each receives your device's push token or address and the notification itself, such as a public alert. Nothing else is sent.

Buying with a card

Card purchases on the buy page happen on the provider's own site, today MoonPay. It takes your card and any identity checks under its own privacy policy and terms, and sets its own fees, limits and availability. Brics never sees or stores your card or identity details.

To start a purchase, the page sends our API the link it built: your wallet address, the asset and the amount. The API signs that link so the provider knows the address came from this site, and returns it. It is not stored. The provider then delivers straight to your wallet; Brics never holds the money.

Export and deletion

Write to hello@bricsfinance.fun and we will send you everything tied to your holder. Records on a public chain can’t be erased, but we can clear your tower name.

Law

Norwegian law applies. The operator of bricsfinance.fun is responsible for this processing.