Privacy
Last updated: March 17, 2026. This page explains what information Coding Pathway uses and how we handle it.
Who this applies to
This notice applies to people using Coding Pathway through the website, sign-in flow, student dashboard, teacher tools, and school-managed classroom use.
Coding Pathway is operated by Christopher Hopkinson, trading as Coding Pathway.
For privacy questions, account requests, or school enquiries, contact schools@codingpathway.co.uk.
What we collect
- Account information needed for sign-in, including name, email address, and sign-in provider.
- Role and access information, such as whether a user is a student, teacher, or admin.
- School, class, assignment, authored content, and progress data needed to run the platform.
- Operational records such as service logs, error records, and key audit events.
- Essential preference information, such as remembered dashboard role selection.
How we use data
- To let users sign in with supported Google or Microsoft accounts.
- To run student learning, submissions, progress tracking, and teacher review workflows.
- To support school, class, assignment, and teacher authoring features.
- To send service emails, such as welcome and assignment-related notifications, when these are enabled.
- To keep the service secure, investigate issues, and improve reliability.
Schools and school-managed use
When Coding Pathway is used by a school, the school may decide which pupil and staff data is provided to the platform and how the service is used in teaching. School-specific onboarding or data protection terms may also apply.
If you use Coding Pathway through a school and have a question about your class membership, account access, or school records, please contact your school first.
Who helps us run the service
- Authentication is currently provided through Google and Microsoft sign-in where enabled.
- The platform is hosted on AWS-managed cloud infrastructure.
- Service emails may be delivered through configured email providers.
- Some teacher-facing content generation features may use OpenAI-backed services.
We do not list every school-specific term on this page. Further implementation details can be shared with schools during onboarding.
Cookies and sign-in
Coding Pathway uses essential cookies for secure sign-in and to remember simple preferences such as dashboard role. We do not currently use advertising cookies on the live product.
See the separate Cookies page for more detail.
How long we keep information
We aim to keep information only for as long as it is needed to run the service, support school use, and maintain operations.
For school-managed accounts, we generally expect data to be kept while the school relationship remains active. Where an account has been inactive for around three years, we may review it for deletion or anonymisation unless a school asks for a different retention period or we need to keep limited records for legal, security, or operational reasons.
Signed-in users can request account deletion through the account page. Some operational records and backups may remain for a limited period after account changes or deletion.
How we protect information
- School-scoped data boundaries and role-based access controls.
- Protected routes for signed-in areas of the service.
- Audit logging for core teacher and admin actions.
- Retention and access controls designed around school use.
Children and school users
Coding Pathway is designed for education use, including school-managed access by pupils. We expect schools and staff to decide how the service is used with their learners and to assess local safeguarding, privacy, and device policies.
We aim to keep the service focused on learning, progress visibility, and school use rather than advertising or unrelated profiling.
Questions or requests
If you want to ask about your information, request account deletion, or raise a privacy concern, contact schools@codingpathway.co.uk. If you use the platform through a school, the school may also need to be involved in handling your request.