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, and no third-party script - with one exception you have to press a button for, Google's file picker, named below.
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. The shelf you keep without an account - the packs and pieces you save and the outfits you make - is kept in your browser the same way, as names rather than files, and is sent to this site only if you sign in and choose to keep it in a library. 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 - this table is kept against the database's own definition (src/db/schema.ts), and the account pages show you each row of yours:
| What | Why | How long |
|---|---|---|
| The provider's name, the id it gives you, and the scope it granted | To know it is you next time | Until you delete the account |
| Of a GitHub sign-in, its access token | Read once per link, to confirm that a GitHub App installation on an organisation is yours | Until you delete the account |
| Of a Google sign-in with Drive allowed, the refresh token | It is the Drive grant: the server reads the one file you picked with it | Until you revoke Drive on Connectors, or delete the account |
| A display name, from the provider, which you can change | To credit your packs and outfits | Until you delete the account - or, if you leave published work in the gallery, as long as that work is there |
| Your e-mail address, only if the provider says it has verified it (GitHub, Google and Discord can; Microsoft is not asked) | Lets a second provider sign into the same account; where a maintainer would write about a takedown. No mail otherwise | Until you delete the account |
| No avatar, no photo, no bio | Nothing shows one | Not stored: every provider's picture is dropped at sign-in |
| Your packs: their working lists, versions, manifests, thumbnails and credits | They are the point | Until you delete them, or the account |
| The pieces themselves - the files of every piece, skin and cloth you have brought in | A pack is a list of them, and so is somebody else's pack that borrows one | Kept when the pack or the account goes, without your name on them. Write to us to have one removed |
| Your library: the packs you saved, your collections and their pieces, your outfits | They are yours to keep | Until you remove them, or delete the account (a public outfit can be left in the gallery under your name, like a pack) |
| Links to packs on GitHub or Google Drive: the repository and App installation, or the Drive file's id, and how the last read of it went | To fetch new versions and to say on the pack's page whether the source still answers | Until you unlink the pack, or delete the account |
| Device tokens, if you sign the desktop editor in: a hash of the token, its label, when it was last used | To let it reach your library; the token itself is shown once and not kept | Until you revoke them |
| While a device code waits for approval: the code, and the address it was asked from | So the approval page can say who is asking | Fifteen minutes |
| Sessions | To keep you signed in | Thirty days, or until you sign out (everywhere, if you like) |
| Reports you file, with your account on them | So the answer can be shown to you | With the report |
| An audit entry when something is published, approved, taken down or deleted, and the decisions listed on your account page | Moderation, takedowns, and telling you what happened | One year |
| Storage counts: how many bytes and files your own packs use | The quota | Computed, not stored |
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. Picking that file loads Google's own picker script from apis.google.com - the one third-party script on the site, loaded only on the Connectors page and only when you press Pick a zip on Drive; Google sees that request and the picking, as it would in Drive itself.
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's settings: Export hands you a JSON file with everything the table above lists, and Delete account removes, at once, the sign-ins, sessions, device tokens, App installations and Drive grant, your saved packs and collections, every pack that is not in the gallery, every outfit that is not public, and your e-mail address. Packs a maintainer approved and your public outfits go too, unless you tick leave them in the gallery under my name - then they stay, and a bare account row keeps nothing but that name. The pieces those packs were lists of are kept, with your name taken off them, because another pack or somebody's saved outfit may be a list that includes one — write to the address below to have a piece itself removed. 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 dated here, and the site's release notes say what changed. This version: 2026-09-13 (what a sign-in stores, what deletion keeps, the picker).