Data processing agreement for schools
Last updated 12 November 2026
This is the agreement between a school and Striqr about the data in its pupils' school accounts. Your school is in charge of that data. We handle it for your school, and only as this agreement says.
This is version 2026-11. A school admin accepts it for the school on the school's Striqr page, before any pupil can join.
It's written to be read. Where the law has its own word for something, we say what it means.
1. Who this agreement is between
In short: Your school and Striqr LTD. It starts when a school admin accepts it.
Striqr ("we", "us") is Striqr LTD, a company registered in England and Wales (number 16317102), at 5th Floor, 167-169 Great Portland Street, London W1W 5PF, United Kingdom. We're on the Information Commissioner's register of fee payers, number ZC298218.
Your school ("you") is the school named on its Striqr page. If an academy trust, a local authority or another body is legally responsible for the school's data, this agreement is with that body, for that school.
It starts when one of your school admins accepts it on your school's Striqr page. We keep who accepted it, which version, and when. That person confirms they're allowed to accept it for the school.
School accounts are for schools in the United Kingdom.
It applies together with our Terms and our Privacy Policy. If they say something different about pupils' data, this agreement is the one that counts.
2. What the words mean
- School account: a Striqr account a pupil gets from your school, with a login card or by joining one of your classes.
- Pupils' data: personal data in, or about, your pupils' school accounts. The data, and what's done with it lists it.
- The law: the UK GDPR and the Data Protection Act 2018, and any law that changes or replaces them.
- Controller: whoever decides why and how personal data is used. For pupils' data, that's your school.
- Processor: whoever handles personal data for a controller, on its instructions. For pupils' data, that's Striqr.
- Breach: pupils' data being lost, destroyed or changed by mistake or unlawfully, or seen or taken by someone who shouldn't.
Your staff's own Striqr accounts are ordinary accounts. We're the controller of those, and our Privacy Policy covers them.
3. What we do with pupils' data
In short: Only what your school tells us to, and nothing for ourselves.
We handle pupils' data only on your school's written instructions. They are:
- this agreement;
- what your school chooses on its Striqr page, where Striqr gives it a choice;
- what your staff do on Striqr for their classes, such as making a login card, setting a lesson or removing a pupil;
- anything else a school admin asks of us in writing, at support@striqr.com, that we agree to do.
We use pupils' data only to give your school Striqr, to keep Striqr secure and working, and to meet the law.
We never use it for advertising or marketing, to build a profile of a pupil, or to train AI models. We never sell it, and we never hand it to anyone for their own use.
If we think an instruction breaks the law, we'll tell your school straight away. We may wait to follow it until that's settled.
If UK law makes us handle pupils' data in another way, we'll tell your school first, unless that law forbids us to.
4. The data, and what's done with it
In short: What this agreement covers: whose data, which data, what for and for how long.
| Question | Answer |
|---|---|
| What it's for | School accounts on striqr.com, so your pupils can learn to code: their classes, lessons and projects |
| What we do with it | Keep it, show it to the pupil and to your staff, run the pupil's code, back it up and delete it |
| Whose data it is | Your school's pupils |
| For how long | From the day your school accepts this agreement until its pupils' data is deleted, as When your school leaves says |
The kinds of data
- A username, and for a login card the name a teacher types.
- How the pupil signs in. With your school's Google or Microsoft account: the school email address and the account's ID, and for Microsoft the ID of your school's organisation. With a login card: a username and a code. We keep the code only as a scrambled hash.
- The school and the classes the pupil is in, and when they joined each.
- Projects and code the pupil makes. A school account's projects are always private.
- Lesson work: their guesses, answers and code, which checks passed, which hints they opened, and when they pressed I'm stuck.
- The record of how a pupil worked, where your school has turned its lesson record on: what they did in the lesson and when, and copies of their code as it changed.
- What Smart Bolt's AI told the pupil, where your school has turned AI hints on: the words of each answer, with the project and file it was about.
- Emails to us, if a pupil writes to our support address. A school account can't open a support ticket.
- Your school's choices: whether its lesson record and AI hints are on, who changed each and when, and which pupils the record was stopped for.
- Technical data: when the account was last active, and our server logs, which hold addresses (IP), browsers and the pages asked for.
We don't ask pupils for sensitive details such as their health, ethnicity or religion, and Striqr isn't the place for them. A pupil's own code and writing can hold anything, so please tell your pupils to keep personal details out of their work.
5. The people at Striqr
Only the people at Striqr who need pupils' data for their work can reach it. Each of them is bound to keep it confidential, and stays bound after they leave.
They look at a pupil's account or work only to give your school support, to fix a fault, to look into a report, or to keep Striqr secure.
6. Keeping it safe
In short: We protect pupils' data with the measures here, and never with less.
We take the security measures the law asks for (Article 32 of the UK GDPR), with the care children's data needs. Today they include:
- Every connection to Striqr is encrypted (HTTPS).
- A login card's code is kept only as a scrambled hash (bcrypt). We never see the password of a pupil's Google or Microsoft account.
- Our database is closed to everyone but our own servers and the few people at Striqr who look after it.
- Every page and every action checks, on our servers, that the person is one of your school's staff with the right role, or the pupil themself. Nobody at another school can see your classes or your pupils.
- A school account's projects are private. It can't publish, share or invite anyone, and it has no public profile.
- Google Analytics and Microsoft Clarity never load for a school account.
We look at these measures again at least once a year, and after any breach. We may change them as threats change, but never so that pupils' data is less safe.
7. Other companies that handle pupils' data
In short: The companies below help us run Striqr. We tell your school before adding one, and it can object.
Your school agrees that we may use the companies below to handle pupils' data. The law calls them "sub-processors". Each gets only what its job needs.
| Company | What it does | Where |
|---|---|---|
| Supabase | Our database: accounts, classes, lesson work and project details | Germany (Frankfurt). Supabase is a US company |
| Google Cloud | Runs striqr.com's web servers and keeps their logs | The EU: the servers and logs in Belgium. Google is a US company |
| Hetzner Online | Servers that run pupils' code | Germany and Finland |
| Cloudflare | Stores backups of project files, and runs our domain names | Western Europe for stored files, and a worldwide network. Cloudflare is a US company |
| DigitalOcean | Servers that route a project's preview to the pupil's browser | United States (New York) |
| Anthropic | The AI behind Smart Bolt's hints, only when your school has AI hints on and a pupil presses for one | United States |
| Google (Gmail) | Sends and stores our email, such as invites to your staff, messages between your school and us, and the note that a pupil reported an AI answer | US company |
Some companies in our Privacy Policy aren't here, because a school account never uses them: Stripe, Google Analytics, Microsoft Clarity and Discord.
Before another company handles pupils' data, we'll email your school admins at least 30 days ahead, saying what it will do and where. Your school can object in that time, for a reason to do with protecting pupils' data, and we'll try to settle it. If we can't, your school can stop using Striqr, and When your school leaves applies.
We have a written contract with each company that protects pupils' data as this agreement does. If one of them fails to, we answer to your school for it.
Not our sub-processors
- Your school's own sign-in. When pupils sign in with your school's Google or Microsoft accounts, Google or Microsoft acts for your school, under your school's agreement with it.
- Code libraries. The editor loads code libraries from cdnjs (Cloudflare), jsDelivr and code.jquery.com. The pupil's browser fetches them itself, so those services see its address (IP), and nothing about the pupil's account.
- What a pupil's code connects to. A program a pupil writes in the editor can connect to other websites and services, as any program can.
8. Data outside the UK
In short: What we keep is in the European Economic Area. A few things can go to the United States, each under a safeguard the law accepts.
Our database, our web servers and the servers that run pupils' code are in the European Economic Area. UK law treats it as protecting personal data adequately.
These can go to the United States:
- An AI hint. When your school has AI hints on and a pupil presses for one, Anthropic gets what the hint needs: the file they're working on, the error it gave, their last command, and their project's file list and set-up. Anthropic doesn't use it to train its models. Our Privacy Policy says more.
- A project's preview. The pupil's browser reaches their running project through DigitalOcean's servers in New York, which route it.
- Email between your school and us, which Google keeps.
- Code libraries, which the pupil's browser fetches from worldwide networks.
For each, we rely on a safeguard UK law accepts. Where the company is certified under it, that's the UK Extension to the EU-US Data Privacy Framework. Otherwise it's the UK's International Data Transfer Agreement, or its Addendum to the EU's standard contractual clauses.
We won't send pupils' data anywhere else outside the UK and the European Economic Area without telling your school first, as Other companies says.
9. Helping your school
In short: Requests about a pupil's data go to your school, and we help it answer.
Requests from pupils and parents. If a pupil, a parent or anyone else asks us about a pupil's data, we'll pass the request to your school within 5 working days, and tell the person that we have. We won't answer it ourselves unless your school asks us to.
Helping you answer. Your staff can see and change much of a pupil's data on Striqr. For the rest, a school admin emails support@striqr.com. We'll answer within 5 working days: to find, correct, copy or delete a pupil's data, or to stop using it.
Your school's own duties. We'll give your school what it needs from us for its data protection impact assessment, and help if it has to consult the Information Commissioner. A template with our part filled in is yours on request.
We'll also help your school keep pupils' data secure, and deal with a breach.
10. If something goes wrong
In short: We tell your school within 48 hours of finding a breach, and help it put things right.
If we find a breach of your pupils' data, we'll tell your school admins without delay, and within 48 hours of finding it.
We'll say what happened and when, which pupils and which data it touched as far as we know, what we've done about it, and who to talk to. If we don't know it all yet, we'll say what we know and follow up.
We'll help your school tell the Information Commissioner and the people affected, where the law asks it to. We won't tell them for your school unless it asks us to, or the law makes us.
We'll find the cause, fix it, and tell your school what we changed.
11. Checking on us
We'll give your school the information it reasonably needs to see that we keep to this agreement and to Article 28 of the UK GDPR. That includes answering its questions about security.
Your school, or an auditor it appoints, may inspect how we handle pupils' data once a year. It gives us 30 days' written notice, comes in working hours, and keeps what it sees confidential. After a breach, or if the Information Commissioner asks, it may come sooner. Each of us pays our own costs.
12. When your school leaves
In short: We delete your pupils' accounts and work 90 days after your school leaves. You can have a copy first.
Your school can stop using Striqr at any time, by telling us at support@striqr.com.
A copy first. If your school asks before the data is deleted, we'll send it a copy of its pupils' work.
Then it's deleted. We delete your pupils' accounts and their work 90 days after your school leaves, or sooner if a school admin asks.
A pupil who leaves your school. A school admin tells us, and we delete that pupil's account within 30 days.
The record of how a pupil worked, where it's kept: the copies of their code for 120 days, and the list of what they did for 400 days. Both go sooner if the account is deleted, or if your school turns the record off or stops it for the pupil.
What Smart Bolt's AI told a pupil, where it's kept: 120 days. It goes sooner if the account is deleted.
Backups and logs. A copy can stay in a backup for a short time after the original is deleted, until the backup is replaced. Until then, a backup is used only to put Striqr right after a fault. Server logs are kept about 30 days.
If your school asks, we'll confirm in writing that it's done. If UK law makes us keep something longer, we'll say what and why, and we won't use it for anything else.
13. Changes to this agreement
This is version 2026-11. We may need to change it, for example when the law changes or Striqr does.
We'll email your school admins at least 30 days before a change takes effect, saying what's changing. A change the law needs sooner takes effect when the law says.
If your school doesn't want the new version, it can leave before the change takes effect. If it keeps using Striqr after that day, it accepts the new version.
14. The rest
Each side's part. Your school is responsible for having a lawful reason to give its pupils school accounts, for telling pupils and parents how it uses Striqr, and for the instructions it gives us. We're responsible for keeping to this agreement, and to a processor's duties under the law.
What each of us owes. Nothing in this agreement limits what either of us owes a pupil, or anyone else, under data protection law. Between your school and Striqr, the limits in our Terms apply.
Law. The law of England and Wales governs this agreement, and the courts of England and Wales may hear disputes about it.
Contact. support@striqr.com, 08:00 to 16:00 on school days.