This Student Data Agreement (the "Agreement") is between ProctoredAI, Inc., a Delaware corporation ("ProctoredAI") and the school, district or other educational institution named in the signed copy (the "School"). Where an IT service provider enrolls the School's devices, that provider (the "Provider") also signs and is bound by the sections that name it. The Agreement takes effect on the date of the last signature (the "Effective Date"). A School signs a copy of this version and sends it to [email protected]; ProctoredAI then records it in the console, and only then can the School's Students group hold devices.
1. Purpose and Definitions
1.1 Purpose. The School wants to use the ProctoredAI service on devices used by its students. This Agreement sets the terms on which ProctoredAI handles Student Data, and it is the separate written agreement that section 1.7(h) of the Terms of Use and section 2.4(g) of the Partner Agreement refer to.
1.2 Definitions. Capitalized terms not defined here have the meaning given in the Terms of Use or the Data Processing Addendum at ProctoredAI.com/dpa (the "DPA").
- "Student" means a person enrolled at the School, whatever their age.
- "Student Device" means a device the School owns or manages and assigns to, or makes available for use by, Students.
- "Student Data" means Client Data that is linked or reasonably linkable to a Student or to a Student's parent or guardian, including data from a Student Device and any Student information that appears in data from a staff device. It includes personally identifiable information from education records as the Family Educational Rights and Privacy Act ("FERPA") defines those terms, and personal information collected online from a child under 13 as the Children's Online Privacy Protection Act ("COPPA") defines it.
- "De-Identified Data" means data from which all direct and indirect identifiers have been removed so that it cannot reasonably be linked to a Student, a device or the School.
- "Student Privacy Laws" means FERPA, COPPA, the Protection of Pupil Rights Amendment, and the state student privacy laws that apply to the School.
- "Service" means the ProctoredAI console, the Agent and the ProctoredAI browser extension.
2. Roles and Permitted Use
2.1 The School Owns and Controls Student Data. As between the parties, Student Data belongs to the School and stays under the School's direct control. ProctoredAI gets no right or license to it except the limited right to process it under this Agreement.
2.2 School Official. The School designates ProctoredAI as a school official with a legitimate educational interest under 34 C.F.R. § 99.31(a)(1)(i)(B). ProctoredAI performs an institutional service the School would otherwise use its own staff for, is under the School's direct control for the use and maintenance of education records, and will use and redisclose them only as this Agreement and FERPA allow.
2.3 Children Under 13. Where Student Devices are used by children under 13, the School authorizes the collection of their personal information for the use and benefit of the School and for no commercial purpose, and gives any consent COPPA requires on behalf of parents, to the extent the law lets a school do so.
2.4 Permitted Purposes. ProctoredAI will process Student Data only to (a) provide the Service to the School as the School's settings direct; (b) keep the Service secure and working, including finding and fixing defects; (c) give the School support it asks for; and (d) comply with law. These are the "Permitted Purposes".
2.5 The Provider. Where a Provider enrolls the School's devices, the Provider acts for the School, is bound by sections 3, 4, 5.1, 6 and 7 for the Student Data it can reach in the console, and will give access only to its personnel who need it to serve the School.
3. What ProctoredAI Will Not Do
ProctoredAI will not:
- sell or rent Student Data, or share it for payment or other value;
- use Student Data to advertise or market to Students or their families, or to target advertising to anyone;
- build a profile of a Student except as needed to show the School the activity on its own devices;
- use Student Data to train, tune or test any artificial intelligence or machine learning model;
- use Student Data to improve the Service or to build other products. Section 3.3 of the DPA (Improving the Service, including catalog improvement) does not apply to Student Data, and the Service keeps every school out of catalog improvement;
- combine Student Data with data from other customers or other sources, except as needed for a Permitted Purpose;
- disclose Student Data to anyone other than the School, the Provider, the Subprocessors in Exhibit B, or as section 5.5 allows;
- try to re-identify De-Identified Data, or give it to anyone who has not agreed in writing not to; or
- collect biometric data, precise location, photos, audio or video of Students, or the contents of a Student's screen.
ProctoredAI may use De-Identified Data only to compute aggregate statistics about the Service.
4. Student Devices: What Is Collected and Required Settings
4.1 Data Elements. Exhibit A lists the Student Data the Service collects. ProctoredAI will not collect other categories of Student Data without the School's written agreement.
4.2 Scope of Inspection. On a Student Device the Service inspects traffic to the AI applications in its catalog and to any other channel the School turns on. Apart from the discovery data in Exhibit A, it does not read or record a Student's other browsing, and it does not judge or grade a Student's written work.
4.3 Required Settings. For every organization, group or device that holds Student Devices, the School, or the Provider for it, will:
- keep Prompt Capture at None or Redacted, never Full (the Service refuses Full for every school);
- set a retention period of 365 days or less for events;
- give console access only to School and Provider personnel who need it, each with their own account and two-factor authentication (the Service requires it for password sign-in; for single sign-on, the School's or Provider's identity provider must require it); and
- treat any exact-match list that holds Student identifiers as confidential, since short values can be recovered from the hashes devices hold.
4.4 Names on Student Devices. A device counts as a Student Device in the Service when it is in the School's Students group, and the Service keeps treating it as one, for names, until it is removed from the Service. From then on the Service stores the signed-in user of that device as "Student", and, unless the School chooses to show device names, stores the device's name as a stand-in such as "Student Device 0042"; the events, alerts and exception requests the Service already held about that device are rewritten the same way, and the School's data export shows the stand-ins. The name the device reports is kept so the School's group rules and device-management matching keep working. It is not shown in device lists, alerts, reports or exports; a School or Provider administrator can look it up for one device at a time to support it, and each lookup is recorded in the audit log. Audit log entries made before a device became a Student Device are kept as they were, because the audit log cannot be changed, and are shown with the stand-ins in the School's export. Alerts and events already sent by email, chat, ticketing system or SIEM before a device joined the Students group cannot be recalled.
4.5 Features Off on Student Devices. Local AI (local model inventory, model server checks and Network Check) and MCP Enforcement do not run on Student Devices, and a Student Device deletes any Local AI report it kept when it joins the Students group.
4.6 Integrations. A connection the School or Provider turns on, such as a ticketing system, chat tool or SIEM, sends data to a service the School or Provider chose. That service is not ProctoredAI's Subprocessor, and the School is responsible for its own agreement with it.
4.7 AI Applications Are Third Parties. The Service controls and records the use of AI applications. It does not make those applications' providers parties to this Agreement, and whether an AI application may receive Student Data is the School's decision.
5. Security, Subprocessors and Incidents
5.1 Security. ProctoredAI will protect Student Data with administrative, technical and physical safeguards that meet or exceed reasonable industry practice, including the measures in Annex II of the DPA.
5.2 Personnel. ProctoredAI will give access to Student Data only to personnel who need it for a Permitted Purpose and who are bound to confidentiality.
5.3 Subprocessors. Exhibit B lists the Subprocessors that may process Student Data. Each is bound by written terms with data protection obligations consistent with this Agreement, and ProctoredAI is responsible for their performance. ProctoredAI will give the School, or the Provider for it, at least 30 days' notice before a new Subprocessor processes Student Data, and the School may end this Agreement without penalty if it objects.
5.4 Location. ProctoredAI stores Student Data in the United States. Cloudflare's network, which terminates connections to the console, operates worldwide.
5.5 Legal Demands. If a court, agency or other third party demands Student Data, ProctoredAI will refer the request to the School, tell the School promptly unless the law forbids it, and disclose only what the law requires.
5.6 Security Incidents. ProctoredAI will notify the School, and the Provider if there is one, without undue delay and in any event within 48 hours after it becomes aware of unauthorized access to, or disclosure or loss of, Student Data. The notice will say what happened, the types of data and the number of Students involved as far as known, what ProctoredAI has done, and whom to contact. ProctoredAI will investigate, contain the incident, keep the School updated, and cooperate with the School's own notices to families and regulators. ProctoredAI will pay the reasonable cost of notices the law requires where the incident was caused by its breach of this Agreement.
5.7 Review. Once a year on request, ProctoredAI will answer the School's reasonable security questionnaire and share a summary of its most recent independent security assessment, if one exists.
6. Access, Correction, Retention and Deletion
6.1 Requests From Parents and Students. If a parent, guardian or Student asks ProctoredAI to see, correct or delete Student Data, ProctoredAI will refer them to the School and will not answer the request itself. ProctoredAI will help the School respond within 10 business days of the School's request, including by exporting or deleting the data held under a named Student Device.
6.2 Retention. Events, resolved alerts and exception records are deleted automatically at the end of the retention period the School sets. Device and user inventory, monthly report snapshots and AI Use Policy acknowledgment records are kept while the School's organization exists in the Service. Audit log entries are kept for 2 years.
6.3 Deletion on Request. The School may at any time direct ProctoredAI in writing to delete some or all Student Data. ProctoredAI will do so within 30 days.
6.4 Deletion at the End. When this Agreement ends, the School's Students group closes and its devices leave it at once. Until the Agent is removed from them, the Service keeps storing their names and signed-in user as section 4.4 describes and sends them no Local AI or MCP Enforcement settings. The School may export what they sent for 30 days. ProctoredAI then deletes the events and alerts from those devices automatically, and anything a device sends later is deleted 30 days after it arrives until the Agent is removed, and any other Student Data on the School's written request or when the School's organization is deleted. Deleted data leaves backups within a further 30 days. ProctoredAI will confirm deletion in writing on request. The School will remove the Agent from Student Devices when this Agreement ends.
6.5 What May Be Kept. ProctoredAI may keep Student Data only where a law requires it, and may keep audit log entries for up to 2 years. Sections 6.3 and 6.4 are subject to this section. It will tell the School what it kept and why, and will protect it under this Agreement for as long as it holds it.
7. What the School Is Responsible For
7.1 Authority. The School confirms that it has the authority to enter this Agreement and to have the Service installed on Student Devices, and that the devices are owned or managed by the School. The School will not install the Service on a device a Student or family owns, and will scope force-installation so it does not reach personal devices.
7.2 Notice and Consent. The School will give Students and parents any notice, and get any consent, that Student Privacy Laws, monitoring laws or its own policies require before the Service runs on Student Devices. This includes naming ProctoredAI in its annual FERPA notice criteria for school officials and in any list of online services it publishes, where the law requires one.
7.3 Settings and Rules. The School decides which AI applications Students may use, which rules apply and what is recorded, keeps the settings in section 4.3, and puts its Student Devices in its Students group.
7.4 Not a Safety or Filtering Service. The Service is not a web filter, a classroom monitoring tool, an exam proctoring tool or a student safety alerting service, and it does not satisfy the School's duties under the Children's Internet Protection Act. The School will not rely on it to detect self-harm, threats or other emergencies.
7.5 Accurate Lists. Where the School uploads a list of Student identifiers for exact-match detection, it will upload only what detection needs and remove the list when it stops using it.
8. Term and General Terms
8.1 Term. This Agreement runs from the Effective Date until the Service is removed from every Student Device and all Student Data has been deleted under section 6.4. Either the School or ProctoredAI may end it on 30 days' written notice, and the School may end it at once if ProctoredAI materially breaches it. Sections 3, 5 and 6 keep applying for as long as ProctoredAI holds any Student Data.
8.2 Relationship to Other Documents. The Terms of Use, the DPA and, where a Provider is involved, the Partner Agreement keep applying; for a School that buys directly, the Customer Terms do too. Where they conflict with this Agreement about Student Data, this Agreement controls. Section 1.8 of the Terms of Use on health information is not changed.
8.3 Changes. ProctoredAI may change the Terms of Use and the DPA as those documents allow, but no change reduces the protection this Agreement gives Student Data. This Agreement changes only in a writing both the School and ProctoredAI sign. When ProctoredAI publishes a new version, the version the School signed stays in force until the School signs the new one or the signed version is retired with at least 30 days' notice to the School.
8.4 Liability. The limits of liability in the Terms of Use, the Customer Terms where the School buys directly from ProctoredAI, and, where a Provider is involved, the Partner Agreement apply to this Agreement. They do not limit liability the law does not allow to be limited.
8.5 Governing Law. North Carolina law and the courts of Cabarrus County, North Carolina, as in the Terms of Use, except that for a public school or district, the law of the School's state and the courts located there.
8.6 State Terms. Exhibit C holds any terms the School's state requires. Where Exhibit C is stricter than the body of this Agreement, Exhibit C controls.
8.7 Public Records. The School may disclose this Agreement where a public records or student privacy law requires it.
8.8 Notices. Notices to ProctoredAI go to [email protected]. Notices to the School and the Provider go to the email addresses in the signed copy.
8.9 Successors. If ProctoredAI is acquired or merges, its successor is bound by this Agreement for all Student Data it receives, and ProctoredAI will tell the School.
Signatures
| School | Provider (if any) | ProctoredAI | |
|---|---|---|---|
| Organization | ProctoredAI, Inc., a Delaware corporation | ||
| Signed by | |||
| Name and title | |||
| Notice email | [email protected] | ||
| Date |
Exhibit A. Student Data Elements
| Category | What it holds | Notes |
|---|---|---|
| Account identity | The email of the account signed in to an AI application, and whether that account is a school or personal one. The device's signed-in user is stored as "Student" | A Student's school email is usually their name |
| Device | The device name, stored as a stand-in such as "Student Device 0042" unless the School shows device names (the reported name is kept for group rules and device-management matching, and an administrator can look it up for one device at a time, audited); operating system, Agent or extension version, hardware identifier, IP address at check-in, the tags and groups the School assigns, and on laptops which well-known security and device-management tools are present and running | On a managed Chromebook the reported name is usually its asset tag or serial number |
| AI use events | The AI application and host, the channel, what the policy did, the rule, the types and counts of sensitive data found, the AI model named where shown, clipboard findings when text is pasted into an AI application, browser control events (browser name and action), AI agent tool-call metadata (server, method and tool name), and the time | No matched values |
| Prompt excerpts | None when Prompt Capture is None. When Redacted, a short excerpt with each finding replaced by its detector name; the surrounding text can include names | Full is not allowed for a school |
| File metadata | Name, size, type and fingerprint of a file sent to an AI application | Never file contents |
| Warnings and exceptions | The reason a user typed when continuing past a warning or asking for an exception, and the decision | Free text a Student writes |
| AI application discovery | Host names that look like AI products and, on Chromebooks, the page title of such a page (at most once per host per week), installed AI applications, matching browser extensions, and the MCP servers configured in AI tools on the device | Never other browsing or other extensions |
| AI Use Policy acceptance | Account name, device, policy version and time, and the typed name where the School asks for one | Only if the School turns it on for Students |
| Usage counts | Hourly counts per AI application and model | |
| Exact-match lists | A list the School uploads, such as student numbers, stored as hashes | Short values can be recovered from hashes |
| Audit log | Actions School and Provider staff take in the console | Kept 2 years |
| Other features the School turns on | If the School turns on another feature for Student Devices, such as endpoint DLP channels, Email DLP, or an identity or MDM connection, the data that feature collects as described in Annex I of the Data Processing Addendum | Turning it on is the School's written agreement under section 4.1 |
Not collected from Student Devices: grades, attendance, discipline or health records as such, biometric data, precise location, photos, audio, video, keystrokes (text is checked only when pasted into or sent to an AI application), browsing history outside AI applications and the channels the School turns on, and anything from Local AI or MCP Enforcement (section 4.5). Features the School does not turn on for Student Devices, such as endpoint DLP, identity or MDM connections and Private Access, collect nothing from them.
Exhibit B. Subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Google LLC (Google Cloud) | Hosting the console, database and backups | United States |
| Cloudflare, Inc. | TLS termination and network delivery | United States company, worldwide network |
| Google LLC (Google Workspace) | Sending email, such as alerts, invitations and notices | United States |
| Amazon Web Services, Inc. | Only if the School turns on Email DLP: the School's outbound email passes through the Mail Gate and is kept only until it is handed back | United States |
Exhibit C. State Terms
None, unless the School and ProctoredAI attach and sign state terms with this Agreement. A School in a state with its own required terms, such as California (SOPIPA and Education Code 49073.1), New York (Education Law 2-d and the Parents' Bill of Rights) or Illinois (SOPPA), may ask for them before signing at [email protected]. ProctoredAI will also review the Student Data Privacy Consortium's National Data Privacy Agreement (NDPA), or a state version of it, if the School asks to sign that instead.
Questions about this Agreement: [email protected].