Legal

Privacy policy

Last updated 15 September 2026 · Primary Coding League CIC, trading as Primary Coding Hubs

This policy explains what personal data we collect when you use this website (www.primarycodinghubs.co.uk) and the Curriculum Builder, why we collect it, and the choices you have. We keep it short and plain because we collect very little.

Who we are

Primary Coding Hubs is a service of Primary Coding League CIC, a Community Interest Company registered in England and Wales. We are the data controller for the data described here, registered with the Information Commissioner's Office under registration number ZC005345. You can contact us at community@primarycodinghubs.co.uk.

What we collect and why

Contact form and email

When you use the contact form we receive the name, email address, organisation and message you type. The form is delivered to our inbox by FormSubmit (formsubmit.co), which processes it on our behalf. We use it only to reply to you and to arrange the outreach, equipment loan or training you asked about. We keep contact messages for up to two years, then delete them.

Website hosting

The site is hosted on Cloudflare Pages. Cloudflare records standard server logs (IP address, browser type, pages requested, timestamps) to keep the service running and secure. We do not use analytics or advertising cookies, and we do not track you across other sites.

Curriculum Builder

The Curriculum Builder runs entirely in your browser. There is no account to create. The details you enter (school name, subject lead, class structure and unit choices) are saved only in your browser's local storage so you can come back to your plan; they are never sent to us. The documents in your pack are generated on your device.

When you download slide decks, worksheets or quizzes from Oak National Academy through the builder, your request passes through a small relay on our hosting so the file can be fetched and named for you. The request carries your licence code and school name so the relay can check the licence. The relay stores nothing; Cloudflare's standard server logs are the only record.

Booking an equipment loan

When you book a kit on the equipment page we ask for the school or group name, your name, email address and phone number, the delivery address and postcode, your dates and any notes. We need these to post the kit to you, to send tracking and the prepaid return label, and to get in touch about the loan. The booking is stored in a database on our Cloudflare hosting for as long as the loan is open and for two years afterwards, so we can deal with any follow-up about the kit, then deleted.

The delivery address, contact name, school name, phone number and email address are passed to Royal Mail to create the postage labels, and Royal Mail may email or text you tracking updates. If we use a label-printing service, the label (which carries the address) passes through it to our printer. The postage is paid through Stripe as described below; the booking reference is attached to the payment so we can match them up.

The availability shown on the equipment page is dates only. It never shows which school has a kit.

Paying for the full pack, or for loan postage

The Curriculum Builder full pack is a one-off payment per school, and equipment-loan postage is paid per booking, both taken by Stripe on a page Stripe hosts. Your card details go to Stripe only and never reach us. Stripe gives us the school name you type at checkout, the email address and name you pay with, your billing postcode, and the payment reference. We use these to issue your licence, to answer questions about the purchase, and to keep the accounting records the law requires. Stripe also uses your details on its own account to prevent fraud and meet its legal duties, as described in its privacy policy. Stripe stores its payment data in the EU and the United States under the UK International Data Transfer Addendum.

Your licence code is calculated from the payment reference and the school name; we do not keep a list of codes. The code and school name are saved in your browser's local storage so the builder stays unlocked, and appear in the footer of every document the pack produces. If you lose the code, "Lost your code?" sends the email address you paid with and the school name to Stripe to find the matching payment; nothing from that search is stored.

We keep payment records for six years after the end of the financial year in which you paid, because HMRC requires it. Everything else about your purchase is held by Stripe under its retention rules.

Lawful basis, in plain terms

Contact form: our legitimate interest in answering enquiries about our services.
Buying the full pack and issuing your licence: performing the contract you make with us when you pay.
Booking an equipment loan, posting the kit and taking the postage payment: performing the loan agreement you make with us when you book.
Payment records: our legal obligation to keep accounting records.
Server logs and security headers: our legitimate interest in keeping the site running, secure and free of abuse.
Google Forms feature: your consent, given on Google's permission screen, which you can withdraw at any time.

Who processes data for us

Cloudflare (hosting, the Oak relay, the licence functions and the equipment-loan bookings database): Cloudflare, Inc., with servers worldwide, under the UK International Data Transfer Addendum.
Royal Mail (postage labels and tracking for equipment loans): Royal Mail Group Ltd, in the UK.
PrintNode (if enabled, relays label PDFs to our printer): PrintNode Ltd.
Resend (if enabled, sends booking confirmation emails): Resend, Inc., in the United States under the UK International Data Transfer Addendum.
Stripe (payments): Stripe Payments Europe Ltd and Stripe, Inc.
FormSubmit (delivering contact form messages and loan-booking notices to our inbox).
Google (only if you use the Google Forms feature, and only between your browser and Google).

We do not sell personal data, and we do not share it with anyone else except where the law requires.

Google Forms feature and Google user data

