Security & Trust

Trust should be understandable.

Schools should know what data a product uses, who can access it, how AI is grounded, what happens when a contract ends, and which responsibilities belong to the school and the vendor.

Operating model

Clear boundaries before badges.

Auzi is designed to support schools’ FERPA obligations. That is a shared operating and contractual responsibility—not a simple product certification.

01

School and tenant boundaries

Branding, content, data, knowledge sources, administrators, and permissions are configured within a school context.

02

Role-based access

Private resources are made available by authenticated school and role when included in the plan.

03

Public vs authenticated information

Public knowledge and authenticated/private contexts are separated in the product model.

04

Approved AI knowledge

School-specific AI is grounded in sources the school approves. Access can be limited by public or authenticated context.

05

Data access

Access is controlled by school, tenant, and role. Audit history is included where the contracted plan provides it.

06

Human responsibility

Schools approve content and authorized users. Auzi documents vendor responsibilities and maintains the reusable platform.

Ownership

School data stays school-owned.

Auzi maintains the reusable platform and product code. The school retains ownership of its data and content. Evaluation and contract documents should define permitted processing, retention, export, deletion, and termination responsibilities.

Auzi does not publish the claim that school data is never used to train public or general-purpose models until every relevant provider and contract has been confirmed by the owner.

Responsible school AI

Grounded answers. Human accountability.

Auzi AI answers from information a school approves. Public assistants can help families find public calendars, policies, forms, and resources. Authenticated assistants can be limited by school and role when private access is contracted.

  • Approved sources instead of open-ended generic web search
  • Separate public and authenticated contexts
  • Defined usage allowances instead of “unlimited AI”
  • Human review of sources, permissions, and published experience

Evaluation documents

Documentation a school should expect.

These documents are not yet approved for public download. Auzi should provide current versions during evaluation once the owner completes them.

Data Processing Agreement

Available by request during evaluation after owner approval.

Request during review

Security overview

Available by request during evaluation after owner approval.

Request during review

Subprocessor list

Available by request during evaluation after owner approval.

Request during review

AI data-use statement

Available by request during evaluation after owner approval.

Request during review

Accessibility statement or roadmap

Available by request during evaluation after owner approval.

Request during review

Retention and deletion process

Available by request during evaluation after owner approval.

Request during review

Incident-response process

Available by request during evaluation after owner approval.

Request during review

School data export and termination process

Available by request during evaluation after owner approval.

Request during review
Request the evaluation package

Leaving Auzi

Plan export and deletion.

A school evaluation should confirm what can be exported, the format and timing, who authorizes termination, the retention window, deletion verification, and any legally required exceptions.

Auzi’s final public claims will follow the approved Data Processing Agreement and production procedures rather than making an unverified promise here.

Accessibility

Accessibility is a requirement.

This marketing site targets WCAG 2.2 AA behavior, including semantic structure, contrast, keyboard access, visible focus, comfortable targets, reflow, and reduced motion.

Auzi’s product accessibility statement or roadmap is still an owner-input document. School-provided content also requires an agreed governance and remediation process.

Publisher ownership

Schools own publisher accounts.

For standalone branded apps, Auzi recommends that the school own its Apple and Google organization or publisher accounts and invite Auzi to manage technical submission and updates. The school completes required identity and legal verification.