Public policy
Privacy policy and student data handling
Koydo's public privacy surface covers student data categories, processor inventory, retention, DSAR rights, and COPPA handling for children and families.
Source
src/app/legal/privacy/page.tsx
Loading...
Institutional Trust Center
Koydo is the operating system for lifelong learning, and institutional trust has to be reviewable, not just claimed. This page packages the public surfaces, operational controls, and procurement workflows that school and government teams can review today.
Verified Paths
Review Surfaces
Some materials are publicly available and some live in partner diligence packets. The point is consistent evidence across public review, procurement review, and live institutional operations.
Public policy
Koydo's public privacy surface covers student data categories, processor inventory, retention, DSAR rights, and COPPA handling for children and families.
Source
src/app/legal/privacy/page.tsx
Public legal surface
Terms of service versioning, policy acceptance evidence, processor controls, and state-aware legal review paths are documented for institutional diligence.
Source
docs/legal/framework.md
Public policy
The public deletion workflow explains how families and institutional partners can request account deletion and how those requests map to Koydo's retention posture.
Source
src/app/data-deletion/page.tsx
Public diligence surface
Koydo now publishes an accessibility review surface and tracks a WCAG audit baseline plus remediation roadmap for institutional diligence.
Source
src/app/legal/accessibility/page.tsx
Partner diligence packet
Eight-layer child safety architecture includes COPPA gate, moderation, rate limiting, CSRF protections, and server-controlled prompt boundaries.
Source
docs/security/child-safety-architecture.md
Partner diligence packet
OpenAI DPA execution, disabled data sharing, and zero data retention controls are tracked for legal and procurement review.
Source
docs/compliance/openai-coppa-status.md
Operational Controls
These are the control surfaces already shaping institutional rollout and governance inside Koydo today.
District-managed identity can flow through SSO providers, organization roles, SCIM users, and provisioning tokens rather than ad hoc learner signups.
Organization-level classroom policy can restrict access by time zone, country match, school hours, and account class for managed deployments.
Scheduled report jobs, export generation, organization audit events, and procurement packet archives create a durable governance trail for pilots and renewals.
Feature flags, rollout percentages, and kill switches support staged school, district, and government deployments with emergency stop paths.
Buyer Workflows
Public review, partner diligence, and rollout planning should connect cleanly. These are the current paths we support.
Start with the public trust, privacy, and terms surfaces before moving into deeper institutional diligence.
Open privacy policyInstitutional partners can generate organization-specific procurement packets with live readiness, reporting, and trust evidence.
Request procurement reviewSchool and district teams can align on implementation, reporting cadence, and deployment profile before broader rollout.
Talk to partnerships