Short version: the in-browser toy miner and the lesson run entirely on your own device, and nothing you type there ever leaves it. We use Google Analytics only to count visits and see which pages help people, with all advertising features switched off. Personal data comes into play only when you sign in with Google to have a real block struck. Then we store your inscription request and the resulting public block, and nothing more.
1. Free in-browser mining: your text stays on your device
When you use the free miner or the interactive lesson, the work runs locally in your browser. The text you type, the hashes computed, and the blocks you mine never leave your device. We don't receive them, log them, or store them; analytics records only that the page was visited. No account is required or offered.
2. The public vault: read-only and anonymous
The vault shows genesis blocks that people have struck. Each entry shows the inscription and block data only, never any information about who requested it. Viewing the vault requires no account and collects nothing about you beyond the standard technical request logs described in §6.
3. Signing in to mine a real block
Striking a real genesis block is free during our beta but requires a Google sign-in (so we can apply the limit of 10 per account). When you sign in and submit an inscription:
- From Google sign-in we receive your Google account identifier and email address. We use them to associate your requests with your account, enforce the 10-block limit, and email you a certificate for each block you have struck (a receipt for something you asked for: inscription, hash, and proof-of-work details). We don't share this.
- Optional updates: when you submit a strike you can tick a box to also receive occasional product news from us. We only send those if you opted in, every one includes an unsubscribe link, and unticking the box (or unsubscribing) stops them. Your certificate emails are unaffected either way.
- We store your request (your account id, the inscription text, and status) so the foundry can mine it and show you progress. You can read only your own requests.
- What becomes public: only your inscription and the resulting block (hash, nonce, header), displayed anonymously in the vault, never your name, email, or account id. Please don't put anything private into an inscription; it is published on purpose.
4. Paid strikes (not currently offered)
We may later offer paid strikes through Stripe. That flow is not active right now. No payment is taken and no card data is handled. If we enable it, Stripe would process payments under Stripe's Privacy Policy and this page will be updated first.
5. Service providers we use
- Google Firebase (Authentication, Hosting & Firestore) signs you in, serves this site, stores the public block records and your own requests, and dispatches certificate emails through an email delivery service.
- Google Analytics 4 counts visits and page usage in aggregate, with ad features disabled, under Google's Privacy Policy.
- Stripe, reserved for paid strikes; dormant while they're off.
These providers process data on our behalf. We don't sell your personal information to anyone.
6. Technical logs
Like virtually all websites, our hosting provider automatically records standard request data (such as IP address, timestamp, and browser type) for security and reliability. We don't use this for advertising or profiling.
7. Data retention
Public block records are intended to remain in the vault indefinitely as part of the service. Your request records (account id + inscription + status) are kept to enforce the per-account limit and for support, then deletable on request.
8. Your choices and rights
You can ask us what data we hold about your account, ask us to delete it, or ask us to remove a block you struck from the public vault. Email us and we'll help. Because inscriptions are published anonymously, removing a vault entry requires you to identify it (for example, the exact inscription and the account you used).
9. Children
The Site is not directed to children under 13, and we don't knowingly collect personal information from them.
10. Changes
We may update this policy; the “last updated” date above reflects the current version.
11. Contact
Questions about privacy or a request about your data: hello@strikeablock.com.