Privacy policy
Built to guide students, not to watch them.
Privacy is part of the product, not an afterthought. This page explains what SafeSight stores, who can see it and what we never do, in plain words.
The short version
- Teachers see summaries and scores by default, not your chats.
- Students can see all of their own data, including everything a teacher can see about them.
- Student work and conversations are never used to train any AI model.
- Live Lab Mode records activity only during an announced exam session on a college lab PC, and stops when the session ends.
- SafeSight never labels anyone as dishonest. It shows neutral evidence, and teachers decide.
- Chats and writing events are deleted after 180 days. Only aggregate numbers are kept.
What we collect
Your account
Your name, email address and role (student or teacher), and the institution and courses you belong to.
Conversations with Sage
The messages you send Sage and its replies, saved with the assignment they belong to. Each message also gets a short label (for example “concept question”) and the hint step Sage used, so the class dashboard can show patterns.
Writing in Trace
When you write an assignment in the Trace editor, it records how the text was made: typing, pasting, deleting, and when the editor was in focus, with times and sizes. It also stores what you submit. Trace runs only inside its own editor; it does not see anything else on your device.
Live Lab Mode
During an announced lab exam, the SafeSight Lab extension on a college PC records tab switches, copy and paste, attempts to open blocked sites, idle time and a regular heartbeat for that seat. Outside a session it records nothing.
Course material
Notes and PDFs a teacher uploads, split into searchable passages so Sage can cite them.
Pilot requests
If you request a pilot on our website, we store your name, role, institution and email so we can plan the pilot with you. We use it for nothing else.
Who sees what
| Who | What they can see |
|---|---|
| A student | All of their own data: every chat, score, flag about them and replay of their writing. Never another student's. |
| Their teacher | For their own courses only: usage summaries, Reliance Scores, topics the class asks about, flags and Trace evidence summaries. The full text of a chat opens only for a flagged item, or when the student chooses to share it. |
| Other teachers | Nothing about students outside their own courses. |
| The SafeSight team | Only what we need to run and fix the service, and never to sell or advertise. |
If a chat shows signs that a student is in distress, Sage responds with care, shares the college counselling contact and a helpline, and raises a private flag for the teacher. Students don't see that flag on their own list, so it can be followed up gently.
How we use AI
Sage, Lens and Trace run on large language models that we call from our own servers through a model provider's API. Your browser never talks to the model directly, and our keys never leave the server.
Student data is never used to train AI models, by us or by the provider. For each pilot we share the exact model and hosting region in writing before it starts.
The AI never decides anything about a student. Trace writes neutral evidence such as “one paste at 14:32 made up 78% of the final text”. What that means is the teacher's call.
How long we keep it
Chats and writing events are deleted after 180 days. After that we keep only aggregate numbers, such as weekly message counts and Reliance Scores, so teachers can still see trends over a semester.
Pilot requests are kept until the pilot conversation is over, or until you ask us to delete them.
Your choices
- See everything SafeSight holds about your learning on your own pages in the student app.
- Choose whether to share a chat with your teacher. Nothing is shared unless you share it or it is flagged.
- Ask for your data to be corrected or deleted, through your teacher or institution, or by writing to us.
Before anyone uses SafeSight, a one-time screen at sign-up explains what is recorded and who sees it. Real students take part in testing only with their consent, and our demo data uses invented names only.
Keeping it safe
Every table in our database has row-level security, so the database itself checks that a student can read only their own rows and a teacher only their own courses. We test this rule automatically. Connections are encrypted, and API keys live only on the server.
Changes and contact
If we change this policy, we will update the date at the top and tell the teachers and institutions we work with before the change applies to them.
Questions about your data? Write to us and a real person will reply.
Bring SafeSight to your course next semester.
Start with a single course. We do the setup with you, and it is always free for students.