How Adaptive Tutor Operates

Transparency

Review current service checks, incident-history coverage, support routes, accessibility status, service providers, source code, and release information.

Loading review information.

Technical readers can also download the operations record or review release trust information.

Public routes

Service status

Check whether Adaptive Tutor and its required services are responding, and review incident-history coverage.

Support intake

Ask for help without automatically attaching diagnostics, secrets, or learner records.

Accessibility statement

Read the accessibility goal, what we test, known limitations, and feedback route.

Security contact

Report a security concern privately through the coordinated-disclosure channel.

Source and releases

Download source code and find the license, third-party notices, software inventory, and verification instructions.

Privacy and providers

Read the current privacy policy and review the service-provider information below.

Historical Coverage

Incident history

Loading incident-history coverage. An empty loading state is not evidence of zero incidents.

Incident history requires the local script to read the public record. Review operations.json; its checked-in unavailable state is not a claim that no incidents occurred.

Service Providers

Provider review

Loading provider verification state.

Service-provider inventory and current verification state
Provider	Purpose	Data	Location evidence	Verification state
Loading the machine-readable inventory.

Release Information

Verify a downloaded release

Checking for a complete site release manifest.

Loading pinned release trust identity.

The maintained local command is:

.venv/bin/python scripts/public_transparency.py verify-release --bundle-dir RELEASE_DIRECTORY

After one locked uv sync --locked --all-groups dependency bootstrap, the offline verifier recomputes every SHA-256 digest and verifies release-signature.json with a source-pinned, version-bounded Ed25519 public key. The signature binds the Adaptive Learning repository, tag, commit, build ID, exact SHA256SUMS bytes, and full sorted subject map. It proves possession of the long-lived release key, not a GitHub OIDC identity or transparency-log time. A site manifest alone is not a signature.