1. Who we are
NibbleCode Inc. ("NibbleCode," "we," "us") is a New Jersey nonprofit corporation that provides free computer science education to kids and teens. Our principal office is 76 Arbor Drive, Howell, New Jersey, USA. NibbleCode is the controller of the personal information described in this policy.
This policy covers nibblecode.org and any NibbleCode course pages, tools, terminals and simulators (together, the "Service"). It explains what information we collect, why, and what choices you have.
The short version: we collect only what we need to give you an account, save your work and run the site. During our pilot, accounts are open to people 13 and over who have been invited. After the pilot, anyone can join, and children under 13 will need a parent's permission first. We do not sell or share personal information for advertising, and we never use advertising or cross-site tracking. During the pilot, we ask signed-in participants before recording how they use the site. Our Donate page can load a donation form run by Givebutter, which brings its own payment and tracking services, but only if you choose to open it.
Effective date: October 29, 2026.
2. What we collect
We collect the minimum needed to run the Service.
| Information | Who it comes from | Where it lives | Why |
|---|---|---|---|
| Email address | Everyone who signs up | Our own server | To create your account and email you a one-time sign-in code |
| Birth year (not your full birth date) | Everyone who signs up with email | Our own server | To check you are old enough for the pilot and to apply the right rules for your age |
| From GitHub sign-in: your GitHub user ID, username, primary verified email address, and your GitHub name as a starting display name | Account holders who choose GitHub | Our own server | To sign you in with GitHub and suggest a display name you can change |
| Display name and avatar (a picture we provide, or one you upload if you are 13 or older) | Account holders | Our own server | To show your account to you. Other learners cannot see it. |
| Sign-up answers: how much coding you have done, where you will mostly learn, which pathway interests you and whether you're interested in learning anything, and when you accepted our Terms and read this policy | Account holders | Our own server | To suggest where to start and to keep a record of what you agreed to |
| Lesson progress, every exercise answer you submit and whether it was correct, Circuit lab circuits and their names, and editor settings | Account holders | Our own server | To save your work and let you continue on any device |
| Files you save in your terminal's home folder (up to 50 MB), and a record of when you opened and closed the terminal | Account holders who use the terminal | Our own server | To keep your files between visits and to look into problems. We do not record what you type. |
| Signed-in devices: device type, browser, operating system, approximate region and country, sign-in time and last activity | Account holders, automatically | Our own server | To show you where you are signed in and let you sign out other devices |
| IP address, browser type, pages requested, time of request | Any visitor, automatically | Cloudflare, and briefly on our own server | To deliver pages, block attacks and abuse, and fix errors |
| Email addresses of people invited to the pilot | Teachers, parents or organizers who ask us to invite someone | Our own server | To let invited people sign up |
| Name, email address, organization, message | People who contact us | Our email account, Google Workspace | To reply and to coordinate the pilot or partnerships |
| Pilot feedback | Pilot participants | Google Drive, limited to officers who need it | To measure whether the course works |
| Donations: your name, email address, amount, any note you add, and payment details | People who donate | Givebutter and its payment processors. We see your name, email address, amount and note in Givebutter, never your full card details. | To process your donation, send your receipt, and keep the records nonprofits must keep |
| Pilot analytics: the pages you visit, what you click, how far you scroll, how long you spend on each lesson step and exercise, and errors the site runs into, linked to your account | Signed-in pilot participants who choose "Allow" | Our own server | To see which lessons and features work and which don't. Off unless you say yes. |
What we do not collect: passwords (you sign in with a code we email you, or with GitHub), your GitHub profile photo, contacts, repositories, or any other data from your GitHub account beyond what is listed above. We also do not collect phone numbers, precise location, school records, or sensitive information such as race, religion, or health.
We do not run ads, use advertising networks or outside analytics companies, sell personal information, or share it for cross-context behavioral advertising. The one exception we can't control is the donation form on our Donate page: it is run by Givebutter, and if you choose to open it, Givebutter's form loads its own analytics along with software from Google and Meta (Facebook). See our Cookie Policy.
3. How we use, share, and keep information
We use information only to run, secure, and improve the Service, to answer people who contact us, and to meet legal obligations. We never use it to build marketing profiles.
Who we share it with. Your account, saved work and terminal files live on a server NibbleCode runs itself; no cloud provider stores them for us. We share information only with service providers that process it on our behalf and under contract, and only as much as they need:
- Cloudflare, Inc. for our domain, content delivery and security. Every visit passes through Cloudflare, which sees your IP address and the pages you request.
- Resend, Inc. to send the sign-in codes and other emails from the Service. Resend sees your email address and the message.
- GitHub, Inc. to sign you in, if you choose it. GitHub tells us who you are; we do not send GitHub your NibbleCode activity.
- Google LLC (Google Workspace) for our email inboxes and document storage.
- Givebutter, Inc. to run our donation form and process donations, with Stripe, Inc. and PayPal, Inc. handling payments. If you open the donation form, these companies and the services Givebutter uses, including Google and Meta, receive information from your browser under their own policies.
We may also disclose information if required by law, to report suspected child abuse or neglect as New Jersey law requires, to protect someone's safety, or as part of a transfer of our assets to another 501(c)(3) organization if NibbleCode dissolves. We do not sell personal information.
How long we keep it.
| Information | Kept for |
|---|---|
| Account, saved work and terminal files | Until you or a parent asks us to delete the account. Deleting an account deletes everything listed in section 2 that belongs to it, including terminal files. Copies in any backups are gone within 30 days. |
| Signed-in devices | Until you sign out, or 30 days after that device was last active |
| IP addresses used to block abuse on our server | 10 minutes |
| Server logs | Capped in size; the oldest entries are overwritten automatically as new ones are written, unless we need them to investigate abuse |
| Pilot invitations | Until the pilot ends, or sooner if you ask |
| Emails and contact messages | 2 years after our last exchange, then deleted |
| Pilot feedback | Until the pilot report is finished, then kept only in aggregate form |
| Pilot analytics | Until the pilot report is finished, and no more than 90 days after the pilot ends |
| Donation records | As long as tax and nonprofit record-keeping laws require |
Where it is stored. NibbleCode and its server are in the United States, and our providers may process data in the United States and other countries.
4. Children's privacy
NibbleCode is built for kids and teens. During the pilot, accounts are open only to people 13 and over. Signing up with email asks for your birth year, and if you are under 13 we stop there and do not store anything about you. Signing up with GitHub relies on GitHub's own rule that its users are at least 13. Teens can sign up on their own. We follow the U.S. Children's Online Privacy Protection Act (COPPA) and our Youth Protection Policy.
- If we learn that someone under 13 has created an account during the pilot, we will delete the account and its data promptly.
- We do not knowingly collect personal information from children under 13 without verifiable parental consent.
- We have no chat, comments, forums, or messaging where users could post personal information, and learners cannot see each other's names or pictures. We will not open any community space until our Youth Protection Policy allows it and this policy is updated.
After the pilot: children under 13. When the pilot ends, NibbleCode opens to all ages. A child under 13 gets an account only after a parent or guardian gives permission. Until then, we keep only what we need to ask for it, and if no parent answers within 14 days, we delete it. Children's accounts are locked down:
- they sign in with an emailed code, not GitHub, since GitHub requires its users to be 13 or older
- they choose from pictures we provide and cannot upload their own
- they cannot see other learners' names or pictures, only those of NibbleCode staff
- they are never included in usage analytics
Donations are meant for adults. The donation form on our Donate page never loads unless someone presses "Show donation form", and we ask anyone under 18 to get a parent's help first.
Before sign-up opens to children under 13, we will update this section to describe exactly what we collect from them and how a parent gives permission, and we will tell each parent directly.
Parents and guardians who believe their child has given us information may ask us what we hold, ask us to delete it, and refuse further collection. Write to [email protected] and we will act within 7 days.
Schools and teachers using NibbleCode in a class do not need to give us student information beyond the email addresses needed to invite students, and we ask that they not send us anything else. Pilot results should be shared without names or other identifiers.
5. Your rights, wherever you live
We give everyone the same rights, whether or not a particular law requires it. You can ask us to:
- tell you what personal information we hold about you and give you a copy
- correct information that is wrong
- delete your information
- stop or limit how we use it, or object to a use
- send your information to you or another organization in a portable format
Send requests to [email protected]. We will answer within 30 days, may ask for information to confirm your identity, and will not charge you or treat you differently for asking. A parent or guardian can make requests for a child.
European Economic Area, United Kingdom, and Switzerland. If the GDPR or UK GDPR applies, we rely on these legal bases:
| Use | Legal basis |
|---|---|
| Creating and running your account; saving your progress and files | Performance of our agreement with you (our Terms & Conditions) |
| Delivering and securing the site; signed-in devices; server logs | Legitimate interests in running a safe, working educational service |
| Replying to messages; coordinating the pilot | Legitimate interests, or steps taken at your request |
| Pilot analytics | Your consent, which you can withdraw at any time |
| Disclosures required by law | Legal obligation |
We do not rely on a child's own consent for any processing. When data moves outside your region, our providers use approved safeguards such as the European Commission's Standard Contractual Clauses or the EU-U.S. Data Privacy Framework. You may also complain to your local data protection authority, though we would appreciate the chance to fix the problem first.
United States. Residents of states with consumer privacy laws, including New Jersey, may have the rights listed above. We honor them for every U.S. visitor. We do not sell personal information, share it for targeted advertising, or use it for profiling, so there is nothing to opt out of. We treat Global Privacy Control signals as an opt-out request if that ever changes.
6. Security, changes, and contact
Security. We use HTTPS on every page, keep each learner's terminal sealed off from everyone else's, limit access to personal information to the officers who need it, use two-factor authentication on our accounts, and choose providers with strong security practices. No system is perfectly secure; if a breach affects your information, we will notify you and the authorities as the law requires.
Cookies. See our Cookie Policy for the cookies and browser storage items we use, and how to say yes or no to pilot analytics.
Changes. If we change this policy, we will post the new version here with a new date. If a change would let us collect personal information from children under 13, we will not apply it to any child until a parent has consented.
Contact. NibbleCode Inc., 76 Arbor Drive, Howell, NJ, USA · [email protected]
