CROWN TRUST & DATA STEWARDSHIP

Trust should be documented, tested, and reviewable.

A school entrusts its operating platform with people, money, records, decisions, and daily responsibilities. Marketing language is not sufficient. The written agreement and launch evidence must make the protections, limits, responsibilities, and unresolved risks visible.

THE FOUNDING-SCHOOL STANDARD

No critical promise should depend on assumption.

This page describes the questions and evidence CROWN intends to place into founding-school due diligence. It is not a certification, warranty, or claim that every control is already complete. Final safeguards, service terms, vendors, availability, and technical assurances must be confirmed in the school's current written proposal and agreement.

Data ownership and permitted use

The agreement must identify school ownership, CROWN's permitted processing, purpose limits, retention, return, export, and deletion responsibilities.

School and household separation

Tenant, role, household, student, and staff boundaries must be validated so information is not exposed to another school or unauthorized person.

Identity and least privilege

Administrative control, role assignment, staff transitions, elevated access, authentication, and audit evidence must be defined and tested.

Security and incident responsibility

Safeguards, monitoring, vendor responsibilities, escalation, notification, investigation, correction, and school communication duties must be documented.

Backup, recovery, and continuity

Backup scope, restoration testing, recovery expectations, service continuity, support ownership, and critical-workflow alternatives must be addressed.

Migration, integrations, and reconciliation

Source quality, mapping, transfer, interface behavior, exceptions, totals, audit history, and acceptance evidence must be agreed before live operation.

Export and transition

Schools should know how authorized data can be exported, which formats are supported, what is retained, and what happens when the relationship ends.

Accessibility and usable controls

Essential role journeys should be checked across devices and with the people who rely on accessibility support.

SOLOMON • KNOWLEDGE, GUIDANCE & INTELLIGENCE

AI assists. People decide. CROWN records why.

Solomon may help explain workflows, locate governed knowledge, frame questions, summarize non-sensitive information, and support responsible analysis. It does not replace the authority or accountability of school leaders.

Restricted decisions

Solomon must not autonomously decide discipline, financial aid, admissions, health, grading, child safety, emergency response, personnel, legal or compliance matters, or financial transactions.

Protected information

Student, parent, financial, health, and other personally identifiable information must not be exposed to uncontrolled third-party intelligence services. Any approved use must follow the documented data boundary, access rules, and school agreement.

BEFORE GO-LIVE

Ask for evidence connected to the agreed scope.

Role and permission matrix
Tenant and household isolation checks
Migration reconciliation and exception record
Integration inventory and responsible owners
Backup and restoration evidence
Incident and escalation contacts
Data export and transition process
Training and role-journey completion
Known limitations and accepted risks
Written activation approval

PUT DUE DILIGENCE IN THE CONVERSATION

Bring your privacy, security, data, integration, and continuity questions.

CROWN should earn confidence by answering the questions clearly and documenting what remains to be completed.

Discuss trust and data stewardship Review founding-school participation