Privacy policy

• –Your request — the text you type after /bm, so it can be designed.
• –Ground heights — a small heightmap around the build site, so the build sits on your terrain rather than floating or buried.
• –Your Minecraft player UUID — used only to meter the free daily allowance, so one player can't exhaust a shared service.
• –Your API key, if you have one — sent as a bearer token to identify which balance to charge.

Not collected: your inventory, chat history, coordinates beyond the build site, world saves, Minecraft account credentials, or anything about other players.

• –Your email address — to send your key, and to contact you about that purchase.
• –A hash of your key — we store sha256 of it, never the key itself — a copy of our database contains no usable keys.
• –Your Stripe checkout session id — so a purchase can be matched to a key and can't be granted twice.

Card details never reach us. Payment is handled entirely by Stripe on their own pages; we receive confirmation that a session was paid, and the amount of credits it bought.

These are the only third parties involved, and each sees only what it needs to do its job:

• –Google (Gemini) — receives your build request text to design the build. Not your UUID, email, or key.
• –Stripe — handles payment and holds your card details; we never see them.
• –Resend — sends your key email; receives your email address and that message.
• –Fly.io / Vercel — host the build service and this website.

Nothing is sold, and nothing is shared with advertisers or data brokers. We don't build profiles of players and there is no tracking across sites.

Usage counters are keyed by day and roll over. Purchase records — email, key hash, balance — are kept while the key is valid, because they are the thing you bought. Build requests are processed to produce your build and may appear in short-lived operational logs; aggregate statistics (how many builds of each kind, and what they cost to run) are kept, but they are counts, not content.

Everything travels over HTTPS. Keys are stored only as SHA-256 hashes, so there is no endpoint — and no database dump — that can hand out a working key. Payment webhooks are cryptographically signature-verified, so a forged request can't create credits. Secrets live in the hosting platforms' encrypted environment stores, not in the codebase.

This is a small independent service, not a bank. We've built it carefully and described it honestly above — but keep your key private, because anyone holding it can spend your credits.

Don't want to send anything at all? Don't run the command — the mod sends nothing until you ask it to build. To have your purchase data deleted, email support@buildmancer.com from the address you bought with and we'll remove the record and revoke the key. You can ask what we hold about you at the same address.

Minecraft has a young audience, so worth being explicit: we ask for nothing beyond a build request and, if you buy, an email address. We don't knowingly collect personal information from children, and the service is usable without buying anything. If you're under 18, ask whoever pays the bills before purchasing.

If this policy changes materially, the date above changes and the summary will say what moved. Questions: support@buildmancer.com.