How Hoppo Keeps Webcam Video Private

A plain-language explainer for school administrators and careful parents: what runs on the device, what is never sent, what analytics collects, which other companies are contacted, and how to check it yourself.

  • Tracking runs in the browser
  • No video or images sent
  • No kid accounts
  • Analytics can be switched off

The short version: Hoppo's camera games watch for movement inside your web browser, on your own computer or tablet. The video, any pictures, and the body, hand and face points the games track are never sent to us or to anyone else. We count anonymous usage (which games are played, scores, errors) with no id stored on the device, and you can turn that off. There are no accounts for kids.

What runs on the device

When a camera game starts, your browser asks for permission to use the camera. If you allow it, each video frame goes from the webcam to tracking models that run inside the browser tab. Hoppo uses Google's open-source MediaPipe models: hand tracking, body-pose tracking, face tracking (for Silly Faces), and object recognition for the find-it games like I Spy. The models and the engine that runs them (WebAssembly) are downloaded once, then everything happens on the device.

The models turn each frame into a set of points, such as where a hand or a shoulder is. The game uses those points to pop a bubble or check a jump, then moves on to the next frame. The points are not kept beyond the current moment of play.

The Brain Break for classrooms and every touch game don't use the camera at all.

What is never sent

  • Video. Camera frames are never uploaded, recorded or stored on a server.
  • Pictures. No photos or screenshots of your child. In the find-it games, small photos of the found objects appear on the results screen; they stay in the browser's memory and disappear when the page is closed or reloaded. Share cards use Hoppo artwork, never a camera image.
  • Body, hand and face points. The tracking points are not saved and not sent anywhere.
  • Sound. The microphone is not used.
  • Names. An optional nickname and pet name are saved on the device only.

What analytics does collect

To learn which games work and fix what breaks, Hoppo sends a small number of anonymous events. Exactly:

  • No stored id. Nothing is saved on the device for analytics. Our analytics provider groups one day's events by a one-way code made from the shortened IP address and browser type, mixed with a secret that changes every day. It is not tied to a name or email, and the next day gets a new code.
  • Events such as game_start and game_end (which game, score, stars, round length, touch or camera), whether the camera was allowed, page views, and short error reports. The only camera detail is the frame size, like 1280 by 720.
  • Browser details: browser type, operating system, screen size, language, time zone, the page address with anything personal-looking removed, and the site you came from.

What it does not collect:

  • No IP address with the events. Analytics goes through our own server first, which blanks the last part of the IP address before passing events on to PostHog, our analytics provider. We also tell PostHog not to store the IP. Our server's access logs (kept about 14 days) store only the shortened IP address, never the full one. Cloudflare, which carries traffic to our server, sees the full address to deliver the page.
  • No location. We tell PostHog not to work out a city or coordinates.
  • No cookies, no screen recording, no ads.
  • Global Privacy Control and Do Not Track are honored. If the browser sends either signal, analytics never starts.

You are in control. In Hoppo, open Settings → Account → Privacy (for grown-ups). Untick Send anonymous usage stats to turn analytics off on that device, or tap Delete everything saved on this device to clear progress. Usage events are deleted after 12 months. The full list is in the privacy policy.

Other companies the browser contacts

As of November 2026:

  • Cloudflare carries all traffic to playhoppo.com and protects it from attacks. It sees the IP address and browser of every visit, as our service provider.
  • The MediaPipe tracking engine and model files are served from playhoppo.com itself, so normally no other company is involved when a camera game loads.
  • jsDelivr (cdn.jsdelivr.net) and Google Cloud Storage (storage.googleapis.com) are the backup: if our copy of the engine or models can't be loaded, the game downloads the same files from them instead.
  • The fonts are served from playhoppo.com itself too.
  • PostHog receives the analytics events above, through our own server. Your browser does not contact PostHog directly.

