Privacy Policy
Last updated 15 November 2026
This policy explains what personal data Striqr LTD collects when you use striqr.com, the Striqr editor, lessons, projects hosted through Striqr, Striqr AI and the Striqr app on Discord. It says why we use the data, who we share it with, how long we keep it, and what rights you have.
Personal data means information about you as a person, such as your email address, username, Discord ID or IP address. Your code and your questions count too when they can be linked to you.
The websites and apps that other people build and host on Striqr belong to them, not us. This policy doesn't cover them (see Data in your projects).
1. Who we are
Striqr LTD runs Striqr. We're a private limited company registered in England and Wales (company number 16317102), with our registered office at 5th Floor, 167-169 Great Portland Street, London W1W 5PF, United Kingdom.
We are the "controller" of the personal data this policy describes: we decide why and how it's used, and we're responsible for it. That's under the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018. For people in the European Economic Area, the EU GDPR applies too.
School accounts are the exception. There, the school is the controller of its pupils' data, and we handle it for the school: see School accounts and lessons.
We're registered with the Information Commissioner's Office (ICO) as a data controller. Our registration number is ZC298218.
For anything about your data or this policy, email support@striqr.com with the subject "Privacy", or write to us at our registered office.
2. What we collect
In short: Mostly what you give us: your account, your projects and your questions. A little is collected automatically, like your IP address and, if you allow it, analytics.
Your account
When you sign up, we collect your username and email address, and your password if you set one. We store passwords only as a scrambled hash (bcrypt), never as you typed them. We also keep your sign-in method, whether your email is verified, your language, and when you were last active on the site and in the editor, and in which project.
If you sign in with Google, GitHub, X, Discord or Microsoft
- Google, including Google's one-tap prompt: your Google account ID and email address. We don't store your name or picture.
- GitHub: your GitHub user ID, your email address and an access token. GitHub asks you to let Striqr read and write your public and private repositories. We use that access only when you import, link, compare or push a project, and we store the token encrypted. Disconnecting GitHub in Striqr cancels the token.
- X: your X account ID, and your email address if X shares it.
- Discord: your Discord user ID and username, and your email address if Discord has verified it. Linking Discord to your account for the Striqr app stores your Discord user ID and username and when you linked them. Signing in to the Striqr app's server settings page (striqr.com/discord/servers) reads your Discord user ID, name and the servers you're in, with whether you can manage each. We keep those with your session for 12 hours at most, and never store them anywhere else.
- Microsoft, with a personal, work or school account: your Microsoft account ID and the ID of the organisation a work or school account belongs to. We store your email address only when you sign up with Microsoft, and only if Microsoft has verified it. We don't store your name.
While you finish signing up with one of these, we hold the details it sent us for up to 30 minutes.
Your projects and code
We keep everything you put in a project: its files and code, name, description and cover picture, and whether it's public, private or shared by link. We also keep the people you invited, your custom domain, and the GitHub repository it's linked to. Projects run on our servers, and their files are backed up for as long as the project exists. When someone copies a project, we record which project was copied, by whom (their username, or a random guest ID) and when.
While your code runs, we also handle what it does: its output, the terminal, and the ports it uses. That's needed to show you the results. Apart from your files, none of it is kept after the project stops.
Lessons
When you do a lesson, we keep your work in it: your guess, your answers, your code, which checks passed and which hints you opened. Code you run in a lesson goes to our runner. The code is dropped when the run ends, and what it printed is held for up to 10 minutes. In a school's class, a lesson keeps more: see School accounts and lessons.
Using Striqr without an account
You can try Striqr without signing up. Your browser gets a random guest ID in a cookie, so the project you start stays yours. A guest project is deleted about 5 minutes after everyone has left its editor, unless you sign up and keep it. Code you paste on the home page is held for up to 6 hours while your project starts.
Striqr AI
We collect what you send to Striqr AI and what it sends back. Striqr AI explains what that includes.
Purchases
When you buy Boost or AI credits, Stripe handles the payment. We receive and keep what we need to give you what you paid for: your plan and its Stripe subscription ID, purchase dates, whether it renews and your AI credit balance. We never see or store your full card number.
Support and messages
We keep your support tickets (your username, and what you and our team wrote) and emails you send us.
If you report something with the Report button or the report form, we get your reason and details. We also get your email address if you give it, and your username if you're signed in. It reaches us as an email, and we keep it nowhere else.
Job applications
If you apply for a job, we collect what you send us: your name, email address, phone number (if you give it), links, cover letter and CV. Your application is emailed to our team and kept for up to 12 months.
Technical data
Like most websites, our servers receive your IP address and details of your browser and device with each request. We use IP addresses briefly to limit abuse, for example how many copies one network can make in an hour. Our hosting provider also records requests and errors in server logs. When your password changes, or Microsoft is added to or removed from your account, we email you. That email names the browser and IP address the change came from, so you can spot one you didn't make. If you consent, analytics tools collect more: see Cookies and analytics.
From other people
Other people may give us data about you. For example: a collaborator invites you to a project by username, a teacher sets a challenge you try, or someone uses the Striqr app on a Discord message you wrote. The Striqr app on Discord explains what the app collects in Discord.
3. Striqr AI
In short: Striqr AI runs on Anthropic's Claude models. What it needs to answer goes to Anthropic, which doesn't use it to train its models.
Striqr AI is our name for the features that use AI. In the editor, those are the AI assistant and Smart Bolt's AI fixes. In the Striqr app on Discord, they are explaining errors, fixing code, hints, Explain this step, /make and reading pictures of code. Everything they produce is made by AI.
These features use AI models made by Anthropic PBC, called Claude. To answer you, we send Anthropic what your request needs:
- The editor's AI assistant: your message and any pictures you add, and the conversation so far. It also gets your project's file list and settings file, and the files the AI opens or needs, which can be their full contents. It also gets the output of the commands it runs, and details of how your project is set up: its Docker image, open ports, plan, custom domain and linked GitHub repository. The assistant can change files and run commands in your project.
- Smart Bolt: when you press its AI fix, the file and error output it needs, your project's file list and set-up, and your language. Without an account you get a few free fixes. We count them by your guest ID for a year, and by a scrambled form of your IP address for up to 2 days, to stop misuse. If you joined a class link, its owner's AI credits pay for your fixes, and they see how many fixes their link gave each day for 60 days, but not who asked.
- The Striqr app on Discord: your code, its error and output, and your question. Also the other words in the message you used the app on, and any pictures of code you send. In a server using learning mode, it also sends the teacher's notes about the class, and the titles and tasks of open challenges.
We don't send Anthropic your email address, password or Discord ID. Names that are part of your code or project can be included, such as a GitHub repository's owner.
No training. We don't use your code, questions or answers to train AI models. Anthropic's commercial terms don't allow it to train its models on what we send through its API. Anthropic deletes what we send within 30 days. The exception is a request flagged as breaking its usage policy, which it can keep for up to 2 years. Anthropic's privacy policy explains this.
Where answers are kept. In the editor, your conversation stays in our server's memory for up to 6 hours after you last use it. Your browser keeps the last 40 messages until you close the tab. In Discord, answers are kept for 7 days so their buttons keep working (see The Striqr app on Discord). For the editor, we record how many AI credits each request used, to charge your balance.
Accuracy. AI can be wrong, so check its answers and test its code before you rely on them. Striqr AI doesn't make decisions about you that have legal or similarly significant effects.
4. The Striqr app on Discord
In short: The app reads only the messages you point it at, and keeps your recent code for 7 days so its buttons work. Delete my data deletes what it keeps.
When you use the Striqr app, Discord sends it the interaction. That includes your Discord user ID, username and display name, and your language setting. It also includes the server and channel, your roles and permissions there (to apply the server's rules), and any Striqr purchases you've made through Discord.
When you add the Striqr app to a server, Discord tells us your Discord user ID and the server's ID. We keep them for 7 days, to send you one welcome message in Discord, then delete them.
When you publish a project with Show it in my Discord servers ticked, we keep your Discord user ID (from your account's Discord link), the project's name and when, for 7 days. The app posts the project in the showcase channel of each server you're in that has one, then keeps which servers it went to.
Which messages it reads
- Messages that mention @Striqr, and messages you send it directly, with their files and pictures.
- A message you use one of its Apps commands on (Share, Run, Explain or Fix). That can be someone else's message. The app reads its code, files and links, and for Explain and Fix the rest of its words. The card it posts credits the message's author by name.
- Forwarded messages, credited as "forwarded" without a name, and the message an @Striqr message replies to.
- In a help thread Striqr opened, it notes who replied (their ID and display name), not what they wrote.
The app doesn't use Discord's Message Content access. Discord shows it a message's words only when the message mentions it, is sent to it directly, or is picked with one of its commands.
What it keeps, and for how long
| What | How long |
|---|---|
| Your last code: the last 5 pieces of code you sent it, with what you typed in its forms (keys and tokens replaced) | 7 days, or until you press Forget my code |
| Results behind a card's buttons: a run's code, input and output, and Striqr AI's answers | 7 days |
| The code behind a share card, with who shared it and who wrote it | 30 days |
| Cards posted in servers: where, by whom, and whose code | 90 days in our records. The card stays in Discord until someone removes it |
| Projects you chose to show in your servers: which server, which project, and your Discord ID, so each goes there once | 30 days |
| What you made with /make: the last 5 versions, with your request | 7 days |
| Your settings, and the one-time tips you've seen | Until you delete them |
| Challenge tries: your score, language, the kind of error, and the hints you opened, never your code | While the challenge is open, then 90 days |
| Help requests: who asked, who helped (their ID and display name), and whether it was solved | 30 days |
| Your daily usage counts, for daily limits | 7 days |
| Top-ups: your balance, and each purchase's record | Balances until used. Purchase records 400 days, kept without your ID if you delete your data |
| Practice spaces (test grounds) made for you | Until the thread is deleted |
| Blocks set by a server's admins, with their reason | Until they end or are lifted |
| A server's settings, tags and challenges | Until changed, or 30 days after Striqr leaves the server |
| Held only in memory: pictures a program drew, files it saved, pictures of code it read, Step through, tool results, and a message that mentioned @Striqr (to follow its edits) | 15 minutes to 2 days, and lost whenever the app restarts |
| Counts that don't say who: which Discord languages people use, how often buttons are pressed, runs per server | 400 days |
| Logs, which can include your Discord ID | A fixed amount of space, with older lines deleted as new ones are written |
What it sends to striqr.com
To run or share code, the app sends it to striqr.com with your Discord user ID, the server's ID, your plan and a title. A default title can include your display name or the code author's, for example "Margaret's Python code". striqr.com keeps a run's code, input and output in memory for 10 minutes.
A share makes a link that anyone who has it can open, run and copy, unless the server chose view-only links. A link nobody opens is deleted after 30 days. An opened one is deleted 30 days after it was last opened, unless you keep it in your striqr.com account. Its preview in Discord can show the first lines of the code, and striqr.com keeps up to 1,500 characters of the code as that preview for as long as the link exists.
The app also sends your Discord ID to striqr.com to check whether you've linked an account, and what plan you have.
When your striqr.com AI credits pay for an answer in the app, striqr.com keeps a record of it: your account, the model, and the credits held and charged. It never keeps the code, the question or the answer with it. Records are kept 400 days.
When you post a code link from GitHub, GitLab, Bitbucket, Pastebin, Python Discord's paste site or Compiler Explorer, the app reads the code from that site. The site sees only that our server asked for the page.
What other people in a server can see
- Anyone who can see a channel can see the cards posted in it: the code, its output, and who posted it or wrote the code.
- A help card shows the asker's name, their code near the error, the error and their question. Helpers' names show on it for a short time.
- A challenge's author and the server's managers can see each member's tries, scores and hints, and download them with names and Discord IDs. The challenge card can also show who solved it, if its author chooses.
- Teachers can turn on a weekly summary in the server's admin log. It names members who may need help with a challenge, and members waiting for help.
- Server admins see their server's stats, including who shares most, and an admin log of what admins did.
Purchases in Discord
When you buy a plan, top-ups or the class plan in Discord, you pay Discord, under Discord's terms. Discord tells us what you bought; we never see your payment details.
Deleting it
/settings → Delete my data asks you to confirm. It then deletes your settings and the code kept for you, and your private run results and private Striqr AI answers. It also deletes what you made with /make, your challenge tries and hints, your help requests, your top-up balances (it warns you first), and your usage history before today. Forget my code deletes just your kept code. Remove on a card takes it down and deletes its code and link.
Delete my data doesn't delete some things. Cards you posted in servers stay until you use Remove on them; My cards in /settings lists your recent ones. If someone else posted your code, you can remove that card with Remove too. Results posted for everyone, and the code behind share links you made, are deleted after 7 and 30 days. Remove deletes a card's code at once. Today's usage counts stay, so daily limits still work. Records a server's admins keep, such as blocks, stay too. So do purchase records (without your ID), copies in backups (up to 60 days), and your striqr.com account. To have any of those deleted sooner, email support@striqr.com.
5. School accounts and lessons
In short: A school can set up accounts for its pupils. The school decides how their data is used, and we handle it for the school.
A school can set up Striqr accounts for its pupils, including pupils under 13. A pupil gets one from a login card their teacher makes, or by joining a class with their school's Google or Microsoft account. A pupil who signs up from their class's join link gets a school account straight away. One who already had a Striqr account of their own keeps it as it was until they press Join. This section is about school accounts. A teacher's own account is an ordinary Striqr account, and the rest of this policy covers it.
Who's in charge of the data
For a school account, the school (or its academy trust) is the "controller": it decides why and how its pupils' data is used. We're its "processor". We handle the data only as our data processing agreement with the school says. We use pupils' data only to give the school Striqr, to keep Striqr secure and to meet the law. We never use it for advertising, profiling, product research or training AI.
The school tells its pupils and their parents how it uses Striqr, in its own privacy notice.
What a school account keeps
- A username, and for a login card a name. A teacher types the pupil's name for a login card, and the username is made from their first name. A pupil who joins with the school's Google or Microsoft account picks a username. Striqr offers one made from the first word of their name and four digits, never their whole name or their email address. We keep no other copy of their name.
- How the pupil signs in. With the school's Google or Microsoft account: the school email address and the account's ID, and for Microsoft the ID of the school's organisation. With a login card: a username and a code. We store the code only as a scrambled hash (bcrypt), and never ask for an email address.
- The school and the classes the pupil is in, and when they joined each.
- Projects and code, as for any account. A school account's projects are always private.
- Lesson work: the guess, the answers, the code, which checks passed and which hints were opened. When a pupil presses I'm stuck, their teacher sees it until the pupil is helped or takes it back, passes the step, or an hour goes by. The time of the last press, and a count of presses, stay with the lesson work.
- Emails to us, if a pupil writes to support@striqr.com. A school account can't open a support ticket.
- What Smart Bolt's AI told the pupil, where their school has AI hints on: the words of each answer, with the project and file it was about.
- The 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, as for any account: when it was last active, and the server logs that What we collect describes.
What a school account can't do
A school account's projects can't be made public or shared, and nobody can be invited to them. It has no Discover, no AI assistant, no payments, and no link to Discord or GitHub. Google Analytics and Microsoft Clarity never load for a school account, whatever is pressed in the cookie banner. A pupil can still open a public project if someone gives them its link, and make a private copy of it. A school account can't open a support ticket, and no password-reset email is sent for one. Once its school stops using Striqr, the account closes: it can no longer be used.
Smart Bolt's AI is off for a school's pupils until the school turns it on. Turned on, it never writes or corrects a school account's code. It gives hints, and it can suggest the command that starts a project. When a pupil presses it, this goes to Anthropic, as Striqr AI describes: the file, the program's last output with its errors, the last command, and the project's file list and set-up. Lessons themselves use no AI.
What the AI says back is kept for 120 days, for the class's teacher and the school's admins to read. A pupil can report an answer. It's then marked for their teacher, and we're sent what the AI said and which school, without the pupil's name.
What teachers see
A class's teacher, and the school's admins, see the class's pupils: their usernames, the names typed for login cards, and the school email address of a pupil who signs in with one. For each lesson set for the class, they see where each pupil is, their guess, their check-in answers, how many tries and hints each step took, and who pressed I'm stuck. They can download this as a spreadsheet. They also see what Smart Bolt's AI told each pupil. They can't open a pupil's projects.
The school's admins also see a list of every pupil account the school has, and who is on its staff. They can take a member of staff off, who then sees none of this.
The record of how a pupil worked
A school's lesson record is off until the school turns it on. While a lesson's page says Your working is saved for you and your teacher, Striqr keeps a record of how the pupil worked through the lesson. It's kept for every lesson a pupil in the school's classes does, at school or at home, whether or not a class set it. A teacher sees it for the lessons set for their class. With the step and the time, it keeps:
- when the pupil opened each step, and when they finished it;
- each run, and how it ended: it ran, stopped with an error, waited for input, took too long or reached a limit;
- each check, and how many checks passed;
- which hints they opened, and whether they answered each question right the first time;
- when they saved their guess, and when they pressed Start again;
- each paste into the code or the guess: its size only, never its text;
- a copy of their code at each run and check, and at most every 30 seconds while they type.
It never keeps each key press or its timing, mouse movements, other tabs or apps, or anything from a camera, microphone or screen.
The class's teacher, or one of the school's admins, can stop the record for one pupil. Turning the record off, for the school or for one pupil, deletes what was recorded. The pupil's code in each lesson stays: it's their work.
The class's teacher and the school's admins see the record on the lesson's progress page, in its live view during the lesson, and as a replay of one pupil's work. These show what happened as facts. They give no mark for effort, and no verdict on the pupil. A short note can appear beside a pupil: stuck (three failed checks or more on a step), opening hints quickly, or idle. A teacher decides what to do about it, and nothing is decided automatically. Each replay a teacher opens is written to our server log, which is kept about 30 days. A pupil can see their own record from My working, while they're in a class and can open the lesson.
How long a school account's data is kept
- The account and its work: while the school uses Striqr. When a school stops, its pupils' accounts close at once: they can no longer be used. We delete the accounts and their work 90 days later. A person at Striqr does the deleting: it isn't automatic yet. Before then, the school can ask us for a copy.
- A pupil who leaves the school: the school tells us, and we delete their account within 30 days. Until we're told, the account stays.
- The record of how a pupil worked: the copies of code for 120 days, about a school term. The list of what they did for 400 days, a little over a year. Both go sooner if the account is deleted, or if the school turns the record off or stops it for the pupil. The pupil's latest code in a lesson is part of their lesson work, and stays with the account.
- What Smart Bolt's AI told a pupil: 120 days. Sooner if the account is deleted.
Which companies handle it
The companies in Who we share it with handle a school account's data too, apart from those a school account never uses: Stripe, Google Analytics, Microsoft Clarity, Discord and GitHub. Anthropic gets a pupil's code only when their school has AI hints on and the pupil presses for one. We tell a school before another company starts handling its pupils' data, and the school can object.
Rights over a school account's data
A pupil, or their parent or guardian, should ask the school first. The school is the controller and knows who they are, and we help it answer. If you write to us instead, at support@striqr.com, we'll pass your request to the school and tell you that we have.
6. What other people can see
- Your username, on your projects and in links to them, and in the editor when you're in a project with others.
- Public projects: anyone can open them and see all their files, run them and make their own copy. Discover and the Striqr app's Explore list them, with their name, description, picture, framework and your username. They can appear in search engines. Web crawlers can read them too, including crawlers that collect data to train AI.
- Projects shared by link: anyone who has the link can open, run and copy them, and edit them if the project allows it. This covers all links made in Discord and every project started without an account.
- Private projects: only you and the people you invite can open their code in the editor. A private project's site has a secret striqr.me address, which we show only to you and them. Its usual address only says the project is private. Anyone you give the secret address to can visit the site and start it. Renaming the project gives it a new secret address, and the old one stops working.
- Collaborators you invite can see and change the project, and see who else is in it.
- Live sites of public projects and projects shared by link are public websites while they run. A site on your own domain is public while it runs, even a private project's.
- Link previews: when a link to a project is posted somewhere else, the preview shows the project's name, owner and picture. For a public project it shows the description too.
A copy of a project includes all its files, even hidden ones such as .env. Never keep passwords, API keys or tokens in a project other people can open.
7. How we use it, and why we're allowed to
Data protection law requires a legal reason, called a "lawful basis", for each use of personal data. These are ours:
| What we do | Lawful basis |
|---|---|
| Create and run your account. Store, run, host and back up your projects. Give you Striqr AI and the Striqr app's features when you use them | Contract: it's needed to give you the Service you asked for |
| Take payments, give you what you paid for, and keep financial records | Contract, and legal obligation for tax and accounting records |
| Send account emails: verifying your address, and resetting or changing your password | Contract |
| Answer support tickets and requests about your rights | Contract, or legal obligation for rights requests |
| Keep Striqr secure and working: limits, logs, stopping abuse and fixing problems | Legitimate interests: keeping the Service and its users safe |
| Read messages someone uses the Striqr app on, and show challenge results and help requests to a server's teachers and admins | Legitimate interests: making the features a server and its members chose work |
| Count how the Striqr app's buttons and languages are used, without saying who | Legitimate interests: improving Striqr |
| Give a school's pupils their accounts and lessons, and show their work to their teachers | We do this for the school, which is the controller. The school chooses the lawful basis: usually its public task of teaching |
| Analytics with Google Analytics and Microsoft Clarity | Consent: only if you allow analytics cookies. You can change your mind at any time |
| Show Google's one-tap sign-in to visitors who aren't signed in | Consent: only if you allow preference cookies. You can change your mind at any time |
| Consider job applications | Legitimate interests, and steps before a possible contract with you |
| Meet legal duties, enforce our Terms, handle reports and legal claims | Legal obligation and legitimate interests |
Where we rely on legitimate interests, we've weighed them against your rights. You can object to these uses (see Your rights).
We don't sell your personal data, and we don't use it for advertising. We don't make decisions about you based only on automated processing that have legal or similarly significant effects on you.
8. Who we share it with
We share data with companies that help us run Striqr, called "processors". Each gets only what its job needs, and only as this policy says:
| Company | What it does for us | Where |
|---|---|---|
| Supabase | Our database: accounts, project details, teams, support tickets, school classes and lesson work | Germany (Frankfurt). Supabase is a US company |
| Google Cloud | Runs striqr.com's web servers, keeps their logs, and stores backups of the Striqr app's database | The EU: the servers and logs in Belgium. Google is a US company |
| Hetzner Online | Servers that run your projects' code, code run in lessons, and the Striqr app on Discord | Germany and Finland |
| DigitalOcean | Servers that route visits to live sites on striqr.me | United States (New York) |
| Cloudflare | Stores backups of your project files and blog pictures, runs our domain names, and serves code libraries (cdnjs) | Western Europe for stored files, and a worldwide network. Cloudflare is a US company |
| Anthropic | The AI models behind Striqr AI | United States |
| Stripe | Payments and subscriptions. Stripe also uses payment data to prevent fraud, as a controller, under its privacy policy | United States and Ireland |
| Google (Gmail) | Sends and stores our email, including job applications | US company |
| Google Analytics and Microsoft Clarity | Analytics, only with your consent | United States |
| Discord | The platform the Striqr app runs on, sign-in with Discord, and purchases in Discord | United States |
Services you choose to use. Some companies get data because you choose to use them, and handle it under their own privacy policies: Google, GitHub, X, Discord and Microsoft when you sign in with them or connect them, and the websites and services your own code connects to.
Fonts and code libraries. Our fonts come from our own servers, so Google Fonts gets nothing. The editor, the code box on the home page and the pages you see once signed in load code libraries from cdnjs (Cloudflare), jsDelivr and code.jquery.com. Your browser fetches these files directly, so those services receive your IP address and browser details.
Docker Hub and code links. When you search for a Docker image, our server sends your search words to Docker Hub. When the Striqr app reads a code link, our server fetches that page. Neither request includes your personal details.
When the law or safety requires it. We may share data to follow the law, a court order or a valid request from the authorities. We may also share it to protect people's safety, our users or Striqr, for example by reporting child sexual abuse material. We may share it with professional advisers such as lawyers and accountants. If Striqr is sold or reorganised, data passes to the new owner under this policy, and we'll tell you before it's used in a different way.
9. International transfers
Striqr LTD is in the UK. Some of the companies above are in the European Economic Area, and some are in the United States. The UK recognises the EEA as protecting personal data adequately.
For the United States, we rely on the UK Extension to the EU-US Data Privacy Framework where the company is certified under it. Otherwise we rely on the UK's International Data Transfer Agreement, or its Addendum to the EU's standard contractual clauses. Data from the EEA is protected the same way under the EU GDPR. Email us for details.
10. How long we keep it
| Data | How long |
|---|---|
| Your account | Until you ask us to delete it. We delete it within 30 days of your request |
| Your projects, their backups, and records of who copied them | Until you ask us to delete them, or we delete your account |
| Guest projects, started without an account | About 5 minutes after everyone leaves the editor, unless you keep it |
| Code pasted on the home page | Up to 6 hours |
| Your work in lessons | Until you ask us to delete it, or we delete your account |
| What code run in a lesson printed | 10 minutes, in memory. The code goes when the run ends |
| School accounts and their work | While the school uses Striqr, then 90 days. Sooner if the school asks |
| The record of how a pupil worked in a lesson | The copies of code 120 days, and the list of what they did 400 days |
| What Smart Bolt's AI told a school's pupil | 120 days |
| Links made in the Striqr app | 30 days if nobody opens them. Otherwise, 30 days after they were last opened. If you keep one in your account, until it's deleted |
| Code run from the Striqr app | 10 minutes, in memory |
| The editor's AI conversations | 6 hours after you last use them on our server, and until you close the tab in your browser |
| Being signed in | Up to 1 year, or until you sign out. If you untick Remember me when you sign in with your password: until you close your browser |
| Unfinished sign-ups | 30 minutes |
| Support tickets | As long as your account exists |
| Purchase records | 6 years after the purchase, as UK tax law requires |
| Job applications | Up to 12 months |
| Server logs | About 30 days |
| Analytics, with consent | Google Analytics up to 14 months. Clarity's recordings 30 days, and its other data up to 13 months |
The Striqr app on Discord lists how long the app keeps its data. Copies can stay in backups for a short time after the original is deleted, until the backup is replaced. We keep data longer only when the law requires it, or to deal with a legal claim or a serious breach of our Terms.
11. Your rights
Under UK and EU data protection law, you have the right to:
- see your personal data and get a copy of it;
- correct it if it's wrong or incomplete;
- delete it (the "right to be forgotten");
- restrict how we use it, for example while we check a complaint;
- object to uses based on our legitimate interests;
- take it with you: get the data you gave us in a machine-readable form, or have it sent to another company;
- withdraw consent at any time, where we rely on it. For analytics, use Cookie settings at the bottom of any page;
- complain to a data protection regulator (see Contact us and complaints).
Some rights have limits. For example, we must keep purchase records for tax purposes, even if you ask us to delete them.
How to ask. Email support@striqr.com from the address on your account, with the subject "Privacy". For the Striqr app, include your Discord username. We may ask you to prove who you are. We'll reply within one month, or tell you if a complex request needs up to two more months. It's free, unless a request is clearly unfounded or excessive. A parent or guardian can ask for a child. For a school account, ask the school first: see School accounts and lessons.
If you live in the United States
Depending on your state (for example California, Colorado, Connecticut, Virginia or Texas), you may have the right to know what personal information we collect, and how we use and share it. You may also have the right to get a copy, and to correct or delete it. We give these rights to everyone, wherever they live. You can ask through an authorised agent, and we won't treat you differently for using your rights.
We collect the kinds of personal information this policy describes:
- identifiers, such as your username, email address, IP address and account IDs;
- commercial information, such as your purchases;
- internet activity, through analytics and only with your consent;
- professional information, from job applications.
We don't sell personal information, or share it for cross-context behavioural advertising. We use sensitive personal information, such as your password, only to provide the Service. We don't use personal data to train large language models.
Appeals. If we turn down a request, you can appeal by replying to our answer. We'll reply to your appeal within 60 days. If you're still unhappy, you can contact your state's attorney general.
Do Not Track and Global Privacy Control. Our website doesn't respond to Do Not Track signals. We don't sell or share personal information for advertising, so there's nothing for Global Privacy Control to opt you out of. Analytics run only if you allow them in the cookie banner.
12. Deleting your account and data
striqr.com: there's no delete button yet. To close your account and delete your data, email support@striqr.com from the address on your account. We'll confirm it's you. Within 30 days, we'll delete your account, your projects and their backups, your support tickets and your Discord link, and tell you when it's done. We cancel any subscription you still have. We keep only what the law requires, such as purchase records. Copies other people made of your public projects stay theirs.
School accounts: ask the school, or email us. We delete a pupil's account within 30 days of their school asking, and every pupil's account 90 days after their school stops using Striqr.
Discord: use /settings → Delete my data, as The Striqr app on Discord describes.
Connected accounts: unlinking Discord in Settings removes the link. Disconnecting GitHub cancels Striqr's token.
13. Cookies and analytics
We use cookies and similar browser storage to keep you signed in and remember your choices. If you agree, we also use them for analytics, and Google uses them for its sign-in prompt. Our Cookie Policy lists each one.
Google Analytics and Microsoft Clarity run only if you choose Accept all, or turn on Analytics, in the cookie banner. They collect which pages you visit, clicks and scrolling, your device and browser, and your approximate location from your IP address. Clarity can record how you move around a page, but it never records the text in the editor, so your code, terminal and AI chats aren't captured. Google and Microsoft may recognise your browser on other websites that use their services. To change your choice, use Cookie settings at the bottom of any page.
Google's one-tap sign-in appears only if you allow preference cookies in the cookie banner, and aren't signed in. Its script comes from Google, which can then see that you visited and whether you're signed in to Google. It sets a cookie that remembers if you closed the prompt. The Continue with Google button loads nothing from Google until you press it, so it works without that consent.
14. Children and schools
Striqr is for people aged 13 and over, unless their school set up their account. Under 18, you need a parent's or guardian's permission, or a school account. Outside school accounts, we don't knowingly collect data from children under 13. If you believe a child under 13 is using Striqr without a school account, email support@striqr.com and we'll delete their account and data.
School accounts. A school can set up accounts for its pupils, including pupils under 13. Then the school decides how its pupils' data is used, and we handle it for the school. A school account keeps its projects private, never loads analytics, and has no AI assistant. School accounts and lessons says what it keeps, who sees it and for how long.
We build Striqr with young people in mind. New projects in an account are private until you share or publish them. Analytics stay off unless you choose them, and we show no ads and sell no data.
Striqr AI and young people. Striqr AI follows extra safety rules written for young people, on striqr.com and in Discord. It keeps what it writes suitable for teenagers, never asks for personal details, and refuses code meant to harm or trick people. It never pretends to be a person. If someone seems to be at risk, it tells them to talk to a trusted adult.
Parents and guardians. You can ask to see or delete your child's data, or to close their account. Email support@striqr.com with the subject "Privacy", and tell us their username, or their Discord username for the Striqr app. We'll check that you're their parent or guardian first. If your child has a school account, ask their school first.
The law. We follow the children's privacy laws that apply to Striqr. These include the UK GDPR, the EU GDPR and, in the US, the Children's Online Privacy Protection Act (COPPA). Outside school accounts, Striqr isn't for children under 13, so we don't knowingly collect their data. School accounts are for schools in the United Kingdom, under UK law. Where a country's law sets a higher age for using online services without a parent's consent, our Terms ask for a parent's or guardian's permission.
Schools and teachers in Discord. When a school or teacher uses Striqr with students in Discord, for example Class mode and challenges in a server, teachers and the server's managers see students' challenge results, hints and help requests. The Striqr app on Discord describes this. Schools should tell students and parents how they use Striqr, and get any consent their rules require. We use students' data only to provide Striqr, never for advertising or profiling, and we delete it when a school asks. A school that needs a data processing agreement can email us.
15. How we protect your data
We use encrypted (HTTPS) connections, and store passwords only as bcrypt hashes. GitHub tokens are encrypted. Access to our database is limited to our own servers and the staff who need it. Code run from the Striqr app runs in locked-down containers with no network access. The app replaces keys and tokens in the code it keeps for you, and warns before one would be posted for everyone.
Only Striqr staff who need it can see your account details. They look at your projects only to give you support, investigate a report or keep Striqr running.
No system is perfectly secure, so we can't promise your data will never be accessed without permission. If a breach puts your data at risk, we'll tell you and the regulator as the law requires.
16. Emails from us
We email you only about your account: to verify your address and reset your password. We also tell you when your password changes, or Microsoft is added or removed. Receipts for payments come from Stripe. We don't send marketing emails. If we ever do, we'll ask first, and each one will have a link to unsubscribe.
17. Data in your projects
If you own a project: your project might collect personal data from the people who use it, for example through a sign-up form on your live site. If so, you decide what it collects and why. That makes you the controller of that data, and responsible for it. Tell your visitors what you collect, get any consent the law requires, and keep it secure. We only store and serve it as your host, to run your project, and we don't use it for anything else.
If you visit a site hosted on Striqr: it belongs to its owner, not to Striqr. Ask its owner about your data. If a site misuses data, report it (see Reporting content).
18. Changes to this policy
We'll update this policy when what we do changes. If a change matters, we'll tell you before it takes effect: by email, on striqr.com or in the Striqr app. The date at the top shows when it last changed.
19. Contact us and complaints
Email support@striqr.com with the subject "Privacy", or write to Striqr LTD, 5th Floor, 167-169 Great Portland Street, London W1W 5PF, United Kingdom.
If you're unhappy with how we've handled your data, please tell us first, with the subject "Privacy complaint", so we can try to put it right. We'll confirm we've received your complaint within 30 days, and tell you what we're doing about it.
You also have the right to complain to the UK's data protection regulator, the Information Commissioner's Office (ICO): ico.org.uk/make-a-complaint, or call 0303 123 1113. If you live in the European Economic Area, you can complain to the data protection authority in your country.