← Buildmancer

Privacy policy

Last updated 30 July 2026 — we stopped advertising on Google and removed its tag. This website now sets no cookies at all, so there is no longer anything to ask you about.

Short version: Buildmancer has no accounts and no passwords. To build something it needs your request text, a small patch of ground heights, and an identifier to meter usage. If you buy credits, it also needs an email address to send the key to. That's all of it. This website sets no cookies, runs no analytics, and contains no advertising or tracking scripts of any kind — which is why it no longer shows a cookie banner.

What's collected when you build

  • Your requestthe text you type after /bm, so it can be designed.
  • Ground heightsa small heightmap around the build site, so the build sits on your terrain rather than floating or buried.
  • Your Minecraft player UUIDused only to meter the free daily allowance, so one player can't exhaust a shared service.
  • Your API key, if you have onesent 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.

What's collected when you buy

  • Your email addressto send your key, and to contact you about that purchase.
  • A hash of your keywe store sha256 of it, never the key itself — a copy of our database contains no usable keys.
  • Your Stripe checkout session idso 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.

Who it's shared with

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.
  • Stripehandles payment and holds your card details; we never see them.
  • Resendsends your key email; receives your email address and that message.
  • Fly.io / Vercelhost the build service and this website.

Nothing is sold, and nothing is shared with data brokers. Nothing you send from inside Minecraft — your requests, your UUID, your key, your builds — is ever used for advertising or shared with an advertising network. There is no advertising network involved anywhere any more: we used to run Google Ads and its tag on this website, and both are gone.

Cookies on this website

There are none. This site sets no cookies, loads no analytics, and includes no third-party tracking scripts — so there is nothing to consent to and no banner to answer. Nothing about your visit is measured or reported to anyone.

Until July 2026 we advertised on Google and this site carried its ad tag, behind a banner that asked first. We stopped advertising, and the tag, the banner and the stored record of your answer were all removed. If you had accepted back then, your browser may still hold a Google Ads cookie from that period: this site deletes any it finds when you load a page, and they expire on their own regardless.

Paying is the one exception, and it happens elsewhere: checkout runs on Stripe's own pages, under Stripe's privacy policy and their cookies, not ours.

The mod and the build service use no cookies either. They aren't a browser, and nothing on this page changes what they send.

How long it's kept

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.

Security

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.

Your choices

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.

Children

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.

Changes and contact

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

See also terms & refunds and support.