Privacy Notice
What personal data MiroBall processes, who it goes to, why, and the rights you have over it. Includes the part most crypto products leave out: what a public blockchain does to your right to erasure.
Effective 8 October 2026. Last updated 8 October 2026.
1. Who is responsible
The controller for the personal data described here is the operator of MiroBall. Privacy requests go to https://github.com/NurstarK/miroball/issues.
We have not appointed a Data Protection Officer, as we are not required to.
2. Scope
This notice covers miroball.com. It does not cover the third parties the site depends on, each of which is an independent controller for its own purposes and has its own notice: Privy, Stripe, MoonPay, ESPN, MiroShark, and our host. Links are in §5.
3. You can use most of MiroBall without giving us anything
Browsing the fixtures board requires no account. We set no analytics, no advertising and no tracking cookies, and we run no analytics product at all. If that changes, this notice changes first and a consent banner appears before any non-essential cookie is set.
Personal data would enter the picture in two places: signing in, and paying for a simulation. Neither is possible on miroball.com today — there is no sign-in and no payment — so in practice the only personal data we currently process is the technical data described in §4, and the account, payment and blockchain entries there describe what happens if and when those features are switched on.
4. What we process, and why
Account data — if you sign in. Email address, or Google account identifier and the email attached to it; the public address of the wallet Privy creates for you; and a Privy user identifier. Purpose: to let you sign in, hold a wallet and pay for a run. Legal basis: performance of a contract (GDPR Art. 6(1)(b)). Note that this data lives primarily in Privy's systems; the MiroBall server reads your wallet address in order to construct a payment and check the balance covers it.
Payment and transaction data. Your wallet address, the amount, the time, the transaction identifier, and the fixture the run was for. Purpose: to deliver the run you paid for, to link a report to the person entitled to it, and to keep records. Legal basis: contract, and our legitimate interest in keeping accurate records of what we sold (Art. 6(1)(f)). See §6 — this data is published on a public blockchain.
Simulation data. The fixture chosen, the generated prompt, whether deep research was selected, and the resulting run identifier and report. Prompts are composed by us from public fixture data and contain no personal data about you. Purpose: to produce and serve your report. Legal basis: contract.
Technical data. IP address, user-agent, request path and timestamp, in ordinary server logs, plus error diagnostics. Purpose: to operate the site, debug it and defend it against abuse. Legal basis: legitimate interest in a functioning, secure service (Art. 6(1)(f)).
Correspondence. Anything you send to our contact addresses. Purpose: to answer you. Legal basis: legitimate interest, or contract where it concerns a run you bought.
We do not process special-category data, we do not profile you, and we take no automated decision about you with legal or similarly significant effect.
5. Who receives it
| Recipient | Role | What reaches them | Where |
|---|---|---|---|
| Privy | Authentication and non-custodial wallet provider; independent controller | Email or Google identity, wallet address, session data | US |
| Fly.io | Hosting | Everything the server handles, including log data | EU (Amsterdam) |
| MiroShark | The simulation engine; independent controller | The prompt, the run identifier and our affiliate address. Not your identity or your wallet address | Third party |
| ESPN / Disney | Source of fixtures, odds and crest images | Your IP address and user-agent, because crest images load directly from ESPN's CDN into your browser | US |
| Stripe, MoonPay | Card and bank onramps, reached through Privy; independent controllers | Whatever their own KYC requires. We never see it | US / global |
| Base network and x402 facilitator | Public blockchain settlement | Wallet addresses, amount, timestamp — publicly and permanently | Public |
On the crest images specifically: every crest you see is fetched from a.espncdn.com by your own browser. That request carries your IP address and user-agent to ESPN, and we cannot prevent it without removing the crests. We have no visibility into and no control over what ESPN does with it. If this matters to you, a content blocker scoped to that host will stop it, and the site remains usable.
We do not sell personal data and we have never disclosed any to a third party for consideration. We may disclose data where legally required, or to establish or defend a legal claim.
6. Blockchain data cannot be erased, and you should decide knowing that
Payments settle on Base, a public blockchain. This has consequences no privacy notice can engineer away, so we state them plainly:
- Your wallet address, the amount, the timestamp and the recipient become permanently and publicly visible to anyone in the world, with no access control.
- We cannot delete, alter, correct or restrict it. Nobody can. There is no erasure, rectification or restriction available over a confirmed blockchain record, and your GDPR rights under Articles 16, 17 and 18 cannot be satisfied in respect of it — not because we decline, but because the record is outside any single party's control.
- A wallet address is pseudonymous, not anonymous. Anyone who can connect your address to your identity — because you funded it with a card, posted it publicly, or reused it elsewhere — can see every MiroBall payment you have ever made, and everything else that address has ever done.
Our legal basis for this processing is the performance of your contract: there is no way to deliver a paid x402 run without an onchain payment. If that trade is unacceptable to you, the remedy is not to pay for a run.
7. International transfers
Several processors are in the United States. Where personal data leaves the EEA or UK we rely on the European Commission's adequacy decision for the EU–US Data Privacy Framework where the recipient is certified, and otherwise on Standard Contractual Clauses. You can ask us at https://github.com/NurstarK/miroball/issues which applies to a given recipient. Public blockchain data has no destination and therefore no transfer mechanism — it is globally readable by design, which §6 covers.
8. How long we keep it
- Server and error logs: up to 90 days, then deleted.
- Payment and run records: up to 7 years, to meet accounting and tax obligations and to defend claims.
- Account data: held by Privy for as long as your account exists; deleting your Privy account removes it there.
- Correspondence: up to 2 years after the matter closes.
- Blockchain records: permanent and beyond anyone's control (§6).
9. Your rights
If the GDPR or UK GDPR applies to you, you have the right to access your data; to have inaccurate data corrected; to have data erased; to restrict or object to processing based on legitimate interests; to data portability; and to withdraw any consent you have given. Exercising them is free and we will respond within one month.
Write to us at https://github.com/NurstarK/miroball/issues. We may need to verify who you are before acting, which for an account request usually means replying from the address you signed up with.
Two honest limits: data held by Privy as its own controller is best addressed to Privy directly, and §6 applies to anything onchain.
You can complain to a data-protection supervisory authority — the one where you live, where you work, or where you believe the problem occurred.
10. Children
MiroBall is for adults. The service requires you to confirm you are 18 or over, and we do not knowingly process the data of anyone under 18. If you believe a child has used the service, write to us at https://github.com/NurstarK/miroball/issues and we will delete what we hold.
11. Cookies and local storage
We set no cookies of our own. Two kinds of browser storage are used, both strictly necessary, so no consent banner is required:
- Your skin choice. A
miroball:modekey in localStorage remembers whether you chose derby mode, so you land on the right page. It identifies nothing about you and never leaves your browser. - Your Privy session. If you sign in, Privy stores a session so you stay signed in. See Privy's own notice for the detail.
12. Security
The site is served over HTTPS. The server holds no private key able to move your funds, no card details and no password — architecture that removes whole categories of breach rather than mitigating them. We cannot guarantee security, and no service can. If you believe you have found a vulnerability, report it at https://github.com/NurstarK/miroball/issues and please give us a reasonable chance to fix it before disclosing it.
13. Changes
Material changes will be posted here with a new "last updated" date before they take effect, and announced on the site where the change affects data we already hold.