Privacy

My Socrates is an educational research tool. This page describes how the application handles information in the demonstration environment and in instructor-run courses. It is written in plain language and avoids absolute guarantees: where a limitation exists, it is stated.

• Account information. For signed-in users: email address, display name, assigned role (student or instructor), and course enrollments.
• Conversations. Messages you send and the responses you receive are stored so that a session can be resumed, reflected on, and — for enrolled courses — summarised for the instructor.
• Learning signals. Practice attempts, reflection notes, and derived progress indicators tied to your account.
• Course materials. Readings, syllabi, and learning outcomes uploaded by instructors, and text extracted from them.
• Operational records. Timestamps, coarse rate-limit identifiers, and security events used to keep the service available and to detect abuse.

Demo sessions are deliberately narrow. They use a fixed sample course and public-domain readings, are capped in length, and are not connected to production course data. Demo conversations are still transmitted to the configured AI provider and stored briefly so the session and its reflection can be shown back to you.

Demo and evaluator records are removed by a scheduled cleanup process after their retention window elapses. Cleanup runs on a schedule rather than instantly, so a short delay between session end and deletion is expected.

Please do not enter personal, confidential, or identifying information into a demo conversation.

Generating a response requires sending the relevant conversation and course excerpts to an AI provider. Instructors and administrators supply their own provider credentials, which are stored encrypted and are never displayed again after being saved. Once text reaches a third-party provider it is handled under that provider’s own terms, which My Socrates does not control.

• You can see your own conversations and progress.
• Instructors of a course you are enrolled in can see aggregate class patterns, and your individual work for that course.
• Administrators can see operational and security records needed to run the service.

Access is enforced at the database level with row-level security policies, in addition to checks in the application.

Course and account data are retained while the course is active. Demo and evaluator data are retained only for their session window plus the scheduled cleanup interval. To request export or deletion of your data, contact your instructor or the administrator who invited you.

The application stores a session token and a small amount of local state — such as accessibility preferences and unsent message drafts — in your browser. The hosting platform sets a bot-management cookie. No advertising or cross-site tracking cookies are used.

This page will be updated as the application changes. Material changes affecting enrolled students will be communicated through the course.