Privacy policy

Last updated 16 October 2026. Applies to the website bloppit.com and the Bloppit app for iPhone and iPad.

Bloppit is made for children and families, so we collect as little as possible.

The short version

No accounts, no sign-up, no email addresses.
No ads, no third-party analytics, no tracking, and nothing is sold or shared for marketing. Bloppit keeps its own simple counts of how the game is used (how many first builds were finished today, for example), with nothing in them about any one child.
Your photos and builds stay on your device.
The exceptions are rooms (Build together and live Blitz) and Blitz challenges. When you start one, the puzzle is shared through our server so your friends can play it. Rooms are deleted after 3 days without activity, and challenges 30 days after the last player.
The Weekly Bloppit keeps two things when you finish it: that you finished, and whether it was a clean build. The build’s time and misses are sent only to check it’s a real finish, and aren’t kept. No name. The week’s counts are deleted after 8 weeks.
Each player’s progress (trail scores, Weekly Bloppit builds, finished models with their stars, XP, the island’s decorations and arrangement, up to twelve stud-grid drawings as colour numbers, the otter’s brick colour, the outfit it wears and the colours picked for it, whether a treehouse or a lighthouse was chosen for Home Island, the otter’s name when it was picked from the list, kept as a number, and which speed each Blitz win beat) is saved on our server under an anonymous progress code, so it isn’t lost if a device is lost or its storage is cleared. The progress code holds numbers and dates only: no name, no age, no photo, no device details. A grown-up can move it to another device with a one-time transfer code, or delete it, from the Grown-ups corner.
If a child types a name for their otter, that name stays on the device. It is never sent to us, and no other player ever sees it. The game also keeps a picture of the player’s island, and the bricks of each finished model (so it can stand on Bloppitopia), on the device, so bloppit.com’s front page can show the island when they come back. None of that is sent to us.

What stays on your device

Photos you add, the brick models and booklets made from them, player profiles (a first name or nickname, and an age, which sets how hard the Brain Trail math puzzles are), sound settings and the build you’re in the middle of are all kept in your browser’s or the app’s own storage on your device. They are not sent to us. Scores and Weekly Bloppit builds are also kept on the device, and copied to the progress code described below. You can remove them at any time by deleting a player in Bloppit, clearing your browser’s site data, or deleting the app.

The age is only used to choose how hard the math puzzles are. It never leaves your device.

Rooms (Build together and live Blitz)

Rooms let people on different devices build or race the same puzzle at the same time. To make that work, our server keeps a room with:

the room code;
a generated label for each player, such as “Brave Otter 214”. The name typed on a device stays on that device and is never sent to the room;
the puzzle being built, including the photos it was made from;
the bricks each player places and their points or times.

Only people who have the room code can ask to join, and the player who made the room decides who comes in. There is no chat and no voice in rooms: nothing a player types or says is sent to another player.

A room is deleted automatically 3 days after its last activity. Our server does not use rooms for anything else.

Weekly top-100 board

Off unless a grown-up switches it on for a player in the Grown-ups corner. When on, that player’s Weekly finish is listed on a board of up to 100 players under a generated name (“Brave Otter 214”) with whether it was clean and how many stars: no real names and no times. The board is deleted with the week’s counts after 8 weeks.

Crews

A crew is a small group (a family, a class, a club) with a shared building goal. The player who makes a crew gets a code and lets each friend in. Our server keeps, under the crew code: a crew name chosen from a fixed list, each member’s progress code, the bricks and builds each member has added, and the crew board. The board can only hold phrases and stickers chosen from a fixed list, shown under generated names (“Brave Otter 214”); nothing typed is ever sent. Anyone in a crew can report a post, which hides it for them and tells the crew’s maker; three reports pause the sender’s posts in that crew. A parent can see every crew a player is in, and take them out, from the Grown-ups corner. A crew nobody has built in for six months is deleted.

Blitz challenges and relays

A challenge lets a friend race your time later; a relay lets a friend finish a model you started. When you make one, our server keeps the code, the puzzle (including the photos it was made from), and for each player a generated label such as “Brave Otter 214”, their time or the bricks they placed, and their misses and hints (up to 12 players on a challenge, two on a relay). Typed names are never sent. Anyone with the code can see the labels and times on that challenge. A challenge is deleted 30 days after the last player.

Weekly Bloppit

When you finish the Weekly Bloppit for the first time in a week, the app tells our server that one more person finished it, and whether the build was clean (no misses, no hints). The build’s time, misses and hints travel with it only so the server can check it’s a real finish; they are not stored. No name and no rank are kept. The server keeps two counts per week so it can tell you how many builders finished clean, and deletes them after 8 weeks.

Your progress code (saved progress)

The first time a player finishes a build, our server makes an anonymous progress code for that player and keeps their progress under it: trail scores, Weekly Bloppit builds, and later the island they grow. It holds numbers and dates only. The player’s name and age never leave the device. The progress code is kept on the device and is the only key to that progress; it is never shown in a web address.

From the Grown-ups corner (Who’s playing → Grown-ups), a parent can make a one-time transfer code to bring a player’s progress to another device (it works once and expires after 72 hours), or delete everything the server holds for that player. A player that hasn’t played for a year is deleted automatically. A family key (12 characters, made in the Grown-ups corner and shown once) lets a parent see, bring to any device or delete the players attached to it, from any device; our server keeps only which progress codes belong to the key, nothing about the parent. The Family Link there is a link or QR code to Bloppit’s first build (bloppit.com/p/start) for opening on the child’s device; it carries a transfer code only when a parent has just made one, and nothing else. Share links and cards (bloppit.com/p/…) point at a build, or carry a drawing as colour numbers in the link itself, never at a player.

Our own usage counts

To know whether Bloppit works, the app sends a handful of events such as “a first build was started” or “a Weekly Bloppit was finished”. Each one is a single count for the day, with the country it came from and whether it came from the app or the website. They include one count when a device opens Bloppit that day or week, and one the first time it comes back after a day, a week or a month (the dates that needs stay on the device). The website’s pages each count a view the same way. No cookies. There is no identifier for the player or the device in them, and they are never joined to a progress code, a name or a purchase. We use no third-party analytics or advertising software.

Information our hosting provider sees

Bloppit is hosted by Netlify. Like any web host, Netlify’s servers briefly handle technical information such as IP addresses to deliver pages and keep the service secure. We don’t use this to identify or profile anyone. The website loads its fonts from Google Fonts and its 3D library from public code libraries (cdnjs and jsDelivr), which also see the IP address of the device making the request. The app has these files built in, so it doesn’t contact these services.

Children

Bloppit is designed to be used by children. We don’t knowingly collect personal information from children. Names typed on a device stay on that device: rooms, challenges, crews and boards only ever show generated names such as “Brave Otter 214”. In the app, anything that leads outside Bloppit, such as web links or sharing an invite, sits behind a grown-ups check.

Parents and guardians can delete a player’s saved progress themselves from the Grown-ups corner, and can ask us to delete a room or challenge at any time. Email us with its code and we’ll delete it.

Changes

If we change how Bloppit handles information, we’ll update this page and the date at the top.

Contact

Questions or requests: hello@bloppit.com. Bloppit is an independent project based in Bermuda.