How student and school data are handled in educational use

Purpose of this page

This page is intended to address student and school data more directly than the general Privacy Policy. It focuses on the information handled when the platform is used by schools, districts, educators, and students in educational implementations.

Student data categories

In educational use, student-related information may include student identifiers provided by the district or school, grade level, roster associations, launch participation, assessment session information, responses, completion state, DLL placement outputs, confidence signals, strengths and growth-area profiles, and related reporting summaries or implementation records.

How student data is used

Student data is used to deliver the DLS Adaptive Assessment experience, support session continuity, produce DLL placements and reporting outputs, support authorized educational review by teachers and district or school staff, maintain platform security, and provide implementation and support services connected to the educational deployment.

No sale of student data

As a product principle, student assessment and reporting data should be used to provide the educational service itself and not sold as a standalone data asset. Final contractual language should still be aligned with institutional agreements, district procurement requirements, and legal review.

FERPA, COPPA, and school governance

Depending on the deployment, student data handled through the platform may be subject to FERPA, COPPA, state student privacy laws, or district-specific requirements. In those contexts, the relevant district, school, or educational authority may remain responsible for determining the lawful basis for use, providing required notices or consents, and defining the governing contractual terms for student data handling.

Who can access student data

Access to student-related information should be role-based and limited to authorized users. Not every user should expect access to the same learner details, reports, or operational views. District, school, teacher, support, and technical access may differ based on role, scope, and contractual or institutional requirements.

Beacon and student data

Chart-Ed may offer assistant or support tooling to help with district, school, and class planning questions. Those Beacon or assistant experiences are not intended for student-level data entry or learner-by-learner case review.

Users should not submit student names, student IDs, session IDs, learner-level results, roster files, or access credentials into Beacon prompts. Student data should continue to be handled through the core educational workflows and role-based reporting tools that are designed for that purpose.

Deletion, return, and requests

Requests involving student records, student privacy, deletion, data return, or related educational information may need to be handled through the relevant district or school, or according to a district agreement or data processing agreement. General questions may be sent to [email protected].

Important draft note

This page is a public-facing draft and not a substitute for a final district-ready student data privacy commitment, DPA, or institutional contract. It should be reviewed with counsel and aligned to the final district contracting package before launch.