Education & nonprofits
Student data privacy and backups: FERPA, COPPA and state student-privacy laws in plain terms for school IT
Your student information system gets a privacy review, but its backups usually don't, even though they hold the same records for longer and in more places. Here's what FERPA, COPPA and state student-privacy laws actually require of data at rest, why client-side encryption matters once backups leave the building, and a vendor checklist for your next NDPA review.
Your student information system gets a privacy review. Your LMS gets a privacy review. The backup of both usually doesn't, even though it holds the same records, for longer, in more places.
That gap matters because the US student-privacy rules follow the data, not the system it lives in. A nightly copy of the SIS database on a cloud bucket is student data, and so is the seven-year-old archive nobody remembers configuring. This article walks through what FERPA, COPPA and the main state laws actually ask of data at rest, why encrypting backups before they leave the building is the control that does the most work, how to handle records for students who have left, and what to ask a vendor when the privacy agreement lands on your desk.
It is written for district and school IT staff, and for the MSPs who run IT for them. It is a plain-terms overview, not legal advice.
What the laws actually require of data at rest
Short version: federal law sets a "reasonable" bar and leaves the controls to you; the states are where the specific requirements live, and New York is the only one that names encryption at rest outright.
FERPA applies to schools and districts that receive federal education funding. It does not list technical controls. The Department of Education's position is that FERPA requires "reasonable methods" to protect education records, not any particular product or setting (studentprivacy.ed.gov). Vendors can receive records without parental consent under the "school official" exception, but only while they stay under the school's direct control for how the data is used and kept. FERPA has no general destruction schedule either, with one catch: a school may not destroy a record while a request to inspect it is outstanding (PTAC, Best Practices for Data Destruction).
COPPA binds the operators of online services aimed at children under 13, so in a school it mostly binds your vendors. The FTC's amended rule took full effect on April 22, 2026 (Federal Register). Two changes reach backups directly:
A written information security program, with a named coordinator and at least an annual review (BBB National Programs).
A written, published data retention policy that states why each kind of children's data is collected, why it is kept, and when it is deleted. Keeping it indefinitely is no longer allowed (JD Supra).
The FTC dropped its proposal to write school consent into the rule, so schools still authorize ed-tech use under the FTC's existing guidance, which limits it to educational use with no commercial purpose (K-12 Dive).
State laws are where most of the concrete duties sit. Three that come up often:
Law | Who it binds | Data at rest | Deletion | Breach notice |
|---|---|---|---|---|
New York Education Law 2-d / Part 121 | Schools, BOCES and their contractors | Encryption in motion and at rest; practices aligned with the NIST Cybersecurity Framework (Student Privacy Compass) | Contract must say how data is returned or destroyed at the end | Contractor to school within 7 calendar days of discovery |
Illinois SOPPA | Schools, ISBE and online operators | Reasonable security; written agreement before any data is shared | Parents can ask the school to delete; operators delete on the school's request | Operator to school within 30 calendar days; school to parents within 30 days (Eduverse summary) |
California SOPIPA | Operators of K-12 online services | Reasonable security procedures | Delete on the school's or district's request | Under California's general breach law |
New York is also moving its baseline from NIST CSF 1.1 to CSF 2.0; the Regents' proposed amendment gave schools until September 1, 2026 to align their policies (NYSED). More than 40 states have some form of student-privacy statute, so check your own state's supplement to the privacy agreement.
None of these laws carves out backups. A copy kept for recovery is held to the same standard as the live record.
Backups are copies, and copies are covered
The privacy agreement most districts now sign says so in plain words. The Student Data Privacy Consortium's National Data Privacy Agreement (NDPA, now version 2.x) states that all copies of student data a provider processes are subject to the agreement in the same way as the original (NDPA v2.2 standard text). By 2024 its registry already held more than 130,000 signed agreements across over 12,000 districts (WSIPC), so if you buy ed-tech in the US you have probably signed one.
Read with backups in mind, the NDPA's standard clauses mean:
Deletion reaches the backup. On written request, the provider must dispose of or hand back student data within 60 days, and again within 60 days of the agreement ending. A backup that survives that window with readable student records is a copy that should not exist.
The backup host is a subprocessor. Any third party that stores student data, including a storage or backup provider, needs an agreement at least as strict as the NDPA and must not sell the data.
Where the backup lives is disclosed. Data stored outside the United States has to be listed by country.
Breaches are reported in 72 hours. The provider tells the district within 72 hours of confirming a breach, and that clock includes the backup bucket.
A recognized security framework applies. The provider picks at least one, such as NIST CSF, ISO 27001 or the CIS Controls, and runs a security audit or assessment at least once a year.
The same logic applies when the district is the one running backups. Your own copies of the SIS, the file server and staff mailboxes are covered by your policies and your state law. The difference is that nobody sends you a 60-day deletion request; you have to schedule it yourself.
Why client-side encryption matters when backups leave the building
If the backup is encrypted on your server before it is uploaded, and only you hold the key, then whoever stores it holds unreadable data. That one property answers most of the questions the laws above raise.
Compare the two kinds of encryption you will see on a vendor's security page:
Server-side ("encrypted at rest" by the storage provider) | Client-side (encrypted before upload, key stays with you) | |
|---|---|---|
Stolen disk at the data center | Protected | Protected |
Leaked storage access key or hijacked cloud admin account | Data readable | Ciphertext only |
Misconfigured or public bucket | Data readable | Ciphertext only |
Provider staff or a compromised provider | Data readable | Ciphertext only |
Legal demand served on the storage provider | Provider can hand over readable data | Provider can only hand over ciphertext |
Who can read your students' records | You and the provider | You |
What that buys a school:
It meets the explicit rule. New York requires encryption at rest for student data. Client-side encryption meets it for every copy, wherever the copy ends up.
It changes a breach into an incident. Most state breach-notification laws exempt encrypted data when the key was not also taken. A leaked bucket of ciphertext is still worth investigating, but it is a very different letter to parents.
It keeps the storage host out of scope for reading. The provider still counts as a subprocessor on paper, but it cannot see, mine or disclose the records. That is the strongest version of "direct control" under FERPA's school-official rule.
It makes deletion provable. Destroying the key for an archive renders every copy of it unreadable, including the ones in the provider's own redundancy. More on that below.
The cost is key custody. Lose the passphrase and you lose the backup, so treat it like the master key it is: keep an escrow copy offline, make sure at least two named people can reach it, never store it next to the backup, and rotate it when someone who knew it leaves. Encryption in transit (TLS) still matters too, but it protects the trip, not the copy at the destination.
Data minimization for departed students
Keep the permanent record your state requires, delete everything else on a schedule, and make sure the backups follow the schedule instead of quietly outliving it.
Two rules pull in opposite directions here. Your state's records-retention schedule sets the floor: transcripts and enrollment history are often kept for decades. Privacy law and the NDPA set the ceiling: working data such as app accounts, LMS submissions, chat logs, device telemetry and photos should go once it no longer serves a school purpose. A workable routine:
Split the permanent record from working data. Keep the permanent record in one system of record, usually the SIS. It does not also need to live in a dozen vendor apps.
Trigger deletion at exit. When a student graduates or withdraws, deprovision their accounts and send vendors a disposition request (under the NDPA that is Exhibit D). Students can be offered an export of their own work first; the NDPA allows that.
Let backups age out on purpose. If your longest backup retention is 13 months, deleted working data is gone from backups 13 months after it was deleted from production. Write that window into your retention policy, so "deleted" has a date you can state.
Split long-term archives by school year, each with its own key. When a year's retention ends, destroying that key retires the whole archive, including any copies you forgot about.
Don't resurrect deleted students. After restoring a system from backup, re-apply the deletions processed since the backup was taken. Keep a log of deleted student IDs and dates, not the data itself, so you can.
Pause for holds. A litigation hold or an open FERPA request to inspect a record stops deletion for that record until it is resolved.
Keep proof. Record what was deleted and when, and file each vendor's written confirmation of disposition.
What to ask a vendor during the privacy-agreement review
The NDPA, or your state's version of it, covers the legal terms. These questions check whether the vendor's systems can actually keep them, especially the parts nobody demos: backups, replicas and deletion. Ask for answers in writing and keep them with the signed agreement.
Scope: what exists, and where
Which student data elements do you collect for the products we use? Is anything listed only as "other"?
Besides production, where else does our data live: backups, replicas, logs, analytics, support tickets, test environments?
In which countries is our data stored, including backups and disaster-recovery copies?
Encryption and keys
Is our data encrypted at rest by you, or only by your hosting or storage provider?
Are backups encrypted before they leave your systems, and who holds those keys?
Which of your staff can read our student records in plain text, and is that access logged and reviewed?
(New York) Do you encrypt student data in motion and at rest to the Education Law 2-d standard?
Subprocessors
Who are your subprocessors, including backup and storage providers, and how do you tell us when the list changes?
Can your backup or storage provider read our data, or only store it?
Retention and deletion
What is your standard retention and destruction schedule? Please send it.
After we request deletion, how many days until the data is gone from production, and how many until it is gone from backups?
Can you delete a single student's data when they leave, or only the whole district's at contract end?
What do you keep as "de-identified" data after deletion, and which de-identification standard do you follow?
Will you confirm disposition in writing?
(Services used by under-13s) Where is your published COPPA data retention policy?
Security program and incidents
Which security framework do you follow, when was your last audit or assessment, and can we see a summary?
Do you have a written information security program with a named coordinator?
Does your breach notice cover backup storage, and does it meet our deadlines (72 hours under the NDPA, 7 days in New York, 30 days in Illinois)?
When did you last restore a customer's data from backup, and how often do you test restores?
Exit
How do we export all of our data when the contract ends, and in what format?
Who is your security contact, and how do we reach them outside business hours?
A vendor that answers "our cloud provider encrypts everything" to the encryption questions has told you about server-side encryption only. A vendor that cannot give a number of days for deletion from backups has probably never had to work it out.
How Duplicati fits
Duplicati was built around the property this article keeps coming back to: data is encrypted on your machine before it goes anywhere, with a key you hold.
Client-side AES-256 encryption for every backup, whether it goes to your own storage, a public cloud bucket or Duplicati Storage. The storage side only ever holds ciphertext.
You choose where backups live, so you can keep them in the region or on the hardware your state and your agreements require.
Retention you set per backup, so working data ages out of backups on a schedule you can write into policy, and separate backup jobs (and keys) per school year when you want to retire an archive by destroying its key.
A management console that doesn't see student data. File paths are redacted before reports reach the Duplicati Console, and agents can be switched to reduced reporting that sends no free text at all.
Google Workspace and Microsoft 365 backup, including the student and staff mailboxes and drives that are hardest to account for when someone leaves.
Whichever tool you use, the test is the same: could you show an auditor, a parent or a superintendent where every copy of a student's data is, who can read it, and the date it will be gone?
This article is a general overview for IT staff, not legal advice. Student-privacy laws vary by state and change often; check your state's requirements and your signed agreements with your district's counsel.



