PRIVACY & SECURITY
A careful approach to sensitive work.
Student records and session recordings deserve a specific conversation about who can access them, where they are processed, and how long they are kept.
What this preview does - and does not - represent.
The screens on this site illustrate a planned product. They use fictional information and do not demonstrate a completed security certification, Canadian-only hosting arrangement, or approval to handle real-client records.
The proposed controls.
These controls are part of the implementation specification. Their operation must be tested and documented for the deployment in scope.
Access by role and relationship
Institution membership, assigned student relationships, and recording permissions are separate decisions.
Deliberate recording access
Meeting participation does not automatically grant playback rights. Sharing and revocation are explicit actions.
A defined recording lifecycle
Recordings, shares, and retained supervision information need documented retention and deletion rules.
Traceable review actions
Approvals, corrections, and evaluation versions need to remain attributable to their records.
What to review before a deployment.
The implementation discussion should establish the facts for the specific service being proposed.
- Storage and processing regions, including backups and support access.
- Subprocessors and third-party media, identity, notification, and reporting services.
- Authentication, access testing, incident response, and operating responsibilities.
- Retention, archival, backup deletion, and access after a host or student leaves.
- Institutional consent, permitted use, and the boundaries between clinical and educational records.
- Export, migration, termination, and deletion arrangements.
Do not send student or client records through this website.
A marketing inquiry should contain only the contact and program information needed for the conversation. There is no session-recording or document-upload function on this website.
Start with your institution's requirements.
Bring your procurement and data-handling questions to the walkthrough. Detailed answers need to match the agreed deployment, not a generic checklist.