District policy controls for direct AI use on managed devices.
Trust center
Tenet Trust Center: privacy, security, and data boundaries.
Tenet is designed to minimize data exposure while giving districts configured control over AI use. Review what runs in the managed browser, what the service stores, and which claims remain subject to district legal and security review.
Governance for AI operations inside participating district applications.
DPA materials, data-flow explanations, and security questionnaire responses.
Current controls
Trust starts with knowing where the data goes.
These statements describe the current Tenet Edge architecture, including the difference between routine local processing, TrueMadeAI-hosted configuration data, and district-controlled BYOS analytics or incident evidence. A signed district agreement and DPA control a deployment.
Content boundary
Sensitive checks run on the managed device.
Tenet Edge evaluates supported interaction paths locally. Routine prompt and response bodies are not transmitted to or retained by TrueMadeAI's product backend.
Purpose limitation
The backend holds the data needed to apply district policy.
That includes policy configuration, roles, roster and schedule mappings, class assignments, platform permissions, and operational account data.
Tenant boundary
District records are separated by authorization and data controls.
District context is enforced in application services and at the data layer. Administrative access is limited to the scope required for the user's role.
BYOS boundary
Districts control configured analytics and evidence destinations.
General analytics exclude raw prompts, responses, file contents, removed identifiers, and pseudonym mappings. Incident evidence is a separate data class and may preserve conversation text and identifying context for defined events in a district-controlled destination. Review the full boundary.
Data protection
Service traffic and stored service data are protected.
Client-to-server traffic uses TLS 1.2 or later. Stored service data uses provider-managed encryption at rest, with access limited by role and operational need.
Procurement
Claims stay tied to reviewable evidence.
We do not list certifications we do not hold. Districts can request the current data-flow explanation, DPA materials, and answers to a security questionnaire.
Review package
Bring procurement, security, and counsel into the same conversation.
We answer technical and contractual questions directly. We also distinguish shipped controls from roadmap work so district reviewers can evaluate the product as it exists today.
- 01Data-flow review
What runs locally, what the service stores, and where district-configured events can go.
- 02Contract review
DPA materials and deployment-specific responsibilities for the district and TrueMadeAI.
- 03Accessibility status
Current design practices, feedback route, and the conformance target we are working toward.