Legal
Privacy
This page explains the practical privacy model for BERT: what the interface reads, which services are involved, and how operational data is handled when you use the product.
Last updated: May 21, 2026
Scope
This Privacy Notice applies to BERT web interfaces, documentation pages, and application surfaces used to interact with the protocol.
It explains practical data handling at the interface layer. It does not change the public nature of blockchain records or the transparency of onchain transactions.
What data is processed
When you connect a wallet, the interface can read your public wallet address and the public onchain state needed to render balances, proposals, rounds, treasury information, and milestone status.
The interface may also rely on standard technical request metadata from RPC providers, hosting providers, or infrastructure partners, including request logs, IP address handling, and reliability diagnostics.
Local browser storage may be used for interface preferences, cached selections, or session-level convenience features.
How data is used
Data is used to render the dApp correctly, route signed transactions to blockchain nodes, maintain operational reliability, and support security diagnostics or abuse prevention where needed.
BERT does not use this interface to take custody of your assets, private keys, or wallet secrets.
Third-party services
Depending on deployment, the interface may rely on wallet providers, RPC endpoints, hosting services, indexing infrastructure, and analytics or telemetry tools selected by operators.
Those providers process data under their own terms and privacy practices. If indexed reads are enabled, public blockchain events may be served through query infrastructure such as The Graph.
Storage and retention
Local interface state remains in your browser unless you clear it. Infrastructure logs or diagnostic records are retained according to the policies of the providers involved in the deployment.
Onchain records are public and persistent by design.
Your controls
You can disconnect your wallet, clear local browser storage, or stop using the interface at any time. Requests related to infrastructure logs should be directed to the relevant provider.
If a deployment operator runs additional offchain services, those services should publish their own operational contact details and handling policies.
Practical privacy summary
- The interface reads public blockchain state and wallet connection data needed for product operation.
- Local browser state may be used for preferences or session-level convenience.
- Infrastructure providers may process technical request metadata under their own policies.
- Onchain records remain public and persistent by design.