How Chart-Ed handles platform, student, district, and store data

Overview and scope

This Privacy Policy applies to the DLS Adaptive Assessment site and related Chart-Ed workflows, including public pages, district onboarding, rollout configuration, teacher and staff access, student assessment delivery, reporting, support interactions, and commerce or store experiences made available through this site or connected services.

This policy is intended to explain the main categories of information we handle, how that information is used, when it may be shared with service providers or authorized institutional partners, and how school or district data contexts may change the applicable rules. It is not a substitute for district contracts, school policies, or other binding education data terms that may govern a particular implementation.

Who uses the platform

Different parts of the platform serve different audiences. Depending on the workflow, we may handle information relating to district administrators, school leaders, teachers and staff, students, parents or guardians, public site visitors, support requestors, and customers who make purchases through Chart-Ed commerce or store experiences.

Information we collect

The information involved depends on the part of the service being used. It may include account and contact information such as names, email addresses, district or school affiliation, role, login state, and support communications. In district and school workflows, it may also include onboarding details, building and classroom configuration, roster and launch information, student identifiers supplied by the district or school, access codes, and administrative records needed to coordinate rollout and reporting.

In assessment and reporting contexts, information may include session identifiers, assessment responses, progress through the adaptive experience, provisional and final DLL placement outputs, confidence or evidence signals, strengths and growth-area profiles, reporting summaries, and related operational metadata such as timestamps, status, and role-based access context.

In commerce contexts, information may include purchaser name, email address, billing or shipping details, order history, fulfillment information, and payment-related transaction records provided through our payment or commerce providers. We may also collect browser, device, and session information needed to keep users signed in, secure the platform, and maintain basic continuity across workflows.

How we use information

We use information to operate the platform, authenticate users, deliver assessment and reporting features, support district onboarding and rollout management, provide account and customer support, fulfill commerce transactions, maintain security, improve reliability, investigate misuse, and communicate about the service.

In educational implementations, assessment and reporting data are used to deliver the DLS Adaptive Assessment experience and related reporting outputs. Those uses may include session delivery, placement calculation, report generation, implementation review, school or class comparison, and authorized support for district and school users. Student assessment data is not intended to be used for advertising to students or to create unrelated commercial profiles about them.

Some support or assistant interactions may also be used to help users navigate rollout, reporting, or implementation questions. Those assistant workflows are intended for district, school, and class planning or support questions, not for student-level case review.

Educational records, student data, FERPA, and COPPA

When the platform is used by a school, district, or other educational institution, some information handled through the service may be considered student data, student records, or education records under applicable law or contract. That can include roster information, student identifiers, assessment responses, placement results, reporting outputs, and related implementation records.

In those contexts, Chart-Ed generally expects the relevant school, district, or educational authority to determine the lawful basis for using the service, to provide any required notices or consents, and to define the governing contractual terms for student data handling. Where FERPA, COPPA, state student privacy laws, or similar requirements apply, those obligations may be shaped by the institutional relationship, the student age range, and the specific deployment model.

As a product principle, student assessment data should be used to provide the educational service itself and not sold as a standalone data asset. This draft policy should still be reviewed and aligned with final contracting terms and legal guidance before broad production launch.

Who we share information with

We may share information with service providers and subprocessors that support hosting, infrastructure, authentication, analytics, security monitoring, email or support delivery, payment processing, order fulfillment, and other operational needs. We may also share information with the relevant district, school, authorized staff, or other institutional users when the platform is being used in an educational implementation.

Where Chart-Ed provides assistant or support tooling through third-party service providers, users should not submit student identifiers, learner-level results, roster data, access credentials, or similar sensitive records into those assistant prompts. Those tools are intended for higher-level operational and implementation questions unless and until Chart-Ed separately documents a narrower approved use case.

We may disclose information when reasonably necessary to comply with law, enforce our terms, protect the platform, investigate fraud or abuse, respond to lawful requests, or protect the rights, safety, or security of users, students, institutions, Chart-Ed, or others.

Cookies, browser storage, and similar technologies

We use cookies and similar browser-side storage to maintain secure sessions, remember simple preferences, preserve continuity during onboarding, launch, assessment, and reporting workflows, and support core platform functionality. Some of these technologies are necessary for the service to operate correctly. Clearing or disabling them may limit sign-in, launch, or reporting behavior.

Data ownership, control, and retention

Data ownership and control may vary by context. In school or district implementations, the relevant institution may control or direct certain categories of student, roster, reporting, or implementation data. In commerce or public-site contexts, Chart-Ed may act more directly as the service operator for the information involved. Retention periods may vary based on technical need, contractual commitments, legal obligations, audit requirements, or customer support needs.

Security

We use reasonable administrative, technical, and organizational measures intended to support secure handling of information in our systems. No system, transmission path, or device environment can be guaranteed to be fully secure, so users and institutions should also protect credentials, access codes, devices, and internal sharing practices.

Your choices and requests

Depending on the context, users may have the ability to manage certain browser settings, update account information, or submit privacy or data-related requests through Chart-Ed support channels. In educational implementations, requests involving student records, district data, or school-controlled information may need to be routed through the relevant institution or handled according to district contract terms and school policy.

For privacy or data-related questions, please see Data Requests or contact [email protected].

Policy updates

We may update this policy as the product, rollout model, reporting capabilities, commerce experiences, or legal requirements change. Material updates should be reflected here so the policy remains aligned with current service behavior.

Important draft note

This is a stronger product-specific draft than the prior cookie-style notice, but it should still be reviewed by qualified counsel, especially for FERPA, COPPA, state student privacy requirements, district contracting terms, and any commerce or payment disclosures that depend on final vendors and deployment choices.