Admit Protocol

Articles · schools

Admit Protocol and FERPA

How a school stays compliant with the Family Educational Rights and Privacy Act while accepting applications through a hosted service and families' AI agents. What the law reaches, what the service signs, and what it does.

Admit Protocol · November 17, 2026 · 5 min read

Schools ask this early, and they should. The short answer is that nothing in Admit Protocol prevents FERPA compliance, and the hosted service is set up the way every admissions and student-information vendor a school already uses is set up. The longer answer follows, question by question. It is not legal advice; have your attorney read the agreement before you sign it.

Does FERPA apply to applicants at all?

Strictly, FERPA covers the education records of students in attendance. An applicant who never enrolls is not a student under the statute, so applicant files sit outside it. The moment an applicant enrolls, the application becomes part of their education record. Admit Protocol does not rely on that gap. The service treats every application as if FERPA applied from the day it arrives, so there is nothing to argue about later.

How can a school share records with an outside service?

Under the school official exception, 34 CFR 99.31(a)(1)(i)(B). FERPA lets a school share education records with an outside party that performs a service the school would otherwise use its own employees for, is under the school's direct control for the use and maintenance of the records, uses them only for that purpose, and does not re-disclose them. Blackbaud, the Standard Application Online, Ravenna and Veracross all operate under it. So does Admit Protocol, through a written agreement each school signs before going live.

What does the agreement say?

That the data is the school's and the family's. That the service acts only on the school's instructions, uses the data for nothing but running the service, and passes it to no one. No training of AI models on it, no combining or comparing across schools, no benchmarking, no advertising. That the service deletes on the school's published schedule or within fourteen days of a request, exports everything on request and at the end of the relationship, and notifies the school of any breach within 72 hours. That subprocessors are named and cannot be added without notice. The agreement is the same text for every school, and Verde Valley School, the first school on the service, signs it too.

Who can see an application?

Staff the school has named, signed in with the school's own Google accounts, and only for their own school. The service's operators, who are named in the agreement, can open data to run or fix the service, and their access is logged the same way. Each school's data is separated from every other school's by row-level security in the database.

Is access recorded?

Yes. Every time a staff member opens an application, downloads a document or exports a record, the service writes who, what and when to that application's timeline, where the school's staff can see it. This is what "under the school's direct control" looks like in practice: the school can see exactly what has happened to its records.

How does a parent inspect or correct a record?

FERPA gives parents, and students eighteen or older, the right to inspect and review records within 45 days of asking, and to ask for corrections. The school answers; the service makes it answerable. Staff can export the complete record for any application as a single file from the desk: the fields, every piece of writing with its attestation, every document as received, and the timeline. When a family corrects something, the correction is recorded beside the original; what was sent is not silently rewritten.

Where is the data, and who else touches it?

In the United States, with Supabase for the database and Vercel for hosting and private file storage, both under data-processing agreements that forbid them from using it for anything but running the service. Email notices go through Google Workspace, and they carry a first name, a grade and a link, never application content. No other company sees application data. If that ever changes, the list in the agreement and on the privacy page changes first.

How long is it kept?

Each school publishes its retention rule. The default: applications from students who do not enroll are deleted two years after the admissions cycle closes, keeping only an anonymous count by grade and outcome for the school's applicant-pool profile. Applications from students who enroll become part of the student's record in the school's own system and are deleted from the service one year after enrollment. Codes expire in minutes, agent tokens in about three months, server logs in ninety days. A legal hold pauses any deletion.

Does the family's AI agent create a FERPA problem?

It is the strongest part of the story. The family's folder never leaves their computer. The family's own agent decides what to send, and a parent approves it by code before anything moves. The school collects only what the parent chose to give, and can show exactly that. No portal has a better consent record. The agent never sees anything from the school's side except the status of the family's own application.

What about the AI assistant the family uses?

The family's assistant, such as Claude or ChatGPT, processes the family's own documents on the family's behalf, under the family's own agreement with that provider, the same as when a parent asks it to summarize a report card. The school is not party to that and holds none of it. What reaches the school is what the parent approved, and it travels over an encrypted connection to the school's own service.

Is Admit Protocol "FERPA certified"?

No, and neither is anyone else; no such certification exists. A vendor who says "FERPA certified" means it signed the school's agreement. Admit Protocol operates under a signed school-official agreement, publishes its privacy policy and retention schedule, logs access, and names its subprocessors. That is what compliance consists of.

What should a school do before going live?

Read the agreement with your attorney. Name your staff and your contact for breach notice. Confirm or replace the default retention rule. Add a sentence to your admissions page telling families the agent path exists. That is the list. The service's own remaining items, before the first school outside the pilot, are a written breach-response procedure and an independent review of the security measures; both are listed in the agreement so you can hold us to them.