
Best For
Teams this article is built to help
Category: Administrator Resources
Evidence
What backs this guide
Curated references are cited at the end of the article.
Materials
What you can leave with
- Condensed key takeaways
- Primary downloadable resource
- 3 bonus downloads
- Interactive self-check quiz
As the spring semester approaches, many school leaders are fielding requests to approve a new tool for the spring semester, and behavior data software is one of the more sensitive approvals on that list. The approach that works: send every vendor the same written questions, grouped by topic, and accept answers that point to a contract clause or a published document rather than a sales promise. The questions below cover the legal basis for sharing records, children's privacy rules, state law, the data processing agreement, where the data goes, who can see it, what happens when something goes wrong, and how the relationship ends.
Why Behavior Data Deserves Its Own Review
A grade book records what a student produced. A behavior record describes what a student did on a hard day: the incident, what came before it, how adults responded, and often a working hypothesis about why. It may include notes about sleep, a medication change, or a family event that staff learned in confidence. Narrative entries sometimes name other students. These records travel into FBA reports, IEP meetings, and discipline decisions, and they can follow a student for years.
That is why a generic software checklist falls short. The questions in this post assume the tool will hold identifiable, narrative records about students with disabilities, because most behavior data tools will. If your team needs a refresher on how records are handled inside the school, start with our FERPA and behavior data privacy workflow. This post is about the vendor.
One step comes before any question: decide what data the work actually requires. If frequency counts and ABC entries will answer your team's questions (our data collection guide walks through choosing a method), a vendor that asks for diagnoses, birth dates, or home addresses should be able to explain why it needs them.
Legal Basis: FERPA and COPPA
FERPA's school official exception
Most schools share education records with a software vendor under FERPA's school official exception. A contractor can be treated as a school official only if it performs an institutional service or function the school would otherwise use employees for, is under the school's direct control with respect to the use and maintenance of education records, and is subject to FERPA's limits on use and redisclosure (34 C.F.R. § 99.31(a)(1)(i)(B)). The same section requires schools to use reasonable methods to make sure school officials reach only the records in which they have a legitimate educational interest (§ 99.31(a)(1)(ii)).
A vendor saying "we're FERPA compliant" is a starting point, not an answer. FERPA's obligations sit with the school or district. The vendor's job is to accept terms that let you meet them. Ask:
- Which document establishes that you act as a school official under our direction, and where does it limit your use and redisclosure of student records?
- Can you change your terms without notifying us? Federal guidance urges caution with click-through terms that allow amendment without notice, because they make direct control hard to show (Privacy Technical Assistance Center, 2014).
- Do you use student data for any purpose other than providing the service to us?
COPPA in schools
The Children's Online Privacy Protection Act rule governs operators that collect personal information online from children under 13. When the Federal Trade Commission published its amended rule in April 2025 (effective June 23, 2025, with most requirements in force since April 22, 2026), it chose not to finalize its proposed provisions on ed tech and school authorization, citing possible changes to the FERPA regulations. It said it would keep enforcing COPPA in the ed tech context consistent with its existing guidance (Federal Trade Commission, 2025).
That guidance says a school can act as the parent's agent and consent to collection only in the educational context, where the operator collects the information for the use and benefit of the school and for no other commercial purpose. It also says operators should not claim in their terms that the school is responsible for COPPA compliance (Federal Trade Commission, n.d.). Ask:
- Do children ever use the product directly, through a student login, a self-monitoring screen, or a survey? If not, where is that stated?
- If they do, what is collected from them, and is any of it used beyond the school's purpose?
- Where is your written data retention policy for children's information? The amended rule requires operators to maintain one and include it in their online notice (16 C.F.R. § 312.10, as amended in 2025).
Many behavior data tools are used only by adults. That does not end the review, because the records staff enter are still education records. Ask your counsel how COPPA applies to your specific use.
State Law and the Data Processing Agreement
Many states have their own student privacy statutes, and some reach well past FERPA. Two well-known examples:
- California's Student Online Personal Information Protection Act bars covered K-12 operators from targeted advertising, from building student profiles except for K-12 school purposes, and from selling student information. It also requires reasonable security and deletion when a school or district requests it (Cal. Bus. & Prof. Code § 22584).
- Illinois's Student Online Personal Protection Act requires a written agreement before covered information is transferred and requires the school to publish that agreement. Operators must notify the school of a breach no later than 30 calendar days after determining one occurred and must give the school a list of third parties receiving covered information (105 ILCS 85/15).
Those are two examples, not a survey. Check your own state's law and your district's policy before you compare vendors.
Then ask whether the vendor will sign your district's agreement or your state's version of the National Data Privacy Agreement (NDPA). The NDPA is a standard student data privacy contract created by the Student Data Privacy Consortium, a special interest group of the Access 4 Learning Community, to set common expectations for how student data will be handled. It is adapted for state requirements and is available to the Community's members (Student Data Privacy Consortium, n.d.). Signed versions can include a general offer exhibit through which a vendor extends the privacy terms it signed with one district to other districts that accept them.
- Will you sign our agreement or our state's NDPA version? If you have redlines, what are they?
- Does a signed agreement take precedence over your click-through terms?
- Do you already have a signed agreement with another district in our state?
Where the Data Goes: Subprocessors, Location, and AI
Every behavior data tool relies on other companies for hosting, email, billing, monitoring, and increasingly AI. Each of those companies is part of your review.
Questions About Data Flows
Subprocessors
Is there a published list of every provider that handles our data, with each one's purpose? How will you tell us about changes, and can we object?
Location
Where is our data stored and processed, including by subprocessors? If we need a location restriction, will you put it in the contract?
AI training
Is student data used to train AI models, yours or anyone else's? Please answer in writing.
AI processing
Which provider processes data for AI features, and is it on the subprocessor list? Are names removed before processing, and where does that not apply (audio or uploaded documents, for example)? Can AI features be turned off for our district?
Also ask how AI output is labeled. A draft hypothesis or summary should be clearly marked as something a qualified professional reviews before anyone acts on it. Our guide to ethical AI use in behavior analysis covers the review side of that question.
Who Can See It: Encryption, Roles, and Logs
Start with the basics: is data encrypted in transit and at rest, and which vendor employees can reach customer data, under what conditions? Then spend most of your time on access inside your own district, because that is where behavior data most often reaches people who do not need it.
Paraprofessionals and substitutes are the hard case. A para assigned to one student usually needs that student's plan and log, not the whole caseload. Federal special education rules require each participating agency to name one official responsible for confidentiality, to train everyone who collects or uses personally identifiable information, and to keep a current public list of the names and positions of employees who may have access (34 C.F.R. § 300.623). Your software should make those duties easier, not harder. Ask:
- Can access be limited by role and to assigned students?
- Can a substitute's access be time-limited so it ends on its own?
- How quickly can we remove a staff member who leaves mid-year?
- Which sign-in methods do you support today, and is single sign-on available or only planned?
Audit logs come next. FERPA requires a record of each request for and disclosure of education records, but not for disclosures to school officials (34 C.F.R. § 99.32(d)). The special education regulations require a record of parties obtaining access to records, except parents and the agency's authorized employees (34 C.F.R. § 300.614). Ask whether access by vendor staff must be logged under § 300.614, since its exception covers only the agency's own authorized employees. Whatever your counsel concludes those rules require, a log of who viewed, edited, and exported a student's records is the evidence you will want when a parent or auditor asks. Can administrators see that history? Does it include the vendor's own support staff? Can you export it?
Breach Notice, Retention, and the End of the Contract
Breach notice duties come from state law and your contract, so get them in writing. Ask what counts as an incident, how quickly the vendor notifies you, what information it provides, and who notifies families. Illinois, for example, requires the written agreement to describe how breach costs attributed to the operator are divided between the operator and the school (105 ILCS 85/15).
Retention and deletion deserve the same care, both during the contract and at the end. When information collected for special education is no longer needed to provide services, the school must tell parents, and it must destroy the information at the parents' request, with a narrow exception for basic permanent-record data (34 C.F.R. § 300.624). That means your vendor needs to delete one student's records on request, not only a whole account.
Ask About the Exit Before You Sign
In what format can we export a complete student record, and can we read it without your software? How long after termination is data deleted or de-identified, including backups? What exceptions apply, and will you confirm deletion in writing?
For the school-side decisions about what to keep, export, or destroy, see our guide to behavior data archives and retention.
Parent Access Requests
Parents have a right to inspect and review their child's education records. Under the special education regulations, the agency must comply without unnecessary delay, before any IEP meeting, hearing, or resolution session, and in no case more than 45 days after the request (34 C.F.R. § 300.613). If behavior records live in a vendor's system, the vendor's export is part of your compliance timeline.
- Can we export one student's complete record, including notes and attachments, on short notice?
- If a parent contacts you directly, will you route the request to us?
How Classroom Pulse Publishes Its Answers
Vendors should publish their answers before a buyer has to ask. Our Trust Center gathers ours in one place. The DPA names the customer as the controller and Classroom Pulse as the processor, commits us not to sell customer personal data or use student data for targeted advertising, and describes an opportunity to export at termination followed by deletion or de-identification, with the exceptions stated. The subprocessor list names each provider and its purpose, including the AI provider and a note on where name replacement does not apply. The security page describes incident notice and says plainly that enterprise single sign-on, SCIM provisioning, and automated roster sync are not available today. The state addenda page explains how district templates are reviewed, and the student privacy pledge page lists our commitments. There are no student logins. Some assessments, such as a preference survey and a student self-report interview, can be completed by a student on a staff member's signed-in device, so include them in your COPPA review.
Those pages are product and procurement documentation, not legal advice, and they do not replace your district's own determinations. Hold us to the same questions you would ask any vendor, and ask for the answers in writing.
Frequently Asked Questions
Does a free plan still need district review?
Yes. Federal guidance recommends that free online educational services go through the same or a similar approval process as paid ones, and it notes that clicking "accept" on a provider's terms creates a contractual relationship much like signing a contract (Privacy Technical Assistance Center, 2014). Price does not change what happens to student records.
What if a vendor won't sign our data privacy agreement?
Ask for its redlines in writing and send them to whoever reviews contracts for your district. Some changes are routine. A refusal to accept use limits, deletion terms, or breach notice is a reason to keep looking.
Who should run this review?
Whoever your district has designated for privacy and technology review, usually with input from special education leadership. Teachers and specialists can help by collecting the vendor's documents and explaining how the tool would be used day to day. Our behavior tracking technology selection guide covers the workflow questions that sit alongside this privacy review.
Ask Once, in Writing, Every Time
The goal is not to find a vendor with perfect answers. It is to get every answer on paper, compare vendors on the same questions, and know exactly which terms protect the students whose hardest days end up in these records.
To send the same questions to every vendor, use the Behavior Data Vendor Privacy Review Checklist, a two-page form with space for each vendor's answers and follow-up owners. More resources for district teams are on the district resources page.
References
Assistance to States for the Education of Children With Disabilities, 34 C.F.R. §§ 300.613, 300.614, 300.623, 300.624. https://www.law.cornell.edu/cfr/text/34/300.613
Cal. Bus. & Prof. Code § 22584 (Student Online Personal Information Protection Act). https://leginfo.legislature.ca.gov/faces/codes_displaySection.xhtml?lawCode=BPC§ionNum=22584
Family Educational Rights and Privacy, 34 C.F.R. §§ 99.31, 99.32. https://www.law.cornell.edu/cfr/text/34/99.31
Federal Trade Commission. (n.d.). Complying with COPPA: Frequently asked questions (Section N, COPPA and schools). https://www.ftc.gov/business-guidance/resources/complying-coppa-frequently-asked-questions
Federal Trade Commission. (2025). Children's Online Privacy Protection Rule; Final rule amendments. Federal Register, 90(76), 16918-16983. https://www.govinfo.gov/content/pkg/FR-2025-04-22/html/2025-05904.htm
Illinois Student Online Personal Protection Act, 105 ILCS 85/15 (operator duties). https://www.ilga.gov/Documents/legislation/ilcs/documents/010500850K15.htm
Privacy Technical Assistance Center. (2014). Protecting student privacy while using online educational services: Requirements and best practices (PTAC-FAQ-3). U.S. Department of Education. https://studentprivacy.ed.gov/resources/protecting-student-privacy-while-using-online-educational-services-requirements-and-best
Student Data Privacy Consortium. (n.d.). National Data Privacy Agreement (NDPA). Access 4 Learning Community. https://privacy.a4l.org/national-dpa/
Put This Into Practice
Turn the article into action with ready-to-use materials. Downloads stay open; emailed resources and quiz results are opt-in.
Key Takeaways
- Behavior records hold narrative, sensitive detail about students with disabilities, so they need a privacy review beyond a generic software checklist
- Ask each vendor to show in writing how it meets FERPA's school official conditions: an institutional function, your direct control over the records, and limits on use and redisclosure
- The FTC's 2025 COPPA amendments did not codify school authorization; existing FTC guidance limits school consent to the educational context and the school's benefit
- Check your own state's student privacy law and ask whether the vendor will sign your district's agreement or your state's version of the National Data Privacy Agreement
- Get written answers on subprocessors, data location, AI training, role-based access for paras and substitutes, access logs, breach notice, and deletion at contract end
Behavior Data Vendor Privacy Review Checklist
A two-page checklist for sending the same student privacy questions to every behavior data software vendor and recording their written answers.
- FERPA, COPPA, and state law questions
- Subprocessor, data location, and AI training questions
- Access, breach notice, deletion, and parent request checks
Email collection is reserved for administrator or procurement resources.
Bonus Materials
Clean downloads to pair with this article
Download resources directly or send a copy to your inbox. Marketing updates are optional.
FERPA Compliance Checklist for Behavior Data
Storage, access, and retention practices for student behavior records
Behavior Data Retention Checklist
Use this checklist to review archives, duplicate exports, working notes, and secure deletion decisions against district policy.
Behavior Technology Selection Rubric
A school-ready rubric for comparing behavior tracking tools by workflow fit, data quality, privacy, reporting, and adoption risk.
Is Your Vendor Privacy Review Ready?
Check whether your questions for behavior data software vendors will produce written answers you can rely on.
Tags:
For school and district leaders
See How We Answer These Questions
The Trust Center collects our DPA, subprocessor list, security summary, and state addenda workflow in one place for district review.
Review Our Privacy DocumentsAbout the Author

Bobby Hillman is a Board Certified Behavior Analyst and Licensed Behavior Analyst with an M.Ed. in Special Education and more than 25 years in public special education and autism services. He works as a Behavior Instructional Specialist and founded Classroom Pulse to reduce the documentation load on classroom teams while keeping the detail FBA and BIP work requires.
About Classroom PulseRelated Articles
The Five-Minute End-of-Day Huddle: How Teams Review Behavior Data
A five-minute end-of-day routine for teachers and paraprofessionals: what happened, gaps in the data, one change for tomorrow, who logs what, and ground rules for privacy.
Reading Your Child's IEP Progress Report on a Behavior Goal
A plain-language guide for families: what progress report codes usually mean, the data behind the rating, questions to ask, and what should happen when progress is not enough.
Writing IEP Progress Reports for Behavior Goals: What the Data Should Say
A six-part narrative for IEP progress reports on behavior goals: baseline, current level, trend, measurement, whether progress is sufficient, and what changes next, with examples.
