de:volt Learn is designed for classroom and self-paced electronics learning. It may be used by individual learners, teachers, schools, universities, and other training organisations. This notice supplements the Privacy Policy and Terms of Service.

A school, teacher, administrator, parent, guardian, or other adult who invites students or directs students to use de:volt Learn must have the authority required by law and institutional policy. This includes any required parent, guardian, school-official, procurement, privacy, accessibility, safeguarding, and acceptable-use approvals.

Students under 13, or under the local age requiring adult or school authorisation, may use de:volt Learn only through an authorised school, parent, guardian, or other responsible adult.

• school, organisation, class, and course names;
• teacher, owner, and student memberships, roles, status, and email/display information;
• join codes, teacher invites, and invitation metadata;
• lesson modules, teacher-authored content, drafts, published versions, and solution circuits;
• student attempts, objective progress, timestamps, assignments, submissions, auto-check results, scores, and marking metadata;
• live classroom session status, presence, current module, and class progress signals; and
• support messages, education pilot enquiries, and operational logs needed to run and secure Learn.

Students can see their own classes, modules, assignments, submissions, progress, and grades where the product exposes them. Teachers and school owners can see class rosters, progress, assignment status, submissions, scores, and live session state for classes they are authorised to manage. de:volt support may access data only where needed to operate, troubleshoot, secure, or legally protect the service.

Teachers and schools must not use de:volt Learn to:

• collect unnecessary student personal information;
• publish unlawful, infringing, unsafe, harmful, discriminatory, or inappropriate content;
• use join codes or invite links in a way that exposes students to unauthorised access;
• share student progress, scores, or submissions with people who are not authorised to receive them; or
• use simulator or AI outputs as safety-critical engineering advice.

If a student, parent, guardian, or regulator requests access, correction, export, restriction, or deletion of education data, the school should send the request to dev@kapadia.bizwith enough detail for us to locate the relevant account, class, or organisation. We will work with the authorised school contact to respond where required by law and feasible in the current product.

Schools that need a written data-processing agreement, procurement terms, accessibility documentation, security questionnaire, or subprocessor list should contact dev@kapadia.biz. Until a separate agreement is signed by de:volt, the public terms, privacy policy, this notice, and any written quote or order terms govern use.

de:volt Learn includes an optional AI tutor that gives short, Socratic hints while a student works on a lesson objective. The tutor is available only where de:volt has enabled it and the student is on an eligible plan, and it is off by default. When a student asks for a hint, de:volt sends a compact summary of the student's current work to our AI provider, OpenRouter, using the configured model provider (currently DeepSeek). This summary may include the objective title and text, a count of components, wires, and nets, a short list of representative component kinds, labels, and numeric parameters, and a brief machine-generated note about why the objective is not yet passing. It does not include the full circuit schematic, the student's name, email, or account identifiers.

Tutor hint requests are processed ephemerally. de:volt does not store the circuit summary, the prompt, or the AI-generated hint in any per-student record, and the AI tutor does not write to student conversation or message history. We retain only aggregate operational metrics for each hint request, such as an identifier derived from the lesson objective's title, input and output token counts, estimated cost, the response source, an opaque session identifier, the provider name, and a coarse error category. We do not log the prompt text, the hint text, the failure summary, the circuit summary, or any component labels.

Teachers and schools should not direct students to enter sensitive personal information into circuit labels or objective content, because that content can be included in the summary sent to the AI provider. As with the simulator AI assistant, simulator and AI outputs are learning aids and must not be relied on as safety-critical engineering advice. The AI provider is listed in the Subprocessors Notice, and general AI processing is described in the Privacy Policy.