Student data privacy, FERPA, and COPPA for school stores
Understand FERPA school-official rules, COPPA school-consent limits, state student-privacy laws, and six written questions for any school store POS vendor.
Quick answer
A school store POS handles student operator accounts, roles, and shift logs that districts treat under FERPA and state student-privacy laws. Require a signed Data Privacy Agreement, anonymous counter checkout, and written deletion timelines before connecting any vendor to your school store.
When a business teacher proposes a point-of-sale system for a student-run store, district IT and privacy review can stall the launch. A generic retail vendor may take weeks to answer basic questions about student accounts, card data, and data deletion.
This guide breaks down how FERPA, COPPA, and state student-privacy laws apply to a school store POS, plus six written questions to send every vendor before scheduling a pilot.
Legal note: This guide is educational context for advisors and district reviewers, not legal advice. Confirm contract terms with your district data privacy officer or legal counsel.
Why a school store POS triggers district privacy review
Even a simple campus store handles two different kinds of records. Keeping those two streams clearly separated makes privacy review far cleaner.
- Student operator records: Student names, school emails, assigned roles, and optional register PINs or shift logs when enabled. Districts routinely govern these records under FERPA and state student-privacy laws.
- Customer transaction records: Items sold, timestamps, tender type (cash or card), and financial totals. If a register asks students for an email address or phone number for a digital receipt, it starts creating buyer profiles tied to minors.
A school-ready POS keeps buyers completely anonymous at the counter and limits student operator data strictly to what’s needed to run the store and teach the class.
How FERPA governs your POS vendor
The Family Educational Rights and Privacy Act (FERPA) restricts sharing education records with outside software vendors without parent consent. Districts authorize school software under the school-official exception in 34 CFR 99.31(a)(1), where all four requirements must hold.
| FERPA school-official requirement | What to verify in the vendor contract |
|---|---|
| Institutional service or function | The POS performs a store-operations or instructional function the school would otherwise manage itself. |
| Direct control | The written agreement gives your district direct control over how student records are used, exported, and deleted. |
| Legitimate educational interest | Vendor access is limited strictly to operating the store, supporting instruction, and maintaining audit books. |
| Re-disclosure ban | The vendor may not re-disclose student records to third parties or advertisers, and named subprocessors stay bound to the same limits. |
A consumer click-through terms of service rarely grants a district direct control. Require a signed Data Privacy Agreement such as the Student Data Privacy Consortium National Data Privacy Agreement (NDPA) or your state’s standard addendum.
Where COPPA fits (and the April 2026 rule update)
The Children’s Online Privacy Protection Act (COPPA) applies to children under 13. High school store operators are 14 to 18, though combined 6-12 schools, middle school spirit carts, and eighth-grade CTE previews cross that line.
Under FTC COPPA guidance (Section N), a school may authorize data collection from students under 13 only for an approved educational context. The vendor can never use that data for commercial purposes. The FTC’s amended COPPA Rule took effect in 2025 with a full compliance deadline of April 22, 2026, tightening written data retention schedules and separate opt-in rules for third-party disclosures.
Even in an all-high-school building, districts increasingly hold every vendor to the same baseline: minimal collection, zero commercial profiling, and a published retention schedule.
State student-privacy laws bind vendors directly
Unlike FERPA, state student-privacy laws place direct statutory duties on ed-tech and school software vendors. Washington’s SUPER Act, the Texas Student Privacy Act, Idaho Code 33-133, and California’s SOPIPA bar vendors from selling student data. They also prohibit targeted advertising and non-educational student profiling.
Check whether your district maintains an approved-vendor registry through your state privacy consortium. Vendors that already sign the NDPA clear these reviews far faster than retail processors built for cafes and boutiques.
Six written questions to ask any school store POS vendor
Send these six questions to every finalist before signing a purchase order, and keep the written replies with your district procurement packet.
- Will you sign the NDPA or our district’s state student data privacy addendum? Ask for a redline timeline upfront.
- Do your registers collect buyer names, emails, or phone numbers at checkout? Confirm whether digital receipt prompts or loyalty profiles can be disabled completely.
- Who is the merchant of record on the payment account, and whose EIN receives the 1099-K? Confirm funds settle directly to the school or district bank account rather than a teacher’s personal account.
- Do full payment card numbers ever touch your application servers? Verify end-to-end encryption to a PCI Level 1 payment processor, retaining at most the last 4 digits for receipts.
- What is your exact retention schedule and written deletion timeline for student records? Confirm that financial ledgers remain intact and de-identified when student names are deleted.
- If your company is acquired, do our signed district data privacy terms stay in force? Require written confirmation in the agreement.
School Store Vendor Evaluation Worksheet
Side-by-side checklist for advisor, IT, and business-office POS review.
How RallyOrder handles school privacy and money
RallyOrder publishes its full data covenants, retention table, and payment architecture openly in the RallyOrder Trust Center. Registers keep buyers anonymous at the counter, and full card numbers flow encrypted straight to Stripe (retaining only the last 4 digits). Schools stay the merchant of record under their own EIN, and RallyOrder signs the NDPA with districts.
When a district requests student deletion, RallyOrder delivers an export if requested and deletes student identifiers within 60 days with written confirmation. De-identified financial records stay intact for your business office. Share our Trust Center or what administrators ask us first with your IT and finance reviewers to cut approval time before launch.
Frequently asked questions
Does FERPA apply to a high school store point-of-sale system?
FERPA binds the school district rather than the vendor directly. When a POS stores student operator records, your district authorizes the vendor under the school-official exception in 34 CFR 99.31(a)(1) through a written contract.
Does COPPA apply to high school stores?
COPPA protects children under 13, so high school students aged 14 to 18 sit outside its age threshold. Districts with middle school operators or combined 6-12 campuses still verify COPPA school-consent rules and the FTC amended rule deadline of April 22, 2026.
Should a school store register collect student buyer names or emails?
No. Counter checkout only needs the items sold and payment type. Keeping buyers anonymous at the register prevents your school from accumulating unnecessary student purchase profiles.
What agreement should a district ask a school store POS vendor to sign?
Ask for the Student Data Privacy Consortium National Data Privacy Agreement (NDPA) or your state-specific student data privacy addendum. Verify that it bars selling student data, bars targeted advertising, and sets a written deletion window.