Trust & Compliance
This is a demonstration prototype for Fairfax County Public Schools. The sections below describe how the platform is built to handle privacy, accessibility, security, and support — and draw a clear line between functionality that runs today and capabilities that are simulated for this demonstration.
What's real vs. demonstrated
| Real & working | Simulated for demo |
|---|---|
| Symbol library with keyword and phoneme search | SSO via SAML / OAuthFCPS identity provider |
| Board editor with templates and full cell customization | Schoology LTI 1.3 + Names & Role ProvisioningRoster sync |
| Custom image upload (with content-scan gating) | Clever rosteringDistrict SIS integration |
| PDF and transparent-PNG export | AWS GovCloud hostingFedRAMP-aligned region |
| Student activities (interactive schedule, choice, AAC practice) | SOC 2 Type II / TX-RAMPIndependent attestation |
| AI assists (board assembly, label translation) | Signed NDPA / data-privacy agreementExecuted contract |
| Role-based access control, library scopes, and audit logging | Production SLA + staffed help deskTicketing & on-call |
Our posture
Accessibility — WCAG 2.2 AA
Designed to meet WCAG 2.2 Level AA: semantic structure, keyboard operability, visible focus, sufficient contrast, and 44px minimum touch targets throughout the student player.
Student privacy — FERPA, COPPA, PPRA
Built to align with FERPA, COPPA, and PPRA. Student records are scoped to the assigning educator and the student, and are never exposed across schools or districts.
No targeted advertising
No advertising of any kind. Student or staff data is never sold, rented, or used to build advertising or marketing profiles.
AI is not used to train models
Content sent to AI assists is used only to fulfill the immediate request. It is not retained for, or used to train, any model.
Data export at closeout
At contract closeout the district receives a full export of its boards, uploads, and activity data in portable formats, followed by secure deletion on a defined schedule.
Support severity & response targets
| Severity | Description | Target response |
|---|---|---|
| Sev 1 | Service down or unusable for all users | 1 hour |
| Sev 2 | Major feature broken; no workaround | 4 hours |
| Sev 3 | Minor feature issue; workaround exists | 1 business day |
| Sev 4 | Cosmetic or enhancement request | 3 business days |
Targets reflect first response during the support window. Resolution times depend on severity and root cause.