How Session and Course Data Moves Through Sukma
Effective date: February 27, 2026
This page explains how Sukma handles session data, user data, and course data in both institution-managed deployments and personal learning accounts. The goal is simple: give buyers and users a clear view of how records move through the platform, where governance is applied, and how continuity is maintained without unnecessary data exposure.
Institution-Managed Flow
1. Learner, educator, host, and agent activity is recorded inside the governed session context.
2. Audience questions are stored as governed session records and normalized into lifecycle status records.
3. Session artifacts such as examples, assessments, whiteboards, and summaries are created as part of the learning workflow.
4. Host or agent actions update question status, instructional artifacts, and session state for review and follow-up.
5. The institution's retention policy is applied to governed conversation content, including learner, host, educator, and agent conversation records stored in session events.
6. After the retention window, governed conversation payloads can be redacted while metadata remains available for audit history.
7. If the institution requests an explicit purge, Sukma can remove governed conversation records, audience queries, examples, assessments, whiteboards, and session summaries for the selected scope.
Independent Learner Flow
1. An independent learner runs a personal session.
2. Session interactions and a summary are generated to support learning continuity.
3. The learner can optionally add verified summary recipients such as a parent or observer.
4. Personal-account privacy, retention, and account-rights policies apply.
Why the Design Matters
• Institutions get governance, accountability, and reviewability for student-facing activity.
• Independent learners get privacy controls without being forced into institution-style governance.
• Session continuity comes from summaries and structured records, not indefinite raw-conversation retention.
Retention and Deletion
• Institution policies can set conversation retention from 7 to 90 days.
• Governed conversation payloads can be redacted after the configured window.
• Explicit org purge can delete audience queries, examples, assessments, whiteboards, summaries, and selected conversation records.
• Metadata can remain available for traceability, policy review, and operational evidence unless the institution requests purge for the selected records.