Dabbledfor Schools
LibraryToolsPricingSign inSign upBook a demo
LibraryToolsPricingSign upBook a demo

FERPA

How Dabbled for Schools handles education records · Last updated November 4, 2026

The short version

We hold very little that could be an education record, and what we hold belongs to the school. A student here is a nickname and the activities made under it — no name, no email, no birthday. Where a school connects its roster, we keep the roster's identifier for each student and a grade level, never a name, and which nickname that identifier matches. We use that record only to run the product for the school, we act on the school's instructions about it, and we delete it when the school says so.

What could be an education record

  • A student's nickname and the class it belongs to. The nickname is chosen by the student or teacher, and the product has no field for a legal name.
  • Activities a student makes in a class, attributed to that nickname, including the description they wrote and the activity that was built from it.
  • Roster identifiers, when a school connects its student information system: the roster's own id for a student, a grade level, which section they are in, and which nickname is theirs. Names from an upload are kept for one day for matching and then deleted. Parent and guardian rows in a roster are ignored.
  • Lesson notes a teacher writes about a class — what was covered and how it went. These are private to the teacher who wrote them and can describe a class's progress in general terms.

That is the complete list. There are no assessments, attendance, discipline records, health information, or contact details for students anywhere in the product.

Our role

We act as a service provider to the school. The school decides which students use the product, supervises that use, and directs what happens to the records it produces. We do not use education records for any purpose other than providing the service to that school, and we do not disclose them to anyone else except the subprocessors listed below, who need them to run the service.

Who at the school can see what

Access follows the school's own roles. A school administrator can see the school's activities, classes and students. A teacher sees their own classes, their own students' work and their own lesson notes. Nobody outside the school sees a school's records unless the school publishes an activity to the public library, and a published activity is attributed to the school, never to the student.

Parents and eligible students

A parent's right to inspect and review a student's education records runs through the school, which holds the account and knows which nickname is which child (the product knows at most which roster identifier it matches). Ask the school; the school can see everything the product holds about a student and can request a copy or a deletion from us at john@dabbled.ai.

Deletion

A teacher or administrator can delete activities and lesson notes in the product at any time, and deleting means deleting. A school can ask us to remove a student, a class or the whole school, and we will. Backups roll off on their own schedule, so a deleted item may persist in a backup for up to 30 days after it disappears from the product.

Subprocessors

  • Anthropic — activity descriptions, follow-up answers and existing activity content are sent to Anthropic's API to build, revise and tag activities and to answer questions. Content sent through the API is not used to train models. A student's nickname is not part of what is sent.
  • Stripe — school billing; no student data.
  • Our email provider — staff verification emails; no student data.
  • Our hosting provider — everything, in the ordinary sense that the application runs on their machines, in the United States.

Security

Passwords are stored as bcrypt hashes. A student's session token and recovery code are the only credentials a student has, and neither identifies them outside the product. Traffic is served over HTTPS. Personal information is kept out of server logs. If we discover a breach affecting a school's education records, we will notify that school within 72 hours of discovering it, with what we know at the time and what we are doing about it, and keep the school updated as we learn more.

Changes

If we change how education records are handled we will update the date at the top and tell schools directly.

See also: Privacy Policy · COPPA · State privacy laws · Questions: john@dabbled.ai

LibraryToolsChatGPT & ClaudePricingWorkshopsFAQContact
PrivacyTermsAI and dataAccessibilityDOE guidanceFor IT

© 2026 Equilibrium Software Solutions LLC