Data privacy agreement

A data privacy agreement is the contract between a district and a vendor that governs what happens to student and family data: what is collected, what it may be used for, who else sees it, how long it is kept, and what happens to it when the relationship ends.

Last reviewed 2026-10-15

Clause by clause, with what a weak version looks like
ClauseStrong versionWeak version you will actually be sent
Data elementsAn itemised schedule of every field exchanged"Student directory and contact information as required"
Purpose limitationNamed purposes only; anything else needs written authorisation"To provide and improve the Services"
Sub-processorsNamed list, advance notice of changes, right to object"Vendor may engage subcontractors"
Breach notificationA fixed clock in hours or days, starting at discovery, with content requirements"Without undue delay"
Deletion on terminationStated window, stated exceptions, written confirmation"Data will be deleted in accordance with Vendor's retention policy"
ExportMachine-readable, on request, during the term and at exitSilence, or "available for an additional fee"
Change of controlDistrict may terminate on acquisition or material data-terms change"Assignable to a successor in interest"
OwnershipRecords remain the property and under the control of the district"Vendor owns aggregated and de-identified data"

Where the standard templates come from

Most US districts do not draft from scratch. The Student Data Privacy Consortium, a project of the Access 4 Learning Community, maintains the National Data Privacy Agreement, and many states run their own alliance with a state-specific version and a shared registry of signed agreements.

The NDPA's structure is worth knowing even if your state uses something else. There is a core agreement, and then exhibits: a description of the services, a schedule of the data elements exchanged, a set of definitions, a form for requesting deletion or inspection, and, the one that saves the most work, a general offer page, in which a vendor offers the same signed terms to any other district in the state. One district negotiates; every other district in the alliance countersigns.

That mechanism is the privacy-side equivalent of a piggyback contract, and it has the same prerequisite: someone has to have done the negotiation properly the first time, because everyone downstream inherits it.

The amendments vendors ask for

Districts see the same requested edits repeatedly. Each is defensible in isolation and each gives something away:

  • "Improve the Services" added to purpose limitation. Reads as harmless maintenance. Covers analytics, product research and, increasingly, model training.
  • "Aggregated and de-identified data" carved out of every restriction. Reasonable in principle; the question is who decides what counts as de-identified, and whether the standard is written down.
  • Breach notification softened from a fixed clock to "without undue delay", or the trigger moved from discovery to confirmation, which can add weeks.
  • Deletion made subject to the vendor's own retention policy, a document the vendor can change unilaterally.
  • Sub-processor list replaced with a URL that the vendor maintains, with no notice obligation.
  • Liability capped at fees paid, which for a $17,000 annual contract is not a deterrent to anything.
  • Assignment permitted to any successor, which is how a district ends up a customer of a company it did not evaluate.

None of these are dishonest requests. But a district signing without reading them has, in substance, agreed to terms it never discussed.

What Kastr can and cannot sign up to

Stating our own position, because a page about DPAs written by a vendor is worthless otherwise.

  • Kastr implements an operator-run scoped portable export with a manifest, checksums and explicit exclusions. Confirm record scope, handling time and any fees in the current written agreement with Ross; no universal self-service export is claimed.
  • Kastr's intended model is school-funded communication without family-facing subscriptions or marketing to families. Confirm the actual permitted uses and restrictions in the current written agreement and supplier terms with Ross.
  • A change-of-control or material-data-terms exit provision is proposed. Confirm the notice period, refund, export scope and other obligations in the current written agreement with Ross.
  • Record-specific retention schedules require school and owner agreement. The automated purge job that would enforce them is not built. No approved manual or automated enforcement is established by this source review.
  • We are not SOC 2 audited. We are independently operated. If your DPA requires a current Type II report as a condition of signature, we cannot meet it this year.

One question worth asking every vendor. "If your export feature breaks, does the contract still oblige you to produce our data?" A product feature can be deprecated in a release note. A clause cannot.

This entry describes what the rule says. Whether and how it applies to your district is a question for your own counsel, not for a vendor.

Questions people actually ask

What is the difference between a DPA and a master services agreement?

The MSA governs the commercial relationship: price, term, service levels, liability. The DPA governs the data: what may be collected, what it may be used for, who else touches it, and what happens at the end. They are often signed together and are frequently inconsistent with each other, which is worth checking before signature.

What is the NDPA and who maintains it?

The National Data Privacy Agreement is a standard template maintained by the Student Data Privacy Consortium, part of the Access 4 Learning Community. Many states run an alliance with a state-specific version and a shared registry, so a vendor's signed agreement can be adopted by other districts in the state.

How long should a vendor have to notify a district of a breach?

Fix a number rather than accepting a standard. Districts commonly require notification within 24 to 72 hours of discovery, with a defined content list. Several states set their own statutory windows for education data, which override whatever the contract says.

What happens to student data when a contract ends?

Whatever the agreement says, which is why the deletion and export clauses matter more than any feature comparison. Look for a stated deletion window, a stated list of exceptions, written confirmation of completion, and an export obligation that survives termination rather than expiring with your login.

Published pricing. Current capabilities included.

$3.50 per student per year under 5,000 students. No tiers or add-on modules. Normal messaging is included under a published fair-use allowance, with transparent cost recovery only above it.