Website information · Draft dated 20 October 2026
Privacy Policy
This notice explains what the Monzero website and its optional services do with information. Transaction privacy on the blockchain does not make visits to this website anonymous.
Scope and contact
This notice covers monzero.org and the project services described here. External community platforms, exchanges, independent pools and node operators have their own practices. The site is maintained under the Monzero project name. Its operator's legal identity and country are not publicly disclosed; no incorporated company is claimed here.
For a privacy enquiry, use the existing project contact security@monzero.org, with “Privacy enquiry” in the subject. Do not put personal information in a public GitHub issue or community message. Never send wallet seeds, private keys, passwords or authenticator secrets.
Information used and why
- Visiting pages and using APIs. Requests expose an IP address, browser information, requested URL and time to the serving infrastructure. These can appear in hosting or security logs. Addresses or searches placed in a URL can also appear in browser history and server logs.
- Faucet accounts. The service stores an email address, a password hash, authenticator setup information, account status, login times and payout address. Claim records connect the account with the payout address, amount, outcome and transaction identifier. It uses keyed hashes derived from client IP addresses and payout addresses to limit abuse. These records support sign-in, email verification, account recovery, claim limits and payouts.
- Community voting. Votes are linked to a signed-in faucet member, a poll, the selected option, a timestamp and an abuse-prevention client hash. Published results are aggregate counts. A vote is not anonymous to the service operator.
- Mining tools. A wallet address submitted to the dashboard is sent to the site's API and used to query the pool. Voluntary miner reports supply a miner identifier and performance information; opted-in history supports public leaderboards. Public node observations support the network map. Do not submit an identifier you need to keep private.
- Telegram services. Optional alerts associate a Telegram chat ID with watched mining addresses, labels, alert preferences and recent alert state. Joining through the verification bot also uses Telegram user and chat identifiers and a short-lived verification token.
- Administration and correspondence. Authorised administrator accounts store login details, permissions and activity records. Messages and contributions contain whatever you choose to provide and are used to respond or maintain the project. Do not include unnecessary personal information.
Account and claim checks can automatically refuse a request because verification is incomplete, a cooldown or funding limit applies, or a bot check fails. Community voting also checks account eligibility. Contact the project if a refusal appears incorrect. You can browse public documentation without creating an account.
Cookies and browser storage
The website's current source does not include an advertising or analytics script. This is not a promise that the hosting provider or an external service keeps no logs.
- Sign-in cookies: the faucet and administration areas use secure, HTTP-only session cookies to recognise signed-in users. Server-side sessions expire after 30 minutes of inactivity, with an overall maximum of 12 hours for the faucet and 8 hours for administration. Signing out clears the relevant session.
- Upgrade notice: choosing “Hide” stores a timestamp in your browser to suppress the notice for 24 hours. The stored timestamp can remain until site data is cleared or replaced.
- Studio drafts: saved drafts stay in this browser's local storage. The browser-based preparation tool does not upload those drafts as part of saving them.
- Worker labels: the mining dashboard saves personal labels locally only when you choose to save them. Use “Forget saved labels” or your browser's site-data controls to remove them.
Clearing site data removes local drafts and preferences and can sign you out. It does not delete server-side accounts, payout records or blockchain transactions.
External services and public information
The homepage loads its directory badge from Chainquiry. That request sends your IP address and ordinary browser request information to Chainquiry even if you do not follow the link. The homepage badge is requested without a referrer header. Its sponsored directory profile is not a security assessment.
Where the faucet displays Cloudflare Turnstile, Cloudflare processes connection and browser signals to distinguish people from bots. Cloudflare also describes processing to improve its detection service. Read the Turnstile Privacy Addendum for its roles and practices.
Hosting and email providers process information needed to deliver the site and account messages. Pool queries and Telegram requests pass the relevant address or chat information to those services. External links to GitHub, X, Telegram, Bitcointalk, Chainquiry and blockchain explorers take you to separately operated services. Their providers may process information in other countries; the operator must confirm the applicable provider locations and transfer arrangements before this notice is finalised.
Donation addresses, public-chain transactions, submitted public content and published network observations can be viewed and copied by others. Blockchain records are maintained by network participants and cannot simply be removed by deleting a website account.
Retention and deletion
The implemented session limits above apply to authentication. Faucet rate-limit records older than 48 hours and administrator login-failure records older than 24 hours are cleaned during subsequent service activity. These limits do not describe hosting logs or account retention.
Opted-in miner history uses a rolling 30-day window; a subsequent report without the history flag removes that miner's saved history. Telegram alert subscriptions can be removed with /stop all; this removes the website's subscription records, not copies of messages held by Telegram.
The application does not currently impose an automatic expiry on all accounts, claim records, votes, correspondence or audit records. Some security logs are append-only. A documented schedule for these records, hosting logs and backups remains to be confirmed. No automatic account-deletion or fixed log-retention promise is made here.
Your choices and privacy requests
You can avoid optional accounts, alerts and miner reporting, clear browser storage, and stop Telegram subscriptions. Contact security@monzero.org to request access, correction or deletion of information about you, or to raise an objection to its use. Explain which service and records are involved without sending secrets. The operator may need proportionate verification before releasing or changing account data.
Depending on the law that applies, you may also have rights to restrict processing or receive a portable copy of data. Where processing relies on consent, you can withdraw that consent without affecting earlier lawful processing. Rights and exceptions depend on the processing involved; a request cannot erase a distributed blockchain.
You may complain to the relevant data-protection authority. For UK matters, see the Information Commissioner's Office. The final notice must identify the applicable lawful bases and any additional local contact details.
Updates
The date at the top records this draft. Changes to providers, data use or retention should be reflected here before the relevant practice changes. See also the Website Terms and security disclosure guidance.