Privacy Policy
Contents
- Who we are and our role
- What data we collect and why
- Student data
- Where data is stored, including Google Drive
- How long we keep data
- Who we share data with
- Cookies and local storage
- Lawful basis for processing
- International transfers
- Your rights
- Data security
- Children
- Changes to this policy
- Contact and complaints
1. Who we are and our role
OctoDecks is provided by Objects and Concepts Limited, registered in England and Wales (company number 13746187), registered office 71-75 Shelton Street, London, England, WC2H 9JQ ("we", "us", "our"). Contact: hello@octodecks.com.
Under UK data protection law our role depends on the data:
- We are the controller for teachers' account, trial and billing data, enquiries you send us, and visits to this website. This policy tells you how we handle that data.
- We are a processor for data about students in live lessons (their answers, and any images or Visualiser recordings in the lesson). When a teacher uses OctoDecks with their class, their school decides why that data is processed, so the school is the controller and we act only on its instructions. Our Data Processing Agreement applies automatically to every school and organisation that uses OctoDecks. If you are a student or parent, your school's privacy notice also applies, and you can contact your school or us.
2. What data we collect and why
| Category | Whose | What | Why |
|---|---|---|---|
| Account data | Subscribed teachers | Email address, name (optional), school or department (for team licences), subscription status, Stripe customer reference | To run your account, send sign-in links, take payment and send service messages |
| Trial data | Free trial users | Email address, a Firebase user ID, browser type, trial start time. Your email address, sign-up time and browser type are also sent to Zapier to add you to our trial email list (see section 6). | To run the trial, send you tips during it, and prevent repeat trials |
| Live lesson data | Teachers and students in a live lesson | Room code, the slides, images and activities the lesson needs, students' automatically assigned numbers and their answers, Visualiser recordings if the teacher uses one. Deleted when the lesson ends, and always within 72 hours. | To run the live lesson and show results to the teacher and students |
| Live lesson check | Subscribed teachers | While a licence is running a live lesson: a random code made by OctoDecks for the device (not a hardware or advertising ID, and not your IP address), the room code, and the time the device last checked in. Linked to the licence, not to a name. Nobody can read it, including the teacher. Deleted when the lesson ends, or within an hour if the connection drops. | To make sure one licence runs one live lesson at a time, because a licence is for one teacher (see our terms) |
| Lesson decks | Teachers | Decks, slides and activity content. Stored on the teacher’s own device, not on our servers. Copied to the teacher’s own Google Drive only if they switch on Drive sync. | To let you build, save and present lessons |
| Server logs | Anyone who visits the website or app | IP address, browser type, time and page requested, kept automatically by our hosting provider (Google Firebase Hosting) | To deliver pages, keep the service secure and investigate faults |
| Website analytics | Visitors to octodecks.com who accept analytics cookies | Pages visited, how you arrived (for example a search or a link), approximate location (country or city, worked out from your IP address, which Google Analytics does not store), device and browser type, and a random ID kept in a cookie | To see which pages are useful and improve the website. Only with your consent. |
| Communications | Anyone who contacts us | Your email address and what you write to us. If you use Send feedback in the app, also your name and email if you give them, and the page, app version and browser you were using. | To reply and provide support |
Analytics on the website only, and only with your consent. Our website, octodecks.com, uses Google Analytics if you press “Accept analytics” in the cookie banner. If you choose “No thanks”, or make no choice, Google Analytics is not loaded at all. We have switched off Google’s advertising features and Google signals, so the data is not used for advertising or linked to your Google account. You can change your mind at any time with (also at the bottom of every page).
No analytics in the app. The OctoDecks app (octodecks.app), including every page students use to join and follow a lesson, has no analytics, tracking or advertising tools. We do not record what teachers or students do in it.
“Ask Mr Hope” on our homepage is a set of pre-written answers built into the page. It does not use AI, and nothing you click in it is sent to us or recorded.
3. Student data
Students do not create accounts, do not log in and are never asked for their name or any other personal details. When a student joins a live lesson with a room code, OctoDecks gives them a number (such as 001, 002) for that lesson only. Their answers are linked to that number and the room code, not to their name or any lasting identity.
This makes student data pseudonymous, not fully anonymous. Personal data can still appear in a lesson, for example:
- a student types their own or someone else’s name in a free-text answer, word cloud or exit ticket
- a Visualiser recording captures a face, a voice or a name written on a book
- a student writes a name on a PaperBuild sign
- the teacher knows which student is using which number
So we treat all live lesson data as personal data and protect it accordingly. We do not collect students’ dates of birth, email addresses or home addresses, and we do not profile students.
Slide images are kept on the teacher’s device. When a live lesson starts, the images it needs are uploaded to Firebase Storage (EU region) so students’ devices can show them, and deleted when the lesson ends (or within 72 hours). Older versions of OctoDecks stored deck images online; each time one of those decks is opened, its images are moved to the teacher’s device and the online copies are deleted.
Visualiser recordings are held only for the lesson. When the teacher ends it, they can download the recordings; the copies on our servers are then deleted (or within 72 hours). A downloaded recording is held by the school, under the school’s own policies.
Screen reader mode remembers on the student’s own device that it is switched on, so it is ready next lesson. This setting stays on the device and is not linked to the student’s name.
Students can read our short, plain-language notice for students, which is linked from the join screen.
4. Where data is stored
4.1 Google Firebase
OctoDecks runs on Google Firebase, provided by Google. Google acts as our processor under its Cloud Data Processing Addendum.
| Firebase service | What it holds | Where |
|---|---|---|
| Realtime Database | Live lesson state and students’ answers (during the lesson only), trial records, licence and account records, feedback sent from the app | EU (Belgium, europe-west1) |
| Storage | Slide images and Visualiser recordings, during the lesson only | EU |
| Authentication | Teacher sign-in (email address and sign-in tokens), anonymous IDs for student devices; sends sign-in link emails | Global: Google processes authentication data in the US and other countries. See section 9. |
| Hosting | Serves the website and app pages; keeps server logs | Global content delivery network: pages are served from the Google location nearest the visitor. See section 9. |
Google Analytics (website only, with your consent) is provided by Google and stores its data on Google’s servers, which may be in the US. See section 9.
4.2 Payments
Payments are handled by Stripe. We never see or store your full card details. Stripe is certified to PCI-DSS Level 1. See Stripe’s privacy policy.
4.3 Your device
Your decks, your settings and (for trial users) the email address you entered are kept in your browser’s local storage on your device. We do not keep a copy of your decks on our servers, during the free trial or after it. Clearing your browser data, or switching device or browser, removes decks held only on that device, and we cannot recover them. PaperBuild worlds work the same way: a world you download is a file on your device, and we keep no copy. If you upload it to play, it is live lesson data and is deleted when the lesson ends.
4.4 Google Drive sync (optional)
If you switch on Google Drive sync, your decks are copied to an OctoDecks folder in your own Google Drive, so you can open them on other devices. It is off by default.
Google’s consent screen will list four permissions:
- “See, edit, create, and delete only the specific Google Drive files you use with this app” (the
drive.filescope). This is the most restricted Drive permission: OctoDecks can only see the.octodeckfiles it created. The rest of your Drive is inaccessible to it. - “See your personal info”, “See your primary Google Account email address” and “Associate you with your personal info on Google”. Google adds these standard sign-in permissions automatically. OctoDecks does not read, store or use your Google profile or email address.
The Drive access token is kept only in your browser and expires after about an hour. It is never sent to our servers. The files in your Drive are held by Google under your own Google account. You can disconnect Drive at any time in the app.
4.5 Fonts
The website and the app load their fonts from our own servers. No page of either, including the pages students use to join and follow a lesson, loads fonts from Google Fonts, so opening them does not send your IP address to Google Fonts.
5. How long we keep data
| Data | How long |
|---|---|
| Account data | While your subscription is active, then 12 months after it ends, then deleted. You can ask us to delete it sooner. |
| Live lesson data (answers, images, Visualiser recordings) | Deleted when the teacher ends the lesson, and automatically within 72 hours at the latest |
| Live lesson check (device code, room code, check-in time) | Deleted when the lesson ends, and automatically within an hour if the connection drops or the browser closes |
| Trial data | 12 months from the start of the trial, or until you ask us to delete it. If you unsubscribe from trial emails, we stop emailing you straight away. |
| Lesson decks | Not held by us. They stay on your device and in your Google Drive, under your control. |
| Server logs | Kept by Google for a short period under its own retention policy. We do not copy them into our own systems. |
| Website analytics | Kept in Google Analytics for 2 months, then deleted automatically. The analytics cookies last up to 2 years unless you delete them or withdraw consent. |
| Payment records | 6 years after the end of the financial year they relate to, as UK tax law requires |
| Emails to us | As long as needed to deal with your message, and no more than 2 years |
6. Who we share data with
We share personal data only with the service providers below (our subprocessors), who act on our instructions under contract, and when the law requires it. The full list, with what each one does and where, is in our subprocessor list.
- Google (Firebase and Google Cloud): hosting, database, file storage during lessons, sign-in and sign-in emails.
- Stripe: payments and the billing portal. Stripe never receives student data.
- Zapier (United States): when you start a free trial, your email address, sign-up time and browser type are sent to Zapier, which adds you to our trial email list. No student data is ever sent to Zapier.
- Google (Google Workspace, EU): sends our trial tips and service emails to teachers. No student data is ever sent to it.
- Google (Google Analytics): only for visitors to octodecks.com who accept analytics cookies. It never receives data from the app, so no student or lesson data is ever sent to it.
We may also disclose data if a court, regulator or the law requires it. If our business is sold, data may pass to the buyer under the same protections, and we will tell you first.
7. Cookies and local storage
We never use cookies for advertising. The app uses only what it needs to work and the settings you choose; it has no analytics cookies.
The website uses Google Analytics cookies only if you agree. When you first visit octodecks.com, a banner asks whether you accept analytics cookies. “Accept analytics” and “No thanks” are equally easy, and nothing is set or sent to Google Analytics until you accept. You can change your choice at any time with , at the bottom of every page; withdrawing consent deletes the analytics cookies. You can also block or delete cookies in your browser settings.
Analytics cookies (website only, with consent)
| Cookie | Purpose | Lasts |
|---|---|---|
| _ga | Google Analytics: tells one visit from another with a random ID | 2 years |
| _ga_SQJE8T55ZZ | Google Analytics: keeps track of your current visit | 2 years |
Local storage (strictly necessary or a setting you chose)
These are kept in your browser’s local storage, not sent to us, and need no consent because they only make the website or app work or remember a setting you chose.
| Key | Purpose | Type |
|---|---|---|
| od-theme | Remembers your background colour (light, dark or a tint) | Preference |
| od-font | Remembers your reading font (standard, Lexend or OpenDyslexic) | Preference |
| od-ra-rate | Remembers your read aloud speed | Preference |
| od-consent | Remembers whether you accepted analytics cookies on the website, and when | Strictly necessary |
| Firebase sign-in tokens | Keep you signed in to the app | Strictly necessary |
| dt_teacher_session | Keeps your teaching session state in the app | Strictly necessary |
| Your decks | Stores your lesson decks on your device | Strictly necessary |
| octodecks_device_id, octodecks_live_codes | A random code for this device, and the room codes of lessons it started today, so a reload or dropped connection can carry on the same lesson (see the live lesson check in section 2) | Strictly necessary |
| octotrial_email, emailForSignIn | The email address you entered, to complete sign-in (trial users) | Strictly necessary |
| oct_screen_reader | Remembers that a student’s device uses screen reader mode | Preference |
The app also loads code from a few other servers: Firebase’s own code from Google (gstatic.com) so that sign-in and live lessons work; Google sign-in (accounts.google.com and apis.google.com) for teachers who use it; and, on teacher pages only, PDF, PowerPoint and zip export tools (cdnjs.cloudflare.com and cdn.jsdelivr.net). Videos a teacher adds to a slide are played by YouTube or Vimeo, under their own privacy policies; YouTube videos use YouTube’s privacy-enhanced mode, so it sets no cookies before you press play. You can clear local storage at any time in your browser settings.
8. Lawful basis for processing
Where we are the controller, we rely on these lawful bases under UK GDPR:
| Processing | Lawful basis |
|---|---|
| Running your account and providing the service | Contract (Article 6(1)(b)) |
| Taking payment and keeping billing records | Contract and legal obligation (Article 6(1)(b) and (c)) |
| Running a free trial you asked for | Contract (Article 6(1)(b)), or steps you asked us to take before entering one |
| Sending tips by email during your trial | Legitimate interests (Article 6(1)(f)): helping you get the most from a product you are trying. You can unsubscribe in any email, and we tell you about these emails when you sign up. |
| Google Drive sync | Contract (Article 6(1)(b)): a feature you choose to switch on. The files go directly between your browser and your Google Drive. |
| Website analytics (Google Analytics cookies) | Consent (Article 6(1)(a)), as the Privacy and Electronic Communications Regulations require for non-essential cookies. You can withdraw it at any time with Cookie settings. |
| Server logs and IP addresses | Legitimate interests (Article 6(1)(f)): delivering pages to your device and keeping the service secure |
| Important service messages (e.g. downtime, changes to terms) | Legitimate interests (Article 6(1)(f)) and, where the law requires us to tell you, legal obligation |
| Responding to legal requests | Legal obligation (Article 6(1)(c)) |
Student data in live lessons: here the school is the controller and chooses the lawful basis. For state schools this is normally public task (Article 6(1)(e)); for independent schools and other organisations it is normally legitimate interests (Article 6(1)(f)). We process this data only to run the lesson, as set out in our DPA.
9. International transfers
Our database and lesson file storage are in the EU. Some of our providers process data outside the UK and EU:
- Google: Firebase Authentication processes sign-in data in the US and other countries, and Firebase Hosting serves pages from Google locations worldwide. Google Analytics (website visitors who accept analytics cookies only) may process data in the US.
- Stripe: a US company that processes payment data in the US.
- Zapier: a US company that processes trial sign-up data in the US.
Each of these transfers is protected by one or both of: the provider’s certification under the UK Extension to the EU-US Data Privacy Framework (the “UK-US data bridge”), and the International Data Transfer Addendum to the EU Standard Contractual Clauses, which forms part of each provider’s data processing terms. You can ask us for a copy of these safeguards.
10. Your rights
Under UK GDPR you have these rights over your personal data:
To use any of these rights, email hello@octodecks.com. We will reply within one month. We may ask you to confirm who you are first.
For student data from live lessons, please contact the school first, as it is the controller; we will help the school respond. In practice we hold no student data after a lesson ends (and never more than 72 hours after it starts), so there is usually nothing left for us to provide or delete.
11. Data security
- All data in transit is encrypted with TLS (HTTPS)
- Data stored by Firebase is encrypted at rest by Google
- Firebase security rules let a device read a live lesson only by entering its room code. Students can see classmates’ answers where an activity shows them to the class, and only the teacher who started a lesson can change or end it
- Code loaded from third-party servers is checked against a fingerprint before it runs, and our pages restrict where scripts can be loaded from
- Teacher accounts use Firebase Authentication (email sign-in link, Google sign-in, or licence key and password); passwords are never stored in plain text
- Live lesson data is deleted automatically, which limits what could ever be exposed
No system is completely secure. If a personal data breach is likely to put your rights at risk, we will tell you and the Information Commissioner’s Office (ICO) as UK GDPR requires. If it affects a school’s student data, we will tell the school without undue delay, as set out in our DPA.
12. Children
Only adults (18 or over) can create OctoDecks accounts. Students of any age can take part in live lessons through a room code, without an account and without being asked for personal details. We have designed the student experience with the ICO’s Age Appropriate Design Code in mind: privacy-protective settings by default, no profiling, no nudges to share more, and a plain-language notice for students.
If a student has typed personal information into an answer and you want it removed before the lesson ends, the teacher can end the session, which deletes it. You can also contact us at hello@octodecks.com.
13. Changes to this policy
We may update this policy. When we make significant changes, we will change the date at the top of this page and tell subscribers by email or in the app.
14. Contact and complaints
- Email: hello@octodecks.com
- Post: Objects and Concepts Limited, 71-75 Shelton Street, London, England, WC2H 9JQ
If you are unhappy with how we have handled your data, you can complain to the Information Commissioner’s Office (ICO) at ico.org.uk/make-a-complaint or on 0303 123 1113. We would appreciate the chance to put things right first.
This policy was last updated on 6 November 2026. Previous versions are available on request.