When they are used, jsDelivr and Google see the IP address and browser type of the device that downloads the files. They receive no game data and nothing from the camera. The game page's Content Security Policy only allows network connections to playhoppo.com, cdn.jsdelivr.net and storage.googleapis.com. If any of this changes, this page is updated.

For school administrators

  • No student accounts, no logins, no class rosters. Students are never asked for a name or email. Teachers can optionally leave an email for updates, and it is kept apart from play data.
  • Domains to allow if your network filters sites: playhoppo.com, cdn.jsdelivr.net and storage.googleapis.com. On managed Chromebooks, camera access may also need to be allowed for playhoppo.com: see camera games on school Chromebooks for the Admin console settings.
  • No camera needed for the classroom Brain Break: Hoppo calls the moves on the screen and the class copies.
  • Certifications: Hoppo aims to follow COPPA but does not hold a privacy certification at this time. We would rather tell you that plainly.

How to check it yourself

You don't have to take our word for it. On a laptop:

  1. Open playhoppo.com in Chrome or Edge, then open developer tools (F12, or Cmd+Option+I on a Mac) and choose the Network tab.
  2. Start a camera game and play for a minute.
  3. At the start you will see the model and engine files download from playhoppo.com (under /ml/), or from storage.googleapis.com and cdn.jsdelivr.net if the game had to use the backup.
  4. After that, the only requests are a few small ones to /ingest: the analytics events. Click one and open Payload to read exactly what it says.
  5. There is no steady stream of large uploads. Sending video would look like a constant flow of big requests for as long as the camera is on.

In Safari, turn on Show features for web developers in Settings → Advanced, then use Develop → Show Web Inspector → Network.

Questions

Email [email protected]. We answer privacy questions from parents and schools, Usage events carry no id stored on your device, so they can't be traced back to it; they are deleted after 12 months. See also the privacy policy and the teacher page.

Frequently Asked Questions

Does Hoppo record or upload my child's video?

No. The camera picture goes straight from the webcam to tracking models that run inside your browser. Hoppo does not record it, store it on a server, or send it anywhere. The only camera detail our analytics receives is the frame size, such as 1280 by 720.

Are body, hand or face tracking points sent anywhere?

No. The points the models find (where a hand, shoulder or nose is) stay in the browser's memory for the current moment of the game and are thrown away. They are not saved and not sent to us or anyone else.

What does Hoppo's analytics collect?

Anonymous usage events, such as game_start and game_end with the game, score, stars and round length, whether the camera was allowed, page views and error reports, plus browser type, screen size, language and time zone. No id is stored on the device: they are grouped for one day by a one-way code from the shortened IP address and browser type that changes every day, and are not tied to a name or email. The IP address is not stored with them and we do not look up location. Global Privacy Control and Do Not Track switch analytics off automatically. Visitors in the EU, EEA, UK and Switzerland send no analytics at all.

Which other companies does the browser contact?

When a camera game loads, the browser downloads the tracking engine and model files from playhoppo.com itself. Only if that copy can't be reached does it fall back to the same files from jsDelivr (cdn.jsdelivr.net) and Google (storage.googleapis.com). Fonts are served from playhoppo.com too. These companies see the IP address and browser that downloads the files, like any website would, but receive no game or personal data. Analytics goes to our own server first, and from there to PostHog.

Do kids need an account?

No. There are no logins and no student accounts. Kids are never asked for a name or email. Progress, an optional nickname and pet name stay on the device. Grown-ups can choose to leave an email for updates, and it is kept apart from play data.

How can I check this myself?

Open the browser's developer tools, choose the Network tab, and play a camera game for a minute. You will see the model files download at the start, then only a few small requests to /ingest, which are the analytics events. There is no steady stream of large uploads, which is what sending video would look like.

How do I turn analytics off or delete what is saved?

In Hoppo, open Settings, then Account, then Privacy (for grown-ups). Untick Send anonymous usage stats to stop analytics on that device, or tap Delete everything saved on this device to clear progress. Usage events carry no id stored on the device and are deleted after 12 months.