Effective date: February 27, 2026
Sukma is designed to help colleges, academic programs, and modern learning organizations adopt AI-native learning workflows with clear governance around student-facing sessions, access controls, and course-linked activity. FERPA is a legal framework, not a product badge. Our role is to give institutions the operational controls, contractual posture, and evidence trails they need to deploy Sukma responsibly.
• Governed session data generated during institution-managed learning sessions
• User data used for role-based access, administration, and governance
• Course data used to provide context, continuity, and session outcomes
• Session artifacts such as audience queries, examples, assessments, whiteboards, and summaries
• Audit and evidence records used for institutional review and procurement
• Institution-owned governance over student-related records
• Role-based controls for policy updates, retention, and review workflows
• Audience question lifecycle tracking for accountability during live sessions
• Governance over examples, assessments, whiteboards, and session summaries
• Session-summary continuity without requiring indefinite raw conversation retention
• Default conversation retention window: 30 days
• Institution-configurable retention window: 7 to 90 days
• Conversation payload redaction after retention for learner, educator, host, and agent session-event records
• Explicit organization purge can remove governed conversation records, audience queries, examples, assessments, whiteboards, and session summaries
• Governance evidence that supports security review, contract discussions, and oversight
This page applies to institution-managed environments. Independent learners using personal accounts should refer to the Privacy Notice and Terms of Service.
Institutional counsel should review deployment terms and policies before contract execution.