repodaofi Privacy Policy — Draft
Last updated: 4 September 2026 Status: Requires project-owner and legal review before production publication
1. Overview
This Privacy Policy explains information that may be processed when you visit repodaofi, connect a wallet, verify wallet control, view a participation record, submit an optional transaction, or open a proof link.
2. Public blockchain information
Wallet addresses, contract addresses, transaction hashes, values, blocks, timestamps, and contract state may be public. Disconnecting a wallet from the website does not delete public blockchain records.
3. Wallet connection and signatures
repodaofi may receive your public wallet address and a signature created in your wallet for the limited purpose described in the request.
repodaofi does not need or request your seed phrase, private key, wallet password, recovery phrase, or keystore file. Never provide those credentials to anyone claiming to represent repodaofi.
4. Application records
The service may process:
- public wallet address;
- one-time nonce and expiration;
- signature-verification result;
- session identifier;
- base and Boost status;
- Points total;
- transaction hash, amount, block, and confirmation time;
- security and availability logs.
5. Browser storage
To recover a pending transaction after refresh, repodaofi may store limited data in your browser:
- wallet address;
- network identifier;
- transaction hash;
- contract address;
- action type;
- submission time.
Browser storage must not contain private keys, recovery phrases, signatures, server secrets, or authentication cookies.
6. Service providers
Requests may be processed by wallet providers, RPC providers, explorer services, database providers, Vercel, domain providers, content-delivery services, security services, and other infrastructure actually enabled for the product. These providers may process technical information under their own policies.
7. Analytics and cookies
Non-essential analytics and cookies should remain disabled unless they are configured and disclosed. The product must not intentionally send seed phrases, private keys, signatures, full wallet addresses, or wallet balances to an analytics provider.
8. Data minimization
The first release does not require legal names, home addresses, passport scans, identity-card scans, biometric templates, phone numbers, or private repository credentials.
9. Public account views
An Account page or shareable proof may display public wallet and transaction information. A wallet record does not prove a person's legal identity, uniqueness, residence, age, reputation, or ownership of external accounts.
10. Retention
Public blockchain information remains according to the rules of the relevant network. Browser-stored pending data remains until cleared by the application or user. Server-side retention periods must be finalized before production and documented in the deployed policy.
11. Security
No website, wallet, network, RPC provider, smart contract, database, or hosting service can be guaranteed completely secure. Use a trusted device, verify the website domain, review wallet prompts, and protect recovery credentials.
12. International processing
Infrastructure providers may process information in countries other than your own. Applicable safeguards and provider terms may vary.
13. Your choices
You may choose not to connect a wallet, not to sign, and not to submit the optional transaction. You may clear browser storage through your browser settings. Clearing browser storage does not remove public blockchain records.
14. Changes
This policy may change as the product, infrastructure, or legal requirements change. The effective date should remain visible.
15. Contact
Publish a contact email only after the project owner supplies and verifies a real address.