Version 2026-10-17. This policy covers the Burrow server at burrow.moe, its website and its client.
The controller of your personal data is the operator of Burrow, an individual based in the European Union. Contact for anything in this policy: legal@burrow.moe. General contact: admin@burrow.moe.
We do not sell data, show ads, track you across sites or send marketing. We do not collect your real name, email address or date of birth. The only statistics we keep are the game's own activity figures in section 2, which are used only to run and plan the server, and the overall traffic figures described in section 4.
| Data | Why |
|---|---|
| Username, password (stored only as a salted hash), and the date and version of the terms you accepted | To give you an account |
| Your game data: animals, items, dens, pets, buddies, block list, trades, achievements, settings | To run the game for you |
| What you choose to write or make: bio, Discord username (optional), Jam-A-Grams, wall posts, paintings, feedback | To show or deliver it as you asked |
| Typed chat and whispers, with the room and time, and the words of Jam-A-Grams and wall posts, with who they went to | Moderation: reviewing reports and deciding on bans |
| IP address at each sign-in, and sign-in times | Security: your sign-in history, limiting abuse, address bans, and finding accounts made to get around a ban |
| Hardware hashes, sent by the Burrow client at each sign-in. The client reads a few identifiers of your device (its system id, hardware serial numbers, network card addresses, and a random id the client makes for itself) and turns each into a one-way hash before sending it; we hash them again with a secret key of our own. The identifiers themselves never leave your device, and the hashes cannot be turned back into them: they do not tell us who you are, what your device is, or anything else about it, and mean nothing outside this server. We also note if the identifiers look missing or altered | Only to prevent ban evasion: hardware bans, and finding accounts made to get around a ban. They are not used for tracking or advertising and are never shared |
| When you log in to the game, how long each visit lasts, and your total playtime | To show you your playtime, and for overall activity figures (how many people play and when) that staff use to run the server |
| The number of players online, counted every minute | Overall activity figures. This count is not linked to anyone |
| Reports, bans and their reasons, appeals, username rejections | Moderation and preventing ban evasion |
| 2FA secret and trusted-device tokens, if you turn 2FA on | To protect your account |
| Technical error reports sent by the game client | Fixing bugs |
Creating an account requires the first row only. Everything else comes from playing.
We share data with nobody else, unless the law requires it. WildWorks receives nothing from us about you.
Parts of Burrow are reached through Cloudflare, Inc., which protects the server from attacks and delivers pages faster. When your connection passes through Cloudflare, it processes your IP address and technical details of the request (such as browser type, the page requested and the time), and may set a cookie that is needed for security. Cloudflare operates worldwide, so this can happen outside your country, including in the United States.
When you sign in or create an account, a Cloudflare captcha (Turnstile) checks that you are a person. It looks at your IP address and at signals from your browser and device, and only tells us whether the check passed.
Cloudflare gives us overall traffic statistics, such as the number of requests and visitors and the countries they come from. These do not identify you and we do not combine them with your account.
Cloudflare handles this data under its own policy: cloudflare.com/privacypolicy.
| Data | Kept |
|---|---|
| Account and game data | Until you delete your account |
| Chat, whispers, and the words of Jam-A-Grams and wall posts | 30 days |
| Hardware hashes | Until you delete your account (the latest 60) |
| Hardware bans (hashes only) | Until the ban is lifted |
| Sign-in history with IP addresses | Your last 40 sign-ins, and none older than 90 days |
| Error reports and server logs | Up to 30 days |
| Handled reports, feedback and username requests | 12 months |
| Ban records | While the account exists, then 12 months |
| Banned IP addresses | Until the ban is lifted |
| Record of game logins and visit lengths | 12 months |
| Number of players online (not linked to anyone) | Kept indefinitely |
| Backups | 14 days |
When you delete your account we delete your game data, chat, hardware hashes, appeal, feedback, username requests and paintings straight away, and your total playtime. Your past logins stay in the overall activity figures for up to 12 months and are not shown to anyone by name. Your username is held for 30 days so nobody can pass as you, and ban records are kept as shown above. Copies in backups disappear within 14 days.
Wherever you live, you can use these on your account page:
You can also ask us to restrict or stop a use of your data, or ask any question, by writing to legal@burrow.moe. We answer within one month.
Burrow is for people aged 13 and over, or the higher age at which the law of your country lets you agree to the use of your data on your own (up to 16 in parts of Europe). We do not knowingly collect data from anyone younger and we do not offer parental consent. If we learn that an account belongs to someone under that age we delete it. Parents and guardians can ask for this at legal@burrow.moe.
The website sets only cookies that are needed to keep you signed in: a session cookie on your account page (12 hours) and, if you choose "Trust this device", a 2FA cookie (30 days). The client keeps your saved sign-in on your own device if you tick "Remember me". Cloudflare may add a security cookie of its own (section 4). There are no advertising or tracking cookies.
Passwords are stored only as salted hashes, sign-in tokens as hashes, and connections are encrypted when the server address begins with https. No system is perfectly secure. If a breach puts your data at risk we will tell you in the game and on this site.
If this policy changes, the version at the top changes with it, and significant changes are announced in the game or on this site before they apply.