Privacy

Last updated November 11, 2026

Brickcay is run by Sunate Inc., doing business as Brickcay. Here's what we keep, and what we don't.

In short

Brickcay keeps that work happened, not the work: no code, no file contents, no commit messages, and never Claude's replies. Your messages to Claude stay on your computer, except when you swear or shout at it: then up to 140 characters reach your own island's feed, never the public link. The one file in a repository it opens is the logo or favicon, for its color, and it keeps only the color. The few words about your work it does keep, a merged pull request's title and what you say at the fire circle, only your island's people see. The rest of this page is the full list.

From GitHub

When you connect repositories, GitHub tells us when work happens. We keep:

The repository's name and main language, and the branch.
Who did it: a GitHub login, or the name and email on a commit when there's no login.
The commit id and the paths of the files changed, for ordinary commits.
Pull request numbers, how many lines they changed, and when they were opened, merged or closed.
The title of a merged pull request and who merged it, so your island's people can see what each deploy shipped. Only they see it: never on the island's link or on our site.
Releases, production deploys, check results and issue numbers.
Commits from a bot, or from an author with no GitHub account (usually an agent), show as a helper monkey. It belongs to whoever on the island pushed those commits, or to the owner, and its bricks count as that person's. Pointing at one shows a monkey name made from the agent's, and only to your island's signed-in people; the agent's own name is never shown.

We don't keep your code, the contents of your files, commit messages, pull request descriptions, or the titles of pull requests that weren't merged.

Your logo

We just open your logo file to customize the buildings. To find it we read the list of file names in the repository, and open one file named like a logo or a favicon. We keep its main color and throw the rest away. We don't keep the file or its name, and we don't open any other file.

If there's no such file, or it has no color, we look at your GitHub organization's picture, and then the site in the repository's homepage field: its icon and the color it says it is. We also read the repository's topics, to choose a landmark.

The color and the landmark show only on your island's private link and in the pictures that go to its people. Never on our site, or in the rankings.

From Claude Code, if you connect it

A small hook on your own computer sends us the repository's name (or, for a project that isn't on GitHub, the folder's), the branch, a session id, when a session starts, each time Claude finishes a reply, and for each file Claude edits its path, its language, which of Claude's editing tools changed it (Edit, Write, MultiEdit or NotebookEdit), and whether the path looks like docs or a test.

The one hook per computer sends only for repositories on your island. Any other repository sends nothing, not even its name, until you say yes to adding it, and then only the island's owner can put it on. An older connection, made for a single folder, still sends us that folder's repository name. On someone else's island only a repository already on it lands there; any other stays off and becomes a request to the island's owner.

It never sends your code or Claude's replies. The hook works out your tone on your computer and sends the mood, which shows as a face over your character, plus one word from a fixed list if you turned words on. Anyone who can see your island can see those. When you swear at Claude or shout at it, it also sends what you wrote, without code and cut at 140 characters, and the people on your island see it in their console's feed with your name. It never shows on the island's link or in public. A message with no tone to show sends nothing at all. To turn moods off, set mood to off in ~/.brickcay/config.json, or ISLAND_MOOD to off.

It also reports how much of your weekly Claude limit you have used: the share used and when your week resets, as Claude Code shows them, and never a token count, a cost or your plan. To read them it sets a status line in Claude Code that shows nothing; if you already have a status line of your own, it leaves it alone and sends none. It shows as a woodpile by your home that only your island's people see, signed in on the island. Not to someone with just the link. Pointing at your woodpile shows what's left this week and when it resets, for that pile alone; nobody gets a total or a ranking.

From Claude, if you connect it

Claude signs in with your Brickcay account, for one island you choose. It can only lay a brick there: it sends us no words, no files and nothing about the work, and we send Claude nothing about you. Disconnect it in your profile.

From you

