Privacy
Last updated 13 October 2026
Kanbanana is a free board for robotics teams. It is used by children, so this page is written to be read by a student, a parent, or a teacher deciding whether to allow it. It describes what the software actually does, which you can check against the source.
The short version
- There is no advertising, no analytics service, and no tracking of you across other websites.
- Nothing is sold or shared for marketing. Ever.
- Accounts made with a Robocode need no email address and, by default, cannot upload a photograph.
- You can download everything we hold about you, and delete your account yourself, from your account page.
Who is responsible
Kanbanana is run by the team credited on the site, FLL Team #4734, the Cannon School Brainy Yaks. For anything on this page, including a request to see or delete data, write to [email protected].
It is a volunteer project offered free of charge. That is not a disclaimer of responsibility, but it does mean it is small: there is no support desk, and a reply comes from a person rather than a company.
What is collected, and why
| What | Why | Where it comes from |
|---|---|---|
| Your display name | So teammates can tell who did what | You, or a coach setting up a Robocode |
| Email address (adults and older students only) | Signing in, resetting a password, team invitations, an email when a teammate mentions you, and the occasional news or announcement from the people who run Kanbanana (with a record of which ones were sent to you). Mentions and announcements can each be turned off on your account page | You, at sign-up |
| Password | Signing in. Stored only as a hash by our authentication provider, never in readable form | You |
| Profile colour, and optionally a small profile picture | So people are recognisable on a shared board | You. Off by default for Robocode accounts |
| What you write: cards, lists, comments, checklists, run notes | It is the product. This is the work your team is doing | You and your teammates |
| An activity trail: who moved or completed what, and when | So a team can see what changed on a shared board | Generated as you use it |
| A record of board changes kept by the database: who added, moved, finished or was given a card, ticked a checklist item or set a due date, and when (never what a card says) | So a team's weekly parent update can say what happened that week | Generated as you use it. Deleted after 12 months |
| A device label such as “Mac · Firefox”, and which tab is active | Keeping one account to one place at a time, so two tabs do not fight | Your browser |
| A record of use: which days you used Kanbanana; the kinds of page you opened (“a board”, never which board) and how long they were open; what you did, such as making a card or posting a comment (never what you wrote); how you arrived (the site you came from and any campaign tags on the link); and your country, state, kind of device, browser, screen width and language | So the people who run Kanbanana can see how it is used, where and on what, and what to improve. Never shared, never sold, never used for advertising | Your browser, as you use Kanbanana. If you are not signed in you are counted with a code that changes every day and cannot be traced back to you. No cookies, nothing stored on your device for it, and no IP address is kept. A browser that sends Global Privacy Control is not counted at all |
| Peel, the AI helper (accounts with an email address only, never Robocode accounts): the messages you send it, the board details it looks up to answer, a card you ask it to peel into tasks or smaller cards (its title, description, checklist, list and board name), and a line a coach asks it to word for a parent update, go to Anthropic to be answered. Kanbanana does not keep your chats; it keeps only how many credits you used each day | So Peel can answer and make the changes you approve, and so each person's daily allowance holds | You, when you use Peel. Anthropic processes it under its commercial terms, which do not allow training its models on it |
| The weekly parent update, if a team sends one: the titles of the cards it finished or worked on that week, their lists, labels and checklist counts (such as 4 of 6), and the first names of the students on them, go to Anthropic to be written into a short email. Never card descriptions, comments, checklist wording or attachments; email addresses, links and last names are taken out first; a coach can keep any card or label out, or leave names out altogether, and nothing is sent to parents until a coach has read and approved that week's email | So parents know what the team worked on without asking the coach | Your team's boards, only when the team has parents signed up. Anthropic processes it under its commercial terms, which do not allow training its models on it |
| Parents on a team's update list (they do not have accounts): their email address, the name they give, what they said about their student, which students they or a coach linked them to, and which updates were sent to them | So the weekly update reaches them, says a line about their own student, and can be paused or stopped from a link in every email | The parent, or a coach who invites them by email. Every parent who signs up from a team's shared link is approved by a coach first |
| People without an account whom the people who run Kanbanana email directly (for example a coach who asked to hear about it): their email address, a name if one was given, and which announcements were sent to them | To send that announcement and keep a record of it. Every such email says who sent it, and replying asks us to stop | The people who run Kanbanana, who typed it in |
| Email lists the people who run Kanbanana keep for their announcements: an address and a name if one was given, typed in or saved from who an earlier announcement went to | So the same people can be written to again without typing them in each time. Every email still goes by the rules above, and a Robocode account's address is never on one | The people who run Kanbanana |
| Kanbanana Split, competition-day mode: your team's events, schedules, judging times, match scores, run order and packing list. A schedule file a coach uploads goes to Anthropic to be read, and is not kept | So everyone on the team knows where to be on the day, and so the coach can keep score. A copy is kept on your device so it still reads with no signal; signing out clears it | Your coach and anyone they let manage it |
| Match alerts, if you turn them on: for each device, the address your browser's push service gave it (Apple, Google, Mozilla or Microsoft, depending on the browser) and the keys that let us encrypt an alert to it | So your phone can say a match or judging session starts in 15 minutes. The alert is encrypted so the push service cannot read it. Turning alerts off, or signing out on that device, deletes it | You, when you turn alerts on |
| A spectator link, if a coach makes one: anyone holding it sees the event's name and dates, the team's name as the coach typed it, and its matches with their times, tables and final scores. Nothing else, and no account is needed | So families can follow along on the day without an account | Your coach, who can turn the link off at any time |
| Feedback you send: the weekly check-in (stars, whether you are a coach, student, mentor or parent, and anything you choose to write) and feature requests | So the people building Kanbanana know what is working, what is in the way and what to add. Read by them only. They can stop asking some people (one person, an email domain or a team, such as their own testers) and delete those people's answers | You, when you choose to answer. The check-in is optional and can be skipped |
| Crash reports: an error message, where it happened, and a browser version | So breakage gets noticed and fixed rather than being discovered by a student | Generated when something fails |
There is no advertising network, no analytics vendor, no session recording, and no third-party tracking script. Fonts are served from Kanbanana itself, so loading a page does not tell anyone else you were here. The one exception is a check that you are a person, run by Cloudflare Turnstile on the sign-in, sign-up, Robocode, password-reset, parent sign-up and contact forms only. It looks at your browser to tell people from automated sign-ups, and Cloudflare does not use it to track you or to show you advertising.
Children
Kanbanana is built for teams that include children, and a coach can create a Robocode for a teammate who is under 13 or has no email address. A Robocode account deliberately holds as little as possible: a display name, an eight-digit code and a picture password (four pictures, chosen at random, which only the team's coaches can see). No email address, no typed password to remember, no contact details for the child.
By default a Robocode account cannot upload a photograph. A photograph of a child is personal information in its own right, and it is not collected unless the person running the site turns that on, which they should only do where they hold the consent that covers it.
To be precise about a limit rather than overclaim: this rule applies to accounts created with a Robocode. A student who signed up normally with a school email address is treated by the software like any other account, and can add a picture. If that matters for your team, use Robocodes for students, or ask us to switch pictures off for everyone.
Kanbanana is intended to be adopted by a school or a coach who is responsible for the students using it, and who has the standing to consent on their behalf or to obtain a parent's consent. If you are a parent and want to see or delete what is held about your child, write to us and we will do it. We will not ask the child.
If a team sends a weekly parent update, the parents on its list read the first names of the students who finished each piece of work (or first name and last initial, or no names, as the coach chooses). A parent never sees the board. The team's shared parent link never lists its students, and nobody who signs up through it gets an update until a coach approves them.
Who else can see it
Your teammates see what you put on your shared boards. That is the point of a shared board, and it is worth telling students plainly: a comment on a card is not private.
Beyond that, Kanbanana relies on a small number of services to run at all. They process data on our behalf and are not permitted to use it for anything else.
| Service | What it does | Where |
|---|---|---|
| Supabase | The database and sign-in | United States |
| Vercel | Serves the website | United States |
| Resend | Sends the few emails Kanbanana sends | United States |
| Cloudflare | Domain name routing, and the person check on sign-in and contact forms | Global |
| Anthropic | Runs the model behind Peel, the AI helper: the messages you send it, what it reads from your boards to answer them, the cards you ask it to peel, and event schedule files a coach uploads to Kanbanana Split. Also writes a team's weekly parent update from its card titles | United States |
| Apple, Google, Mozilla, Microsoft | Deliver match alerts to devices that turned them on, through each browser's own push service. They carry the alert encrypted and cannot read it | Global |
Data is stored in the United States. Nothing is sold, and nothing is handed to anyone else except where the law actually requires it.
How long it is kept
Being straight about this rather than quoting a period we do not enforce: board content stays until your team deletes it, because it is your team's work, and your account details stay until the account is deleted. Crash reports are cleared by hand once the problem is fixed. Deleted on a schedule: the record of use after 400 days; the record of board changes, and the weekly parent updates with who they went to, after 12 months; the working copy of a week that an update is written from, after 14 days.
What is immediate is deletion when you ask for it. Delete your account and the things that name you go at once, not on a schedule.
What you can do about it
From your account page, under “Your data”(press your picture and name at the top right of your boards page), without asking anyone:
- Download a copy of everything linked to your account, as a single file.
- Delete your account, along with your profile, your picture and your comments.
If you get a team's weekly parent update, every email links to your own settings page, where you can pause it, stop it, or leave the team's list, which deletes your address from it. Nobody needs an account for that.
Cards and lists your team made together stay on the board when you leave, because they belong to the team rather than to you. If you want those removed as well, ask your coach, who can delete the board.
You can also ask us to correct something, or object to how it is used, by writing to [email protected]. If you are in the UK or the EU you have the right to complain to your data protection authority.
Keeping it safe
Every request is checked by the database itself rather than by the app, so a modified browser gets no further than an ordinary one. Traffic is encrypted. Passwords are stored as hashes. Administrative keys exist only on the server and never reach your browser.
No system is beyond reach. If something does go wrong and it affects people's data, we will say so, on this site and by email where we have an address, and we will say what actually happened.
Changes
If this page changes in a way that matters, the date at the top changes and the site says so. See also the terms of use.