Access with boundaries
Organization-aware roles, delegated responsibility, review paths, and protected administrative actions keep authority explicit.
K12First Trust Center
Trust begins with
clear boundaries.
Security, privacy, reliability, and honest communication shape how K12First builds and operates Cast and Guard.
Product-specific safeguards Observable operations Responsible disclosure
Service statusPublic operational view
Protected connections
HTTPS transport, encrypted credentials, validated events, and narrowly scoped integrations protect service communication.
Operational visibility
Health, activity, decision evidence, acknowledgments, and audit history make important system behavior visible.
People-centered response
Consequential changes are designed around authorized review, understandable context, and accountable follow-through.
Product safeguards
Trust should be specific to the product.
Cast and Guard handle different work. Their security explanations should reflect those differences.
Cast security
Private-by-default content, scoped roles, approvals, signed player operations, integration safeguards, visible player health, and recoverable workflows support responsible school communications.
Explore Cast
Guard security
Tenant-aware data access, message custody, explainable policy evidence, quarantine review, scoped provider actions, and durable receipts support responsible email-security operations.
Explore GuardShared operating principles
Secure defaults. Explicit changes. Evidence where it matters.
Data minimizationCollect and expose only the information needed for the authorized product workflow.
Tenant-aware accessScope customer data, policy, identity, and administrative actions to the organization.
Reviewed changeUse staged activation, canaries, acceptance checks, and rollback planning for consequential integrations.
Honest claimsDescribe implemented safeguards and current availability without implying certifications or guarantees that have not been earned.
Operational transparency
Check service status or report a concern.
The public status page provides a privacy-safe view of K12First service health. Suspected vulnerabilities should be reported privately without credentials, student data, or suspicious attachments in the first message.
Talk with K12First
Have a security or procurement question?
Tell us what your district needs to review. We will bring the right technical and product context.