Privacy & your camera

Last updated 12 September 2026

Mid-Air Games has no accounts, no login and no database. The games run entirely inside your browser tab. Your webcam video is analysed on your own device and is never uploaded, recorded or sent to us or anyone else.

What happens to your camera feed

Three of the four games ask for camera access. When you allow it, the video stream stays inside your browser. Google's MediaPipe models — downloaded to your device as ordinary JavaScript and WebAssembly files — look at each frame and work out where your hand or face is. The games read those coordinates and nothing else.

No frame, screenshot, recording or landmark coordinate is transmitted anywhere. The pages do make other network requests — they download code and assets from the services listed below, and analytics sends measurement data — but none of it carries anything derived from your camera. You can check this yourself: open your browser's developer tools, watch the Network tab while you play, and you will see no upload of image or landmark data at all.

When you leave a game or close the tab, the camera stream is released and the camera indicator light goes out.

What is stored on your device

Scores and settings are kept in your browser's localStorage. This never leaves your device and we cannot read it. Clearing site data for mid-air.games erases all of it permanently.

StoredWhat it is
High scores & leaderboardsYour best scores per game, and the name you type on the score screen
Achievements & progressBadges unlocked, highest stage reached, belt progress
Player nameOnly what you type into the name box yourself
Cookie choiceWhether you accepted or declined analytics

The leaderboards are local to your browser. Nobody else can see them, and they do not sync between your devices.

Analytics cookies

We use Google Analytics 4 (property G-QETDZT45CW) to count page views and see which games get played. No analytics cookie is written until you accept. The site loads with Google Consent Mode set to deny analytics storage, so nothing is stored in your browser and no visit is tied to you unless you press Allow.

To be precise about what does happen before you choose: the Google tag itself is fetched when the page loads, and while consent is denied it may send cookieless pings that carry no identifier and cannot be joined up across pages or visits. If you press Decline, it stays that way.

If you accept, Google sets the cookies _ga and _ga_QETDZT45CW to tell repeat visits apart. We look at aggregate numbers: which game was opened, which control mode was chosen, whether the camera was allowed, and when a run ends. The end-of-run event includes your score for that run as a plain number, so we can see how far people get. We never send your name, your leaderboard, or anything derived from your camera. Google LLC acts as our processor.

Changed your mind? Clear site data for mid-air.games and the banner will ask again, or block cookies for this site in your browser settings.

Other services your browser contacts

The site is static and self-hosted, but pages load libraries and assets from a few third parties. Each of these necessarily sees your IP address and browser, as any web request does.

Children

The games are suitable for all ages and we do not knowingly collect anything from anyone. Because there are no accounts and nothing is uploaded, playing requires giving us no personal information at all.

Your rights

Under the GDPR you have the right to access, correct, erase and port your personal data, and to object to processing. In practice there is very little to exercise these against: we hold no account, no profile and no server-side record of you.

You also have the right to complain to your local supervisory authority. In Ireland that is the Data Protection Commission.

Who we are

Mid-Air Games is an independent browser-games project operated from Ireland. Contact: info@mid-air.games.

Changes

If this page changes materially, the date at the top changes with it. The site is open about its behaviour by design: everything described here is visible in the page source.