Welcome to the new MathsGenie!Tell us what you think

Privacy and Cookie Policy

Last updated: 24 April 2026

This policy describes how Maths Genie (“we”, “us”) processes personal data when you use our website and app. It also explains how we use cookies and similar technologies, and which partners help us deliver the service.

If you use Maths Genie with an account, we process personal data so we can run the service — for example to keep you signed in, save your preferences and study progress, and improve reliability and security.

What we process

Depending on how you use Maths Genie, this may include:

  • Account and profile: information from your sign-in provider (such as your name, email address, and profile picture) and details you add in the product.
  • Usage and study data: content and activity associated with your account, including progress, saved work, and settings — stored so the service works as you expect.
  • Support and feedback: if you contact us or submit a report through our feedback forms, we process what you send us so we can respond.
  • Product analytics and diagnostics: where you consent, we process pseudonymised product usage events (pages viewed, features used, interaction timings), a small sample of session replays, and error/exception reports so we can understand how the product is used, fix bugs, and improve reliability. Where you do not consent, we rely on a privacy-preserving, cookieless mode that counts usage without storing identifiers on your device (see “Product analytics and session replay” below).

We host application data with our database provider and deliver the site through our hosting network. We do not sell your personal data.

Sign-in and Google OAuth

Authentication is handled by WorkOS (User Management / AuthKit). When you sign in, WorkOS issues a secure session so we can recognise your account on later visits.

If you choose Sign in with Google, Google acts as an identity provider during that flow. Google receives information according to its own settings for that login experience. See Google's Privacy Policy and How Google uses cookies. WorkOS receives tokens and profile details needed to create your session; we receive only what is required to run Maths Genie.

Service providers and infrastructure

We rely on subprocessors to host and operate Maths Genie, including:

  • WorkOS — authentication and user management. Privacy policy.
  • Cloudflare — network security and delivery of the application; optional edge cookies as part of operating the site. Static assets may be served from Cloudflare R2. Privacy policy.
  • PlanetScale — managed Postgres database for application data. Privacy policy.
  • Tally — forms used for feedback and bug reports. Privacy policy.
  • PostHog — product analytics, session replay, and error tracking. We use PostHog Cloud EU (hosted in Frankfurt, Germany) so application data stays within the EEA. Analytics requests are reverse-proxied through our own domain under /ingest and forwarded to PostHog; we act as the data controller and PostHog acts as our data processor under a Data Processing Agreement. Privacy policy.

Cookies and similar technologies

Cookies (and similar technologies such as localStorage) are small pieces of data stored on your device. We and our providers use them where strictly necessary to keep the product working and to remember your choices. Where you give consent, we also use them for optional product analytics and session replay so we can diagnose issues and improve Maths Genie. We do not run advertising cookies or sell personal data.

Examples include:

Strictly necessary / functional

Session and security cookies from WorkOS (such as artefacts used during sign-in and to maintain your authenticated session), and cookies we set to remember that you have completed onboarding or to align the app with your account state. These are needed for the service to function safely.

Cookie consent

We record your choices about optional cookies (for example in a cookie named maths_genie_consent and associated storage) so we do not keep asking on every visit.

Product analytics and session replay (PostHog)

We use PostHog (EU-hosted) to understand how Maths Genie is used, to reproduce bugs through a small sample of anonymised session replays (currently around 5% of sessions), and to capture front-end exceptions. Nothing is captured until you make a choice in the cookie banner.

If you choose “Allow”: PostHog sets first-party items in localStorage and/or cookies — typically ph_<project>_posthog and related keys — to assign a pseudonymous device identifier, group events into a session, and remember your opt-in choice. When you are signed in, we also link that identifier to your account ID (and, on the server, your email) so support and debugging can match up server-side and client-side events.

If you choose “Opt out”: we switch PostHog into cookieless mode. No PostHog cookies, local storage, or session storage are written on your device; PostHog counts unique visits using a rotating, server-side privacy-preserving hash rather than a persistent identifier, and session replay is disabled.

Session replays mask inputs and sensitive text by default; passwords and similar fields are never recorded. See PostHog's session replay privacy controls for details.

Cloudflare

Our hosting provider may set cookies for security, performance, or bot management. More detail: Understanding the Cloudflare Cookies.

Embedded YouTube videos

Learning content may include YouTube embeds. When you play a video, Google may use cookies and similar technologies subject to YouTube's terms and Google's privacy policy. Where we can, we load embeds in a privacy-conscious way; Google may still process data when content is played.

Managing cookies

You can change optional cookie choices in Settings → Privacy & cookies when you are signed in. You can also delete or block cookies from your browser settings; blocking strictly necessary cookies may affect sign-in and core features.

For general guidance on controlling cookies, see Cookies and You.

Changes

We may update this policy when our practices or providers change. The “Last updated” date at the top will reflect the latest revision.