In short: if you choose "Create quizzes in Google Forms", the Curriculum Builder asks your permission to create quizzes in your own Google Drive. It never sees, reads, stores or shares anything already in your Google account.

The Curriculum Builder can turn Oak National Academy starter and exit quizzes into Google Forms quizzes for you. This is optional. If you use it:

What we ask for. We request the Google Forms "create and edit forms" permission (the forms.body scope). We ask for no other Google permission.
What we do with it. Your browser creates new Google Forms in your Drive and fills them with the quiz questions, answers and points from the pack you built. The forms belong to you from the moment they are created.
What we do not do. We do not read, list, change or delete any existing forms or files in your account. We do not use Google user data for advertising, profiling, or training artificial-intelligence or machine-learning models, and we never sell it.
Where the data goes. Everything happens between your browser and Google. The access token Google issues is held in your browser's memory only for the sign-in session; it is not stored, and it is never sent to Primary Coding Hubs or to anyone else.
Sharing. We do not share Google user data with any third party, and we do not transfer it to our own servers.
Retention and deletion. Because we hold no Google user data, there is nothing for us to retain or delete. The quizzes stay in your Drive under your control. You can remove the builder's access at any time at myaccount.google.com/permissions.

Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

How we protect Google user data

The Google Forms permission is classed by Google as sensitive, so this section sets out exactly how that data is protected, even though our design means we never hold it.

Encryption in transit. Every request from the Curriculum Builder to Google (sign-in, creating a form, adding questions) is made over HTTPS (TLS 1.2 or later) directly from your browser to Google's servers. The website itself is served only over HTTPS, and Cloudflare redirects any insecure request to the secure address.
No storage at rest. Primary Coding Hubs has no server, database or file store that receives Google user data. The access token is kept in your browser's memory for the sign-in session only. It is never written to cookies, local storage, our hosting, our logs or any backup, so there is no copy for us to encrypt, lose or leak.
Least privilege. We request a single scope (forms.body) and use it for only two operations, forms.create and forms.batchUpdate, on a form the app has just created. Tokens are short-lived and are issued for that scope alone, and the app never requests offline access or refresh tokens.
Access controls. No member of our team can see Google user data, because it never reaches us. The Google Cloud project, the Cloudflare hosting account and the Stripe account are protected by two-step verification, and access is limited to the named staff who maintain the site.
Secure development. The Curriculum Builder is a static, open web application whose source is version-controlled. The document-generation libraries it uses are fixed versions served from our own site, the Google sign-in library is loaded directly from Google, and changes are reviewed and tested before release.
Incident response. If we ever became aware of a security incident affecting Google user data, we would notify affected users and Google without undue delay, and the Information Commissioner's Office within 72 hours where UK law requires it, and we would revoke the affected credentials.
Retention and deletion. We retain no Google user data. Your quizzes live in your Google Drive, where you can edit or delete them, and you can revoke the builder's access at any time at myaccount.google.com/permissions. Closing the browser tab discards the access token.

Cookies and local storage

The public website sets no cookies of its own, and there is no cookie banner because there is nothing to consent to. (The staff-only loans admin page sets one sign-in cookie for the member of staff using it.) The Curriculum Builder uses your browser's local storage for two things only: your plan, so you can come back to it, and your licence code, so the builder stays unlocked. Both are strictly necessary for the service you asked for, and neither is sent to us or used to track you. Clearing your browser data or pressing "Start again" removes your plan. Embedded Google sign-in uses Google's own cookies under Google's privacy policy, and Stripe's checkout page uses Stripe's.

How long we keep things

Contact form messages: up to two years.
Payment records: six years after the financial year of the purchase.
Equipment loan bookings (contact and delivery details): two years after the loan ends.
Licence codes: not stored by us; they live in your browser and can be recalculated from the payment.
Google user data and Curriculum Builder plans: never held by us.

Children

This website and the Curriculum Builder are for teachers, school leaders and adults who work with young people. We do not knowingly collect personal data from children. Our outreach work with children is covered by our safeguarding policy and the consent arrangements agreed with each school or group.

Your rights

Under UK data protection law you can ask us for a copy of the personal data we hold about you, ask us to correct or delete it, restrict or object to how we use it, or ask for it in a portable form. Email community@primarycodinghubs.co.uk and we will respond within one month, free of charge. We may need to keep payment records even if you ask us to delete other data, because the law requires us to. If you are unhappy with how we have handled your data you can complain to the Information Commissioner's Office at ico.org.uk, though we would welcome the chance to put things right first.

If something goes wrong

If we ever discover a breach affecting your personal data, we will tell the people affected and the Information Commissioner's Office without undue delay, and within 72 hours where the law requires it.

Changes to this policy

If we change how we handle data, we will update this page and the date at the top. Significant changes will be flagged on the Curriculum Builder itself.