Between
Early Signal Project (“ESP”)
and
[School District or School Name] (“District”)

Effective Date: [Month Day, Year]
Review Date: [Month Day, Year]

---

1. Purpose

This MOU establishes a collaborative partnership whereby ESP will develop and pilot a data-driven student-support platform. The goal is to flag at-risk students, guide targeted STEM outreach, monitor socio-emotional well-being, and deliver adaptive mini-quizzes—all while fully adhering to student-privacy laws.

2. Parties & Authorized Representatives

• ESP Project Lead: William Aubrey, william@earlysignalproject.org
• District Liaison: [Counselor/IT Lead Name], [Email], [Phone]

3. Scope of Work

ESP will:

1. Ingest de-identified academic (grades, attendance, behavior) and sentiment-survey data.
2. Build risk-prediction models and dashboards for counselors/teachers.
3. Develop an adaptive formative-assessment module.
4. Map under-served zones for STEM workshops.
5. Provide weekly reports and a 16-week pilot evaluation.

The District will:

• Provide secure, scheduled exports of required data fields.
• Review and sign off on all data-use and privacy documents.
• Offer educator time for feedback sessions and pilot coordination.

4. Data Use, Privacy & Security

1. Data Types & Classification
   • PII: names, student IDs, DOB → never stored in analytic tables.
   • Protected Academic Records: grades, attendance, discipline logs → anonymized.
   • Survey Responses: free text & Likert scale → stored under random IDs.
2. Anonymization
   • All raw files are stripped of names and IDs; a one-way hash generates a new “StudentKey.”
   • Demographics (e.g., ZIP) truncated to 3-digit codes.
3. Storage & Access Controls
   • Data at rest is AES-256 encrypted; in transit via TLS 1.2+.
   • Role-based access:
     • Admins (ESP & IT): full read/write on warehouse
     • Teachers/Counselors: view-only dashboards
   • MFA required for all accounts.
4. Compliance
   • ESP and District affirm compliance with FERPA, state student-privacy statutes, and district policies.
   • Any data breach must be reported to District IT within 24 hours.

5. Data Retention & Destruction

• Raw Files (unencrypted PII): retained ≤ 6 months, then securely wiped (NIST 800-88 standard).
• Anonymized Data: retained ≤ 2 years for longitudinal analysis.
• Backups: rotated every 90 days and destroyed after 1 year.

6. Term, Renewal & Termination

• Term: 16 weeks from Effective Date.
• Renewal: by written agreement 30 days before term end.
• Termination: Either party may terminate with 14 days’ written notice. Upon termination, ESP will return or destroy all District data per Section 5.

7. Confidentiality

Each party agrees that all shared data, models, algorithms, and source code are Confidential Information. No party shall disclose Confidential Information without prior written consent, except as required by law.

8. Amendments

This MOU may be amended only by mutual written consent of authorized representatives.

---

For Student Success Insight Network:	For [School District/School Name]:
Name: ____________________________	Name: ____________________________
Title: ____________________________	Title: ____________________________
Date: ____________________________	Date: ____________________________

---