A well-meaning fee policy can create a federal privacy violation. Here's how to stay on the right side of the rules.
A district technology director recently asked a legit question: a student's device has been reported missing, it hasn't checked in since the day it disappeared, and it isn't coming back. Should the family pay the full replacement cost, or should the fee be scaled by whether the student qualifies for free or reduced-price meals?
The instinct behind the question is good. A $350 Chromebook bill means very different things to different families, and a sliding scale feels fair. But that second option, using meal eligibility data to set or waive device fees, is where a sensible equity idea can turn into a compliance problem. And in many districts the person proposing it doesn't know that.
This post covers what makes the idea risky, what data you can use, and how to build a fair policy that holds up.
Before you act on anything here: this post is general information, not legal advice. Confirm the details with your nutrition services director, your state child nutrition agency, and district legal counsel before changing policy.
Problem 1: Meal eligibility data is federally protected
Free and reduced-price eligibility comes from the National School Lunch Program, and the rules for sharing it are stricter than most staff realize. Under the Richard B. Russell National School Lunch Act and its regulations (7 CFR 245.6), a student's eligibility information may be disclosed only to specific recipients for specific purposes. Beyond those limited exceptions, using it for any purpose other than determining meal eligibility generally requires parental consent first.
Three points surprise people:
- Sharing inside the district counts. A nutrition office emailing its eligibility list to the technology department, or an IT director pulling the eligibility field from the student information system (SIS), is a disclosure. Having both offices on the same payroll doesn't make it exempt.
- A device fee waiver is not meal administration. Setting a replacement fee is a local district decision, not part of running the meal program. If parents haven't consented, the eligibility list generally isn't available for this purpose.
- There are real penalties. Federal law (42 U.S.C. 1758(b)(6)(C)) provides for a fine of up to $1,000, up to one year in prison, or both for anyone who discloses eligibility information in a way the law doesn't authorize. Some states add their own penalties on top.
The SIS adds a hidden risk. Many systems show a meal eligibility flag on the student record, and anyone whose role grants access can see it. Being able to see the field in a report doesn't mean you're allowed to use it.
Problem 2: The data may not exist, or may not be accurate
Many schools now serve free meals to every student through the Community Eligibility Provision (CEP). CEP schools generally don't collect household meal applications at all, so there is no per-student eligibility flag to base a fee scale on. Districts that try anyway end up with inconsistent results: a student at a CEP school and a student at a non-CEP school with identical family income could be charged different amounts.
Even outside CEP, meal eligibility is a snapshot taken at application time. It wasn't designed to measure a family's ability to pay a device bill months later.
Problem 3: State fee laws may limit what you can charge at all (California example)
Many states have their own rules about charging students. California's are among the strictest:
- Free public education. California Education Code 49011 bars public schools from charging a "pupil fee" for participating in an educational activity, and 49010 defines that term broadly enough to include deposits. A mandatory device deposit or required "insurance" fee as a condition of receiving a school-issued device is very likely prohibited.
- No damage deposits. A California Attorney General opinion indicates schools may not require deposits meant to guarantee payment for breakage, damage, or loss of school property.
- Charging for actual loss works differently. California Education Code 48904 generally makes parents liable when a student willfully damages school property or fails to return loaned property. It also comes with specific notice and due-process steps, and limits on what districts can withhold, such as grades, diplomas or transcripts. Read the current text before relying on it.
- Families can file complaints. Pupil fee complaints in California can be filed through the Uniform Complaint Procedures, so a poorly designed fee policy can become a formal complaint quickly.
If you're outside California, look up your own state's rules on pupil fees and parent liability for school property. They vary widely.
Problem 4: Collections and billing involve student records too
Sending an unpaid device balance to a collection agency, or listing it on a fee report shared with outside parties, means disclosing information drawn from student records. Treat it as a FERPA question. If an outside vendor handles billing or collections, make sure the contract and procedures meet FERPA's requirements for third parties acting on the district's behalf, and share only the minimum information needed.
Problem 5: Location tracking needs to be disclosed up front
Before declaring a device lost, many districts use their mobile device management (MDM) tools to check where it last connected. That's generally reasonable for district-owned equipment, but families should be told in advance. Put it in your acceptable use policy or device agreement, and check whether your state has laws limiting location tracking of devices students take home.
What you can use
| Data | Usable for device fees? | Notes |
|---|---|---|
| Device asset records (serial number, asset tag, assigned student) | Yes | This is your core record. Keep it accurate. |
| MDM last check-in date and location | Yes, with disclosure | Shows when and where the device was last active. Disclose tracking in your device agreement. |
| Signed device agreement or acceptable use policy | Yes | Documents what the family agreed to. |
| Police or incident report for theft | Yes | Often the basis for waiving or reducing a fee. |
| Hardship information the family provides on its own form | Yes | Collected separately, with clear consent. |
| Free/reduced meal eligibility (without parental consent) | Generally no | Protected under 7 CFR 245.6. |
| Free/reduced meal eligibility (with documented parental consent) | Possibly | Confirm the consent language and permitted uses with your state agency. |
| Aggregate counts (e.g., "42 devices lost this year") | Yes | Fine for reporting and budgeting as long as no individual student can be identified. |
A fair approach that holds up
You can still keep fees fair without relying on protected data:
- Adopt a written board policy. Define what counts as "lost," "stolen" and "damaged," set the fee schedule, and include a clear process for reductions, waivers and payment plans.
- Use a separate hardship form. Let any family request a reduced fee or payment plan through a short form that is separate from the meal application, so you collect only what the family chooses to share.
- If you want to use meal eligibility data, get consent properly. Some districts add an optional consent statement to the meal application that lets families allow their eligibility status to be shared with other district programs. Work with your nutrition services office and state agency to word it correctly, and record each family's answer.
- Limit who can see the eligibility field. In the SIS, restrict the meal eligibility field to staff who are authorized to see it. Technology staff with broad database access should be reminded in writing that access doesn't authorize use.
- Build in due process. Send written notice, give families a chance to respond, and allow appeals. This is required in many states and is good practice everywhere.
- Don't make fees a condition of access. In states like California, deposits or mandatory insurance as a condition of receiving a device can be an illegal pupil fee. Optional, truly voluntary programs are treated differently. Confirm with counsel.
- Report in aggregate. For board reports and budget planning, share totals, not lists of students.
Bottom line
A sliding-scale fee based on meal eligibility looks like a fair policy, but in many districts it's a federal disclosure problem, may rely on data that doesn't exist, and may run into state fee law. The fix isn't to give up on fairness. Build the policy on data you're allowed to use, collect hardship information separately with consent, and keep the meal program's data inside the meal program.
Before you change your device fee policy, talk to your nutrition services director, your state child nutrition agency and your district's legal counsel.
Sources and further reading
- USDA FNS: Disclosure Requirements for Child Nutrition Programs
- 7 CFR 245.6: Disclosure of eligibility information (eCFR)
- 42 U.S.C. 1758 (Cornell LII)
- Nebraska Dept. of Education: Confidentiality and Disclosure of Free and Reduced Data
- California Education Code 49011 and 49010
- CDE Fiscal Management Advisory 23-02: Pupil Fees
- AALRR: How Distance Learning Highlighted Ed Tech Inequities (discusses the Attorney General opinion on damage deposits)
- ACLU of Southern California: AB 1575 FAQ
This article is for general information and is not legal advice. Laws and guidance change; verify current requirements with your state agency and legal counsel.