What we collect
The information needed to run the service: accounts from your roster, and conversations.
Clear about where your data goes.
Plain terms for school leaders, IT, and privacy staff.
The plain version.
On our hosted service, student data is held in our systems, in your region (Canada or US), under a data-processing agreement with your school. The school is the data controller. We act on your behalf. During the beta, Trailpost runs on our shared hosted service. To write an answer, it sends the student’s question and the source text it found to an AI model service (OpenRouter and the model company behind it). It doesn’t send names, email addresses or class details. When your school signs on, we set up your own Trailpost instance, and student questions no longer go to any outside AI service.
What happens to data
Who sees what, and for how long.
Who can see it
Students see their own history. Teachers see their own class’s usage and flagged messages. Counselors see the conversation around a safety alert. School admins see aggregate reports and flagged messages, and can open a student’s full conversation only for an investigation, with a stated reason — every access is logged. We have no routine access to conversations.
How long it’s kept
Your school sets retention and can delete data, including on a parent’s request.
Your controls
Content settings, user roles, retention and legal hold, records export, and which approved content is on.
Final terms are set in the data-processing agreement.
Parent rights
Families stay in the loop.
Parents can ask to see a summary of their child’s usage, request deletion, or opt their child out. Schools handle these requests through their existing processes. We provide the tools.
Hosting options
Hosted by default, in your region.
Most schools choose the hosted service: nothing to install, and available at school and at home. Your data stays in your region, under a data-processing agreement.
The rules schools work under
Designed to support the rules you work under.
We design to support the privacy rules schools work under, including FERPA and COPPA in the US, and PIPEDA and provincial privacy laws in Canada.
What we don’t claim yet. We don’t claim security certifications at this stage. When we hold them, we’ll say so here.
Privacy brief
Want the details in writing?
Request our privacy brief for your IT or privacy team.
FAQ
During the beta, yes. Trailpost runs on our shared hosted service. To write an answer, it sends the student’s question and the source text it found to an AI model service (OpenRouter and the model company behind it). It doesn’t send names, email addresses or class details. When your school signs on, we set up your own Trailpost instance, and student questions no longer go to any outside AI service.
Not routinely. Flagged messages go to the right staff. A full conversation can be opened only for an investigation, with a stated reason, and every access is logged.
[TO CONFIRM BEFORE PUBLISHING]
In your region, Canada or the US, depending on your school.
Yes. On-premises options are available for boards that require it.
Your school is the data controller. We act as your data processor.
Help shape it.
We’re working with a small group of schools to build and test Trailpost. Pilot schools help decide what success looks like.
Join the pilot