Trust centre
A plain-English view of what the product processes, when AI is involved, where teachers remain in control and which questions a school should settle before adoption.
At a glance
Feynman Education is a retrieval-practice application for schools. It stores the information needed to operate classes, deliver questions, mark answers and show progress to authorised users.
AI and data flow
The current AI marking provider is Anthropic. When an open written answer needs AI assessment, the service may send the question text, model answer or marking points, relevant marking guidance and the pupil-written answer to Anthropic. The routine marking prompt is designed not to include the pupil’s name, email or internal user identifier.
Some staff AI tools process class misconceptions or generate questions. Those operations may send anonymised wrong-answer text and private teacher question-bank content to Anthropic. The application records provider, model, request and response identifiers, operation, latency and success information for operational usage monitoring.
Multiple-choice, exact-match, numerical and previously accepted equivalent answers can be handled without a new AI request. This reduces external processing as well as cost.
Teacher control
AI output is not treated as unchallengeable. Pupils can flag a decision, teachers can review the original answer and marking context, and authorised staff can uphold or overturn the mark. A marking-quality dashboard shows review and agreement information.
Schools control their own class setup, content selection, assignments and teacher-created questions. Feynman should support professional judgement rather than replace it.
Security and access
Authentication is provided through Supabase Auth. Application records are protected using authenticated requests, role-aware application checks and database row-level access policies. Teacher, head-of-department and moderator capabilities are separated.
- Production traffic is served over HTTPS.
- Secrets used by server-side functions are not exposed in the browser application.
- Administrative actions require an authenticated, authorised account.
- Usage and request identifiers support investigation without being used as pupil-facing identifiers.
To report a suspected vulnerability or incident, email schools@feynmaneducation.com with “Security” in the subject line.
Service providers
The current core service stack includes Vercel for web hosting, Supabase for authentication, database and server functions, and Anthropic for the AI operations described above. Provider and processing terms can change as the service develops; schools should request the current subprocessor and transfer information during procurement.
Retention and deletion
The product retains account, class, question and response records so that pupils can continue spaced practice and staff can review progress. A single universal retention period is not represented here because school requirements may differ.
Before production adoption, a school can request a documented offboarding, deletion and retention schedule appropriate to its role and policies. Account and class-management controls support removal of users and memberships, while database deletion requests should be coordinated to preserve referential and audit integrity.
Accessibility
The interface is being developed toward WCAG 2.2 AA practices, including keyboard-operable controls, visible focus, meaningful labels, responsive layouts, reduced-motion support and readable contrast. It has not yet been independently audited, so we do not claim formal conformance.
Please report a barrier, including the page, device and assistive technology used, to schools@feynmaneducation.com.
School procurement
Schools can use this centre as a starting point and request the supporting information required by their own process, including data-processing terms, subprocessor details, security questions and deletion arrangements.