Guided Scholar was built by an educator for educational contexts. Trust, safety, and student privacy are not features added after the fact, they are foundational to how the system works. In school-account deployments, that includes teacher visibility, class-linked activity, and school-governed access controls.
Districts and schools evaluate AI tools differently than they evaluate consumer software. The questions they ask are not just about features, they are about governance, accountability, and what happens to student data. These are the right questions, and Guided Scholar was designed to answer them clearly.
This page describes how Guided Scholar handles student data, how teachers maintain visibility into student work, how the system supports academic integrity rather than undermining it, and what compliance frameworks apply. One point worth stating directly: in school-account deployments, Guided Scholar is not private student AI use. It is a governed, class-linked practice environment visible to the responsible teacher and controlled by the school deployment context. Where answers are incomplete because the system is still in development, we say so directly.
Student submissions are not used to train AI models. Data is retained for defined periods and then deleted. No third-party AI provider receives or retains student data.
In school-account deployments, teachers see every student's draft history, revision depth, and progress status. Student practice is class-linked and teacher-visible, not private chatbot access.
Guided Scholar does not generate student content. The student writes. The system responds to what they wrote. Feedback supports revision, it does not replace teacher judgment or produce finished work.
Guided Scholar collects only the data necessary to deliver feedback and support teacher visibility. No data is sold. No data is used to train AI models. No student data is transmitted to or retained by third-party AI providers.
In school-account deployments, student activity (submissions, revision history, and feedback records) is visible to the responsible teacher and governed by the school deployment context. This is not private student AI use. Family and homeschool accounts may include parent or guardian visibility and control, governed by the account model rather than school deployment policy.
| Data Type | Collected | Used To Train AI | Retention |
|---|---|---|---|
| Student draft submissions | Yes | No | 6 months active, 6 months archived, then deleted |
| Revision history | Yes | No | Same as above |
| Feedback records | Yes | No | Same as above |
| Login / account information | In development | No | To be defined upon release |
| Usage analytics | Limited | No | Aggregated, non-identifiable |
Note on the login system: Guided Scholar's student and teacher login system is currently in development. Complete account data policies will be published prior to broader rollout. Schools and districts with specific data handling requirements are encouraged to contact us directly to discuss requirements before piloting.
One of the most important questions about any AI writing tool is whether teachers can verify that students actually used the feedback. Guided Scholar's teacher dashboard answers that question directly.
Teachers can see: every student's draft count and last activity timestamp, revision depth classified as substantial, moderate, surface-only, or no revision, a side-by-side comparison view of any two drafts, revision insights showing word delta and structural changes, and automatic flagging of students who received feedback but have not yet revised.
In school-account deployments, this visibility is not optional, it is the default. Student practice inside Guided Scholar is a governed, class-linked activity. It is not a private student AI companion. Teachers maintain oversight of the work, the revision history, and how students respond to feedback. That oversight is what distinguishes bounded educational AI assistance from unrestricted general-purpose AI access.
This visibility does not require teachers to read every draft. It gives them the information they need to prioritize their time, identifying students who are engaging meaningfully versus those who need direct intervention.
The teacher assignment module, which will allow teachers to assign specific prompts, set deadlines, and manage class-level workflows, is currently in development and expected in beta within weeks. When released, teachers will have direct control over which assignments students work on within Guided Scholar and will be able to view all student work within their assigned classes.
The central concern schools have about AI in writing instruction is the same concern that motivated Guided Scholar's design: does this tool do the work for the student, or does it help the student do better work themselves?
Guided Scholar cannot produce student content. This is not a setting that can be toggled, it is how the system is built. The student submits their own writing. The system returns structured feedback, rubric scores, revision suggestions, and prioritized next steps. The student then decides whether and how to revise. The system does not assign final grades or replace teacher judgment, it provides instructional feedback that supports revision.
The revision visibility teachers have in the dashboard exists precisely so they can see whether a student's revision was substantive, whether they actually processed and acted on the feedback, or whether they made cosmetic changes and resubmitted. That distinction is visible in the data, and it is the key question for academic integrity in any feedback-driven system.
In school-account deployments specifically: student practice is not private AI use detached from school oversight. It is assignment-bounded, class-linked activity. Teachers control the deployment context, can see all student work, and retain full instructional authority over how feedback is applied and how work is evaluated.
Guided Scholar is designed with FERPA and COPPA requirements in mind. Because the system is currently in a beta phase with a limited pilot context, formal compliance documentation (including a complete privacy policy, terms of use, and student data agreement) is being developed in parallel with the teacher module and account system.
Schools and districts considering Guided Scholar for pilot use are encouraged to contact us directly. We are committed to meeting district-specific data handling requirements and will work with technology coordinators and administrators to address compliance questions before any broader deployment.
Coming soon: Formal Privacy Policy, Terms of Use, Student Data Policy, and FERPA/COPPA Alignment Overview. These documents will be published prior to any non-pilot deployment. Contact peter@guidedscholar.ai for questions in the interim.