Biggymind
Try our Beta App

Biggymind Privacy Policy

Last updated: September 12, 2026

Who we are

Biggymind is an adaptive learning product.

Privacy contact: privacy@biggymind.com

This policy explains what information Biggymind collects, how it's used, and — because Biggymind is built for children — what rights parents and guardians have over their child's information under the Children's Online Privacy Protection Act (COPPA) and general privacy practice.

Who this policy covers

Biggymind is a guardian-first product: every child profile ("kid profile") is created and managed by an authenticated adult guardian. A child cannot create their own account, and no information is collected from a child before a guardian has created an account and added that child's profile.

Information we collect

About the guardian (adult account holder)

Standard account information needed to operate the service: an email address, an authentication credential (password, stored as a one-way hash — never in plaintext), and family/account settings a guardian configures (redemption caps and similar controls).

About a child (kid profile)

We collect only what's needed to personalize instruction and track a child's own learning progress — never a legal name, contact information, or any data broker-style profile. Specifically:

  • A display name — a first name or nickname a guardian chooses, never verified as (or required to be) the child's legal name.
  • An avatar selection — an illustrated mascot shape/color, not a photo.
  • A PIN — a 4–6 digit code, stored as a one-way cryptographic hash and checked only on our server, never stored or visible in plain text.
  • Enrolled grade level — used to target instructional content at the right level.
  • Date of birth — optional, entered by a guardian, used only to show the child's age to their own guardians. Never shown to the child.
  • Standardized test scores you choose to enter — optional MAP Reading RIT scores and test dates, typed in by a guardian. Used only as a reference point for the guardian and to check the accuracy of our own difficulty calibration. Never shown to the child, and never shared with the test's publisher or anyone else.
  • Learning activity — practice sessions, answers, scores, (for the read-aloud feature) text transcripts of what a child read aloud, and (for the Writing subject) the sentences and short pieces a child writes, with their planning notes, used to track mastery and adapt future content.
  • Gamification state — credits earned, streaks, badges, and a child's own self-written wishlist item names/notes.
  • Parental-control settings — whether a profile is active or archived, and any per-child overrides a guardian sets.
  • Cosmetic/accessibility preferences — font size, keyboard layout, and similar display settings.

What we do not collect, for a child, ever

We do not collect a child's email address, phone number, home address, precise geolocation, a real photograph or video, or any government-issued identification. This is a deliberate design choice, not an oversight.

How we use this information

Solely to operate and improve Biggymind for your own family: to generate and adapt practice content to your child's actual skill level, track progress over time, power the credits/rewards system, and give guardians visibility into their child's activity. We also use aggregated, internal usage data (such as how often features are used, and where users tend to stop partway through an activity) to understand how Biggymind is used and to improve the product — this is never sold, shared externally, or used to build an advertising profile of any individual child. We do not use a child's information for behavioral advertising, and Biggymind has no third-party advertising or analytics/tracking integrations of any kind today.

Where information goes (third parties)

AI-generated content (Anthropic). Biggymind uses Anthropic's API to generate practice questions, passages, and worked examples. Every request we send contains only abstract values — grade level, the skill being practiced, how many questions to generate, and (occasionally) a general image topic — never a child's name, ID, or any other identifying information. A child's identity never reaches this or any other AI provider.

Checking a child's own sentence (Anthropic). Two Writing activities send a child's own work to the same API so it can be checked. In Sentence Building, when a child arranges word tiles into a sentence we do not have on file, we ask whether that arrangement is also correct; and for short typed sentences ("Join these two sentences with because"), we ask whether the sentence does what was asked. These requests contain the practice item and the child's sentence only, never a name, ID, or anything else about the child. The sentence is kept with the child's practice history, which a guardian can review and delete.

A child's own writing (Anthropic). In the Composition activity a child plans and writes a short piece of their own, a paragraph or a few, in response to a writing prompt. After the child sends a piece in, we send the prompt and the piece to the same API so it can be read and given feedback, and a guardian can see how the child's writing is developing. The request contains the prompt, the child's planning notes, and the piece only, never a name, ID, grade, or anything else about the child. Before a piece is sent in, a check on our own server refuses it if it contains a phone number, email address, or street address, so those are never stored or sent. Every piece is kept, in full, with the child's practice history, where a guardian can read it and where it is deleted with the child's profile. If a piece suggests a child may be at risk, we show a quiet note to the child's own guardian; nothing is sent anywhere else.

Read-aloud scoring. When a child reads a passage aloud, scoring happens entirely on our own server, by comparing the resulting text against the stored passage. We never send an audio recording or transcript to any third-party scoring service.

Browser speech recognition. The read-aloud feature uses your web browser's own built-in speech recognition to convert a child's spoken words into text. In most Chromium-based browsers (e.g. Google Chrome), this built-in feature works by sending the audio to that browser vendor's own cloud transcription service — a data flow that happens inside your browser, that Biggymind does not initiate, control, or have a data-sharing agreement for. Biggymind itself never receives, stores, or transmits the audio — only the resulting text is sent to our server.

Images. Some reading passages include images loaded from Wikimedia Commons. Loading any image on the internet reveals the requesting device's IP address to the server hosting it — ordinary web behavior, not something specific to how Biggymind uses these images.

No advertising, analytics, or tracking. Biggymind does not use Google Analytics, advertising pixels, or any other third-party tracking or analytics tool. We do not sell or rent any information, and we do not share a child's information with any third party for their own marketing purposes.

Parental rights and controls

As a parent or guardian, you can, at any time, from your own account dashboard:

  • Review what's been collected — your dashboard already shows your child's practice sessions, progress, credits, and activity.
  • Archive a child's profile, which pauses all further activity and data collection for that profile while preserving their history.
  • Permanently delete a child's profile and every piece of data associated with it — every practice session, answer, transcript, credit, wishlist item, and badge. This is a real, complete deletion, not a soft flag. This action requires typing the child's name to confirm, since it cannot be undone.
  • Contact us at privacy@biggymind.com with any question about your child's data, including a request we haven't built a self-service tool for yet.

Consent

Before any information can be collected about a child, an adult must first create and verify their own guardian account, and only that authenticated adult can then create a profile for their child.

Data retention

We keep a child's information for as long as their profile remains active or archived — that is, until a parent or guardian chooses to permanently delete it. We do not automatically delete a profile or its history after a period of inactivity or after a child ages out of the product. We keep information this way because a multi-year learning record has real, ongoing value to a family, and deletion is always available, complete, and entirely within a guardian's own control, as described above.

Data security

Every piece of a child's information is scoped so that only their own family's guardians can see it, enforced at the database level. Every action that writes or changes a child's data — whether taken by a guardian or by the child using their own profile — is independently verified server-side to belong to the correct family before it's allowed. No online service can guarantee perfect security, but we've built and verified real, specific protections rather than assuming them.

Device approval. Before a new device can sign in with your family's code, a guardian must approve it from their own dashboard. To help you recognize a device you're approving, we store a general browser/operating system label (for example, "Safari on iPhone" — never a specific device model) and the country the request came from — never your city or precise location, and never your device's IP address itself. This information is used solely to secure your family's account — to let you see and control which devices can access it — and never for advertising, analytics, or any other purpose, and it is never shared with any third party.

Changes to this policy

If we make a material change to what we collect or how we use it, we'll update this policy and notify guardians before the change takes effect for their family.

Contact us

Questions about this policy, or about your child's information:
Email: privacy@biggymind.com