Vendor and district walkthrough
Example Learning — sample vendor
1. Verify vendor access
In production, the reviewer confirms that the person is authorized to represent the vendor. Email confirmation alone does not grant access.
- Request verification
- Confirm email
- Affiliation review
- Submit evidence
Evidence entry is locked until the simulated email confirmation and affiliation approval are complete.
2. Submit supporting evidence
An approved vendor can submit up to 10 public HTTPS links with a title and evidence type. The examples below use placeholder URLs; they are not verified documents.
3. District reviewer view
Pending review — demonstration only. Submission does not automatically change a rating. A reviewer checks the source, date, product scope and whether it supports a vendor statement, documented implementation or independent verification.
Example reviewer questions
- Is school data limited to school-authorized use, with restrictions on advertising, resale, unrelated profit, profiling and unrelated AI training?
- Are retention periods purpose-limited, including backups and subprocessors, with no unrelated reuse?
- Can parents/guardians request deletion through a clear, authorized process?
- Which FERPA, COPPA and state requirements apply to this product and district workflow?
- Is there current evidence for encryption, access controls, incident response and other safeguards?