One shareable guide to how WiseBoard uses AI, protects student information, keeps adults in the loop, supports accessibility, and helps a district implement responsibly.
This page is the buyer-facing index. Every answer is paired with the source artifact that should travel with a procurement response.
A public policy or product behavior supports this answer.
Share the linked document so the buyer has the underlying evidence.
Do not turn this into a promise until the named owner confirms it.
Approved talking points
Use the status label on each answer when preparing an RFP or security questionnaire.
WiseBoard uses district-provided information to provide the classroom, assessment, communication, and administrative services the district requests. Student data is not sold, used for advertising, or used to build commercial profiles.
Districts retain control of their records. Anonymous-code and student-ID roster modes are available when a district does not want names stored.
Read the Privacy Policy and FERPA statementThe current AI Usage Disclosure says WiseBoard uses OpenAI's GPT-4o family through API endpoints. Prompts pass through server-side data minimization, including pattern scrubbing and pseudonymization where applicable.
The published disclosure states that WiseBoard customer prompts and completions are not used to train external models, that zero-retention enterprise API terms are used for traffic that may contain student PII, and that an organization-wide AI off switch is available.
Open the AI Usage DisclosureRetention depends on the record type, so do not quote a single blanket number. The published materials describe account and service data as retained while active and for 30 days after deletion, with encrypted backups retained for 30 days.
The Student AI Safety page separately describes Pip transcripts as retained for the academic year and 90 days after a student leaves a class, and safety events as retained for 24 months. A district's executed DPA controls where it differs from a public policy.
Review retention in the Privacy PolicyAI output is a draft for an educator to review. WiseBoard's instructional action loop lets teachers approve, dismiss, or correct recommendations and does not autonomously grade, change student records, assign interventions, or message families.
Outcome checks show available descriptive measures only; the product does not claim that an action caused a student outcome. Teachers and districts remain responsible for decisions and local policy.
Read the instructional evidence packPip's Study Hall is opt-in per class and off by default. The published safety design includes age-tier content controls, district or school strictness floors, teacher controls, daily caps, distress detection, trusted-adult redirects, transcript visibility, and parent opt-out.
Pip is a study assistant, not a counselor, therapist, doctor, or substitute for an adult. Districts should decide whether Study Hall is enabled and how local student-support and family-communication policies apply.
Open the Student AI Safety guideWiseBoard describes itself as partially conformant with WCAG 2.2 Level AA and publishes a main-product VPAT, a Pip's Arcade companion VPAT, known limitations, and alternative paths for affected workflows.
Sales should share the VPAT and accessibility statement rather than promise that every surface is fully conformant. The published statement documents keyboard, screen-reader, voice-control, switch-control, and reduced-motion testing.
Open the Accessibility StatementA district rollout should agree on enabled AI features, staff roles, roster and identity setup, retention expectations, family communication, and the people who own follow-up review.
The sales kit includes a 60-day pilot agreement and a path for district-specific pricing, DPAs, security questionnaires, and board walkthroughs. Do not promise a support or turnaround SLA unless it is in the district's proposal or contract.
Open the pilot agreementThe Trust Center publishes a security overview, subprocessor materials, status page, responsible-disclosure path, and incident-response runbook for district review.
The current Trust Center description and the sales security summary describe different confirmed-incident notification timings. Sales must ask the trust owner to reconcile the current SLA before quoting a number or adding it to an RFP response.
Open the Trust CenterSupporting artifacts
Owner follow-up
Trust / legal: Reconcile the confirmed-incident notification SLA across the Trust Center and sales security summary before quoting it.
Sales operations: Attach the district's state addendum, executed DPA language, and any requested security questionnaire to the deal record.
Finance / operations: Provide the current W-9, ACH instructions, and certificate of insurance when a district requests a complete purchasing packet.
Product / AI operations: Reconfirm the active model provider and applicable retention terms whenever a provider, endpoint, or AI feature changes.
Implementation owner: Document enabled features, staff roles, family-notice steps, local retention policy, and support expectations for each rollout.
Send the district name, state, student count, deadline, and required artifacts. We can route DPA, security, accessibility, and implementation questions to the right owner.