NibbleCode
NewsDonate
Log inJoin the pilot

© 2026 NibbleCode Inc. All rights reserved.

501(c)(3) nonprofit · EIN 42-5321894

About
Terms & ConditionsPrivacy PolicyCookie Policy

on main build 03040c1

Legal
  • Privacy Policy
  • Terms & Conditions
  • Cookie Policy
  • Youth Protection Policy

Cookie Policy

Last updated November 2, 2026

Yum, cookies!

1. Summary

NibbleCode uses cookies and browser storage to run the site, keep you signed in, and remember how you like things laid out. During our pilot, we also ask whether we may record how you use the site, so we can see which lessons work and which don't. That is off unless you say yes. We never use advertising or social media cookies ourselves, and nothing we use follows you to other websites. The one exception is the donation form on our Donate page, which is run by Givebutter and loads only if you choose to open it.

Cookies are small text files a website saves in your browser. "Local storage" is a similar feature that lets a website save information on your device. This policy covers both. It is part of our Privacy Policy.

2. What we use

Always on

Everything in this table is strictly necessary or stays on your device.

NameTypeSet byPurposeHow long
SESSIONCookieNibbleCodeKeeps you signed in, and holds a sign-up or GitHub sign-in while it is in progress, including the check that protects GitHub sign-in from forgery30 days after your last visit, or until you sign out
XSRF-TOKENCookieNibbleCodeProves that buttons and forms you use really came from our site, protecting you from cross-site request forgeryUntil you close your browser
tzCookieNibbleCodeYour time zone, so dates and "days active" match your own clock1 year
dashDensityCookieNibbleCodeWhether you chose the comfortable or compact dashboard1 year
themeCookieNibbleCodeWhether you chose the dark, light or match-device look1 year
analyticsConsentCookieNibbleCodeRemembers whether you said yes or no to pilot analytics, so we don't ask again1 year
introSeenLocal storageNibbleCodeRemembers that you've seen the intro animation, so it doesn't play every timeUntil you clear it
lessonSplit, lessonSidebarLocal storageNibbleCodeHow wide you made the lesson and practice panels, and whether the lesson list is openUntil you clear it
circuitPlacementLocal storageNibbleCodeWhether gates snap to the grid or go exactly where you drop them in the circuit builderUntil you clear it
circuitFlowLocal storageNibbleCodeWhether current visibly fills the wires in circuits, from the Current flow switch in PreferencesUntil you clear it
nibble:lesson-guideLocal storageNibbleCodeFor staff only: whether the lesson editor's guide is hiddenUntil you clear it
__cf_bmCookieCloudflare (our network and security provider)Tells people apart from bots to protect the site from attacks30 minutes
cf_clearanceCookieCloudflareRecords that your browser passed a security check, so you aren't asked againAs long as our Cloudflare security setting allows, 30 minutes by default
_cfuvidCookieCloudflareApplies rate limits fairly when many visitors share one network, such as a schoolUntil you close your browser

Cloudflare cookies may not appear on every visit; they are set only when security features need them.

When you sign in with GitHub, GitHub may set its own cookies on its own site. Those are covered by GitHub's cookie policy, not this one.

Pilot analytics (only if you say yes)

During the pilot, we record how people use NibbleCode so we can fix what's confusing and keep what works: 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. We record it only while you are signed in, linked to your account, and never while you are signed out. It is kept on our own server, never by an outside analytics company, and never for children under 13. No extra cookie is used: your choice is stored in analyticsConsent, above. We keep it until the pilot report is finished, and no more than 90 days after the pilot ends.

Donation form (only if you open it)

Our Donate page has a "Show donation form" button. Until you press it, nothing from Givebutter loads, and the form never loads on any other page. When you press it, the page loads Givebutter's donation form, and that form loads services from other companies. They may set their own cookies or store information in your browser, and some of them may recognize you on other websites. We don't control them; they are covered by their own privacy and cookie policies, not this one.

CompanyWhat it does in the form
GivebutterRuns the donation form, processes your donation, and measures how its form is used
Cloudflare and hCaptchaSecurity checks that keep bots out of the form
Stripe and PayPal (including Braintree)Take card, PayPal and other payments, and check for fraud
GoogleGoogle Pay, address suggestions, and Google Analytics for Givebutter
Meta (Facebook)Facebook's software, which Givebutter includes in its form

When we tested the form, it set security cookies from Cloudflare and hCaptcha (up to 30 days) and cookies from PayPal (up to 400 days). The exact list is up to Givebutter and may change.

The donation form is meant for adults. If you are under 18, please ask a parent before opening it.

3. Your choices

Saying yes or no. The first time you sign in during the pilot, we ask whether you'll allow pilot analytics. "Allow" and "No thanks" are equally easy, and nothing is recorded unless you choose Allow. Saying no doesn't change anything else about NibbleCode. You can change your mind at any time from Cookie settings at the bottom of every page. Turning analytics off stops recording right away, and you can ask [email protected] to delete what was already recorded.

Controlling cookies and storage. You can block or delete cookies and site data in your browser settings. Deleting them signs you out, resets your layout and display choices, and forgets your analytics choice, so we'll ask again; your lesson progress and saved work stay safe in your account. Blocking our sign-in cookies will stop you from logging in, and blocking Cloudflare's cookies may cause extra security checks.

Changes. If what we store changes, we will update this page and its date before the change goes live.

Questions. [email protected]