Privacy
Plainly: the site stores nothing about you until you sign in, and then it stores as little as an account can be made of. No analytics, no tracking, no advertising, no third-party scripts.
Without an account
Reading the site, using the editor and browsing the gallery store nothing on the server about you. The server keeps ordinary access logs (the address a request came from, the page, the time) for up to fourteen days, for keeping the site up and for abuse, and nothing is derived from them. Download and view counts are plain totals with no per-visitor record.
The editor loads Pyodide, the Python runtime it runs on, from the jsDelivr CDN, which therefore sees the request for those files and nothing else; Blockbench's own calls home are blocked by the site's policy. The editor keeps your own work in your browser's storage (IndexedDB and localStorage) so it is there on your next visit. That data never leaves your browser unless you upload a pack or link a folder yourself. A selection in the gallery is kept in your browser the same way. The cookie page lists all of it.
With an account
Signing in goes through a provider you choose (GitHub, Google, Discord or Microsoft). The site never sees a password. What it stores:
| What | Why | How long |
|---|---|---|
| The provider's name and the id it gives you | To know it is you next time | Until you delete the account |
| A display name, from the provider, which you can change | To credit your packs | Until you delete the account |
| Your email address, only if the provider gives one | Account recovery and abuse contact; nothing else, no mail otherwise | Until you delete the account |
| Your packs, their versions, their manifests and thumbnails | They are the point | Until you delete them, or the account |
| Links to packs on GitHub or Google Drive, if you make them | To fetch new versions | Until you unlink them |
| Device tokens, if you sign the desktop editor in | To let it reach your library | Until you revoke them |
| Sessions | To keep you signed in | Thirty days, or until you sign out |
| An audit entry when something is published, approved or deleted | Moderation and takedowns | One year |
A GitHub link asks for access to the one repository you choose, through a GitHub App you install on it, not to your account. A Google Drive link asks for the one file you pick, through the drive.file scope, and can be revoked on its own. Neither is asked for at sign-in.
Where
The site, its database and its file storage run in the Netherlands. The parties that process data on its behalf are the hosting provider, the file storage provider, and the sign-in provider you chose, each for exactly the part they do. Nobody is sold or given anything.
Your rights
Under the GDPR you can ask what is held about you, have it corrected, have it exported and have it deleted. Two of those are buttons on your account page: Export hands you a JSON file with everything the table above lists, and Delete account removes the user, identities, sessions, device tokens and private packs at once. Packs you have published in the gallery are deleted too, unless you choose to leave them published under your credit. For anything else, write to admin@armorpieces.com. The controller is mattjes, reachable at that address.
Age
You must be old enough to hold an account with the provider you sign in with, which for all four is thirteen, and older where local law says so. The gallery is for all ages, and the terms keep it that way.
Changes
If this page changes in a way that matters, the change is announced on the account page for thirty days and dated here. This version: 2026-09-06.