Privacy Notice — ErgoRaffle V2
Last Updated: June 13, 2026
Version: 1.1.0
In plain language (summary — not a substitute for the full Notice below):
- No accounts, no profiles, no data sale. There's nothing to sign up for.
- You connect your own wallet; your private keys and seed phrase never reach us.
- Whatever you do on-chain (raffles, donations, gifts, refunds, claims) is public and permanent forever — no one can delete it, including us.
- The interface and its hosting may process minimal technical data (like IP address in server logs) just to work and stay secure.
- If you contact support, you may share an email or transaction ID — used only to answer you.
- Don't put personal or sensitive information into raffle content; it becomes public.
- For questions about off-chain interface data, contact raffle@rosen.tech.
This Privacy Notice explains how data is handled when you use the ErgoRaffle V2 interface (the "Interface") at ergoraffle.com and interact with the ErgoRaffle V2 smart contracts on the Ergo Blockchain (the "Protocol"). It should be read together with the ErgoRaffle V2 Terms of Service (v1.1.0).
ErgoRaffle V2 is free, open-source, non-custodial software. There are no user accounts, and the contributors who publish the code do not build identity profiles or sell your personal data. For the limited off-chain technical data processed by the official Interface, the party operating ergoraffle.com acts as a data controller (see Section 10).
1. The Core Principle: We Don't Want Your Data
- There is no sign-up, no account, no password, and no profile.
- You interact with the Protocol directly through your own non-custodial wallet.
- The contributors do not build identity profiles, do not sell or rent data, and do not run advertising or tracking-based monetization.
2. Public Blockchain Data (Not Controlled by Anyone)
Everything you do on-chain is recorded on the public Ergo Blockchain and is permanent, public, and outside anyone's control, including ours and yours:
- your wallet address(es);
- the raffles you create, the tickets (donations) you buy, the gifts you add;
- refunds, claims, amounts, tokens, NFTs, and timestamps.
Anyone in the world can read, copy, index, and analyze this data forever. This is an inherent property of public blockchains, not a feature of the Interface. The contributors cannot edit, hide, anonymize, or delete on-chain data.
3. Data the Interface May Process
To render the Interface and build transactions, your browser may process or transmit the following. Where this happens it is to make the Interface function, not to identify you:
- Wallet connection data — when you connect a wallet, the Interface reads your public address and balances to construct transactions. Your private keys and seed phrase never leave your wallet and are never seen by the Interface.
- Public node / explorer requests — the Interface queries public Ergo nodes or explorers to read chain state and broadcast transactions. Those third-party endpoints may independently log technical request data (such as IP address) under their own policies.
- Basic technical/hosting logs — the service hosting the Interface (and any CDN) may automatically record standard request metadata such as IP address, browser/user-agent, and timestamps for security, abuse-prevention, and reliability. These logs are not used to build user profiles.
- Error and performance monitoring (Sentry). The Interface uses Sentry to capture crash reports and performance diagnostics so we can find and fix bugs. When an error occurs, Sentry may collect technical data such as IP address, browser and device information, the page and actions leading to the error, and a stack trace. This is used only for reliability and security, not advertising or profiling. Sentry processes this data under its own privacy terms.
- Bot protection (Google reCAPTCHA). The Interface may use Google reCAPTCHA to prevent abuse and automated attacks. reCAPTCHA collects hardware and software information and interaction data, and may set cookies, which are sent to and processed by Google under Google's Privacy Policy and Google's Terms of Service. Use of the Interface is subject to those Google terms where reCAPTCHA is active.
- Local browser storage — the Interface may store non-identifying preferences (such as theme or last-used settings) locally in your browser. You can clear these at any time.
- User content you submit — any title, description, link, or image you attach to a raffle is published through the Interface and, where applicable, on-chain or via linked storage, and becomes public. Do not include personal or sensitive information in raffle content.
- Support requests (optional). If you choose to contact support — for example, if an automatic refund does not arrive — you may voluntarily provide information such as an email address, a transaction ID, or a wallet address. This is used solely to respond to your request, is not used to build a profile, and is retained only as long as needed to resolve the matter. Support may be offered through a third-party platform (for example, Telegram or Discord); if so, that platform processes your messages and account data under its own privacy practices, which we do not control. Share only what is necessary, and do not include sensitive personal data.
Legal basis and retention. The legal basis for processing the technical/hosting, Sentry, and reCAPTCHA data above is the controller's legitimate interest in the security, abuse-prevention, and reliability of the Interface. These logs are retained only as long as needed for those purposes (typically no more than 90 days) and are then deleted or aggregated. Support-request data is retained only until the matter is resolved.
4. What We Do Not Collect
- No names, emails, phone numbers, or postal addresses (unless you voluntarily place such information into public raffle content — which you should not do — or provide it when contacting support).
- No KYC/identity documents.
- No private keys, seed phrases, or wallet credentials.
- No payment-card or bank data — the Protocol uses on-chain assets only.
5. Cross-Chain Interactions (e.g., BTC and Runes)
If you use cross-chain payment paths, your transactions are also recorded on those external networks (such as Bitcoin) and processed by third-party watchers, bridges, or proxy mechanisms. Those networks and services are independent and govern their own data handling. The same public-and-permanent principle applies to data recorded on them.
6. Third-Party Services
The Interface relies on independent third parties — for example, your wallet provider, public Ergo nodes and explorers, hosting/CDN providers, Sentry (error monitoring), Google reCAPTCHA (bot protection), any support platform we adopt (for example, Telegram or Discord), and any cross-chain watchers. Each operates under its own privacy practices, which the ErgoRaffle V2 contributors neither control nor are responsible for. Review their policies directly.
7. Cookies & Tracking
The Interface does not use advertising or marketing trackers and does not sell data. Storage it sets directly is functional (see Section 3). However, Google reCAPTCHA may set its own cookies and Sentry may set or read identifiers for the purposes described in Section 3; these are governed by those providers' policies. Where reCAPTCHA or any other non-essential technology sets cookies, the Interface will present a consent mechanism where required by applicable law (for example, EU/UK ePrivacy rules) before those cookies are set. If we add or change such technologies, this Notice will be updated.
8. Your Choices & Rights
- On-chain data cannot be erased. Because blockchain records are immutable and public, no one — including you or the contributors — can delete, rectify, or recall them. Consider this carefully before transacting.
- Off-chain data. For the limited technical/hosting, Sentry, reCAPTCHA, and support data described above, applicable data-protection laws in your region may give you rights such as access, correction, or deletion. You can exercise these by contacting raffle@rosen.tech (see Section 11). Some logs are also held by the relevant hosting or third-party provider under their own policies.
- Wallet privacy. Your on-chain privacy is largely in your hands — for example, by choosing which addresses you use. Treat your wallet address as public.
9. Children
The Protocol and Interface are not intended for anyone under 18, or the age of majority in their jurisdiction. Do not use ErgoRaffle V2 if you are below that age.
10. Who Is Responsible (Controller Status)
- Public on-chain data (Section 2). No one is a data controller of the public blockchain — it is permanent and outside anyone's control. Consistent with the Terms of Service, ErgoRaffle V2 is published as free, open-source software and autonomous smart contracts, and the contributors do not operate the Protocol as a service.
- Off-chain interface data (Section 3). For the limited off-chain technical data processed by the official Interface (hosting/CDN logs, Sentry, reCAPTCHA, and support requests), the party operating ergoraffle.com acts as a data controller for that narrow processing and is responsible for it as described in this Notice.
- All use, and all consequences of public on-chain disclosure, remain the sole responsibility of the User who transacts.
11. Contact & International Transfers
- Contact. For questions about this Notice, or to exercise data-protection rights over off-chain interface data, contact: raffle@rosen.tech.
- International transfers. Sentry and Google reCAPTCHA may process data outside your country, including in the United States, under their own safeguards (for example, Standard Contractual Clauses or equivalent mechanisms). On-chain data is inherently global and public.
12. Changes to This Notice
This Notice may be updated by posting a revised version to the Interface or the code repository with a new "Last Updated" date. Continued use after changes constitutes acceptance.
ErgoRaffle V2 is free, open-source, non-custodial software. This Notice is not legal advice.