Trust control panel · public edition

Trust begins with state, source and limits.

This centre separates what the website can demonstrate from policies, operators and assurances that are not yet approved for publication.

Control register

Read the boundary beside the claim.

A partial state means only the written public boundary is supported. It does not imply an audit, certification or production SLA.

TRUST-02 · PARTIAL

Security overview

Public entry and continuity controls are documented where the website can prove them.

Infrastructure topology, certifications, audit results and incident metrics are not published without approved records.
TRUST-03 · WITHHELD

Retention and deletion

No retention duration is presented as policy until legal and product owners approve it.

The previous page-authored deletion and tax-retention timelines were removed.
TRUST-04 · PARTIAL

Student and minor privacy

Public examples avoid personal records and parent examples are labelled SAMPLE.

Consent ages, guardian powers and response times require an approved privacy record.
TRUST-05 · UNAVAILABLE

AI providers and subprocessors

A provider list is not currently approved for public release.

No vendor, hosting location or data-transfer claim is inferred from code or marketing copy.
TRUST-06 · PARTIAL

Model and data use

Public tools state their source, limitation and unavailable modes near the result.

Training-data and model-provider policies remain withheld until an owned policy record exists.
TRUST-07 · WITHHELD

Vulnerability disclosure

The disclosure workflow is designed but no public security contact is verified.

A security.txt file will not publish a guessed inbox or response promise.
TRUST-08 · UNAVAILABLE

Incident communication

No incident SLA or communication channel is claimed without an operational owner.

Service incidents remain an app/operator responsibility until the public policy is approved.
TRUST-09 · UNAVAILABLE

Service status

This website does not simulate uptime or a live status page.

Availability requires production monitoring evidence, not a decorative green badge.
TRUST-10 · PARTIAL

AI transparency cards

Question, predictor and commerce surfaces identify source, method, limitations and app ownership.

Per-product provider and human-review detail remains gated by approved product records.
TRUST-11 · PARTIAL

Challenge and appeal

Public results explain that they are planning or practice aids and may be challenged in the app flow.

No human-response SLA is published without a verified support route and owner.
TRUST-12 · WITHHELD

Certifications and assurance

No certification badge appears on the public website.

Certification, audit and compliance claims require scope, issuer, validity and evidence.
Human path

No guessed inbox. No fake status.

Security, grievance and privacy contact details stay withheld until the owner-fact and legal review gates approve them. Product entry remains available; policy escalation is not simulated.