Your GitHub id and login, when you sign in with GitHub or connect it, and who you are on Brickcay, kept in a cookie for 30 days so you stay signed in, with a record of that sign-in on our servers, so logging out ends it and a copied cookie stops working. A GitHub account you connect counts its commits as yours on your islands; "Not you?" takes it off.
The name you give your character. Anyone on your island sees it; the public island never does. If you own an island, anyone with its link sees your name, and nobody else's, where it asks them to join.
The island's time zone, and who asked to join and who was let in. When you ask to join, the owner sees your email and gets one to say so, and you get one when you're let in. Someone whose email is at the owner's own company walks straight in, unless the owner turns that off.
Your answer if you tell us what you used before. It's optional.
What you write in the form on the companies page, including your name and work email.
From the events your tools send, we work out numbers per island for ourselves: how much each tool is used, active hours, lines changed, and the order tools are used in. Never per person, and never what the work contains.
Your email, if you ask for early access. We use it to let you in and to tell you about Brickcay, and nothing else.
Your email, if you sign in with it or add it. We use it to sign you in and for the emails about your island. The link in a postcard stops postcards.
Every island is on the rankings: its made-up name, a rounded score, its size and its era are public on /rankings. Never its link, its repositories or its people. To take an island off, write to us.
Achievements, worked out per person from those same events and shown only to that person, on their profile and in the emails we send them. The island's owner sees how many someone has, and never which. Some good ones bring a pet to your home on the island, which anyone who can see the island can see. Nothing there says what it was for.
The look you draw for your character on an island: who they are, their skin tone, what they wear, and the color you keep. Anyone who can see the island can see them. It's a drawing you choose, and we don't use it for anything else.
A picture of each island, drawn from its public state: no names, no thoughts. It goes only in emails to people on that island, and in invites they send.
An address someone types to invite you, who invited you, and your email if they did. We send that invite and keep the address, so the same invite doesn't go out twice. One nobody used can be sent again after 14 days.
What you say at a fire circle, your team's daily on the island: what you did, what's pending and what's next, as the short lines you keep, and the votes on whether a task got done. Only the people on your island see them, in the console and on the island's own pages; the public island shows people around a fire and no words. The last 30 circles are kept.
If you speak your turn instead of typing it, your browser turns your voice into text: Chrome sends the sound to Google to do it, Safari to Apple. We never get the sound. The text goes to Anthropic, whose Claude writes it into short lines on your screen, and is not kept by us: only the lines you keep are, when you say your turn. This is the one place where words about your work leave your computer, and only for your island.
What you add or vote for on the public board. Nobody signs in there: a random id in a cookie, which says nothing about who you are, keeps it to one vote per browser for a year.

Who sees what

Anyone with your island's link sees the buildings and the characters, never repository names or logins. People you let in may see more, such as who is who.
The owner of an island sees its repositories and its people in the console.
We see totals across all islands, such as how many were created, how many lines were merged and which tools are in use, and we use them to run and improve Brickcay. We can reach the underlying data to keep the service working.
The island behind this website is our own.

The radio

When someone plays a song on an island's radio, a short clip plays from our own site, and its name shows in a corner of the island's page. Nothing loads from anyone else. Each song is played with a radio ticket, and every crate holds one; we keep how many you have and when each was used. Until November 16, 2026, songs were also earned from how much of your weekly Claude limit you used, the same reading as your woodpile; songs earned that way and not yet played stay, and the reading earns none after that day.

Crates

Your first and third day of work in a week each earn you a crate with a meme sound or a pet in it, and a radio ticket. Nothing about crates costs money. We keep the crates you earned, the sounds you put on your keys, the pets you kept, which of them you told to stay home, and your radio tickets. When you play one, its name shows for a few seconds in a bubble over your character, to anyone who can see the island, and the people on your island who have the console open hear it. Crates and sounds are never counted on a leaderboard, the feed or the postcard.

Who helps us

Vercel hosts the site and the servers, Neon hosts the database, and Resend sends our email. Anthropic writes a spoken turn at a fire circle into short lines, and doesn't use it to train its models. Google Sheets keeps our working copy of the early access list. GitHub Actions stores our daily backups of the database. They process data for us. GitHub signs you in and sends us events. We don't sell your data, and there are no ads or tracking scripts on this site.

Keeping and deleting

We keep your data while your account or your island exists, because your island is built from it. From your profile you can download everything in your account, in one file, and you can delete your account.

Deleting your account ends every sign-in and removes, right then, your email, your names, your GitHub link, your tokens and connected computers, your sign-in codes, the look you drew, and invites you sent that nobody used.
On an island someone else owns, what you built stays, as someone with no name, in the same place and color, so nobody else moves. The branch names, file paths, commit and pull request references and merged pull request titles from that work stay with it, under that same anonymous villager. Your words at the fire circle go.
So that commits arriving later join that same character instead of bringing your name back, each island you were on keeps a one-way fingerprint of your GitHub login and your commit email. It holds no readable name or address, though someone who already knows your email or login could match it.
If you own an island, deleting your account deletes the island, for everyone on it.
If an island's owner had turned you away, we keep a one-way fingerprint of your email and GitHub account for that island, and nothing else, so that deleting an account can't undo their answer. The owner can still let you in, and then it goes.
Two kinds of copy last longer. When a repository is taken off an island, its events are kept for 90 days in case that was a mistake. The database is backed up to GitHub every day, and those copies last 30 days, or up to a year for the one made on the first of each month. A deleted account stays in the backups until they run out, and in those kept events unless its island went with it.
Deleting your account doesn't reach copies outside our database: your email on the early access list in Google Sheets, if you asked for early access, and Resend's logs of the emails we sent you. To be taken off that list, write to espindola@sunate.app.

To have an island deleted without deleting your account, or anything else this page doesn't cover, write to espindola@sunate.app.

Questions

Write to espindola@sunate.app. A person will answer. If this page changes in a way that matters, we'll update the date above.