Building without an account
Blockwright does not receive that local data unless you choose an online action such as Build Together, device sync, account backup, publishing, AI/video reconstruction, or creating an add-on code.
When you use an online feature
| Feature | What is stored | How long |
|---|---|---|
| Build Together | The shared build name, material list, exact Blockwright blueprint when available, current gathered totals, an 8-character pair code, and a hashed host token. No account or Minecraft identity is required. | 24 hours after the latest material update, or until the host ends the room. |
| Device sync | Your selected build data under a random 26-character code. The code is the key. | Up to one year after the latest save. |
| Private add-on code | Sanitized build name, dimensions, Bedrock palette, compressed block positions, count, checksum, random code, and expiry. | 30 days. |
| Public creator capture | The same sanitized block layout plus a creator-source label. The creator intentionally publishes the code in a tutorial description. | Up to five years so an older tutorial can keep resolving to its exact build. |
| Optional account | OAuth provider and provider ID, chosen public handle, avatar URL when the provider supplies one, hashed session token, and builds you save to the account. For Apple sign-in, its refresh token is retained so Blockwright can revoke Apple access if you delete the account. | Until you delete the account or the applicable session expires. Apple access is revoked during deletion. |
| Community publishing | The build and public title, description, tags, author handle, preview, and view count you choose to publish. | Until you unpublish or delete it. |
| YouTube or AI import | The link, tutorial details, screenshots, temporary video frames, or prompt needed to reconstruct the build are processed to answer the request. Native video analysis captures only after you approve the system permission. It does not record audio or save a recording. The source URL is not copied into a private add-on code. | Video frames and screenshots are limited to processing and are discarded after the request. Ordinary service security logs remain unless you save or publish the resulting build. |
What the Minecraft add-on does not collect
- No Microsoft or Minecraft login.
- No gamertag, world seed, world name, coordinates, inventory, contacts, camera, microphone, or payment information.
- No copy of the blocks already in your world.
- No placement progress sent back to Blockwright.
The add-on checks nearby blocks inside Minecraft only to mark guidance as correct, missing, or wrong.
Service providers
Blockwright uses Cloudflare to host the site and APIs. If you choose sign-in, Apple, Google, or Discord handles authentication. Blockwright does not request your email address from any sign-in provider. YouTube receives normal browser requests when you open or play embedded tutorial content. Those services apply their own privacy terms.
Operational abuse protection uses a one-way hash of the requesting IP address in minute-sized buckets. Those rate-limit entries expire after two minutes.
Community safety and support requests
A report stores the target build, creator, or AI-result summary; the selected reason; optional details; and, when signed in, the reporting account. A support request stores its topic, message, optional page or handle, and an optional reply email when you provide one. Signed-out submissions use short-lived rate-limit data to prevent abuse. Reports and support requests remain as a private moderation audit trail.
Your choices
- Use the core checklist without signing in.
- Only share a Build Together pair code with friends you want to edit that build.
- Leave a shared build while keeping your local copy, or end the room for everyone when you created it.
- Do not publish a build unless you want it visible to other people.
- Block a creator to hide their community content for your signed-in account, or unblock them later.
- Remove local builds and browser data from the app controls.
- Delete an optional account from the profile menu. Account builds, publications, favourites, sessions, and associated preview cards are removed; local checklists remain on your device. Step-by-step instructions, including how to ask for deletion without the app, are on the account deletion page.
Children and families
Blockwright is designed so the core tool and private blueprint-code flow do not require a child to create a profile. A parent or guardian should supervise optional account creation, public publishing, external links, and Minecraft Marketplace or Realm purchases.
Security
Private codes should be treated like private links: anyone who has one can retrieve that build until the code expires. A Build Together pair code also allows its holder to update shared material progress. Creator capture codes are public because creators place them in public tutorial descriptions. Blockwright uses HTTPS, validates blueprint dimensions and block data, atomically merges simultaneous material updates, checksum-verifies add-on downloads, hashes owner and session secrets in storage, and rate-limits sensitive operations.