Privacy Policy

Last updated: October 5, 2026

This policy covers the copy of Flakkar published at flakkar.io.

This Privacy Policy explains how Cody Ehrenreich (“we”, “us”) handles information in connection with the game Flakkar (the “Game”), published at flakkar.io. Contact: support@flakkar.io.

Information we collect

We, the Game's developer, do not set our own advertising cookies. We do collect anonymous gameplay statistics and, for some visits, an anonymous recording of the visit, both described in their own sections below, so we can see where the Game loses players and fix it. Multiplayer also has its own section below — joining a match necessarily means your device talking to ours. The Game saves a few small functional values in your browser's local storage: your in-game settings and preferences (for example volume and audio on/off, language and units, graphics quality, HUD visibility, crosshair, screen shake, field of view, and control options), and a little progress state such as the last game mode you played, your experience points, and whether you have seen the tutorial and the one-line privacy notice. These values stay on your device and are not used to track or identify you.

When you play the Game on a third-party portal, that portal's software may collect data as described under Advertising and Third-party platforms below. In addition, the Game asks that platform's SDK for your browser language and country so it can pick a sensible default language and choose metric or imperial units. It reads those values only to set that default — they are not stored by us, combined with anything else, or sent anywhere. You can override the choice at any time in Settings.

Hosting

The Game's website is delivered by Cloudflare, and the multiplayer game server described below is rented from OVHcloud. Like any web host, Cloudflare's servers may process technical data (such as IP address and request metadata) to deliver content and protect against abuse. See Cloudflare's privacy documentation for details.

Advertising

The copy of the Game at flakkar.io shows no advertising and loads no advertising software. There is no portal SDK on this site, no ad break, and no advertising identifier.

Gameplay statistics

While you play, the Game sends a small, anonymous report to a statistics service we run on the same server as multiplayer (Virginia, United States, rented from OVHcloud), about once every twenty seconds while the Game is on screen. It contains only:

• What happened in the Game — for example that it finished loading and how long that took, which mode you started, which tutorial step or campaign mission you reached, that your aircraft was shot down or scored a kill, your pilot level, and which weapons you equipped.
• Where you are in the Game — the screen you are on (lobby, playing, paused…), so we can tell at which point players stop playing.
• Coarse technical details — device type (desktop, phone or tablet), browser and operating system family, screen width rounded to the nearest hundred pixels, screen pixel density, browser language, time zone, the graphics chip family (for example “Intel” or “NVIDIA”, never the exact model) and whether the browser is drawing in software, the number of processor cores and the memory class the browser reports, frame-rate and frame-timing statistics, the graphics setting in use, the site or link you arrived from (a short name such as “reddit”, never the full address), and a short code identifying any error the Game hit (never the error text).
• A random session number that is new every time the Game is opened, so the reports from one visit can be grouped together.

On flakkar.io the Game also keeps one anonymous random number in your browser's local storage, so we can tell how many players come back on another day. It is not linked to your name, callsign, account or IP address, and clearing your browser's site data for flakkar.io deletes it.

It never contains your callsign, an account, chat, anything you type, or your IP address. The service sees your IP address only as part of receiving the report, uses it for a moment to limit how often one address may send, and does not store or log it. Detailed reports are deleted after 90 days; what remains after that are per-visit summaries with nothing in them that identifies you. The statistics are used only by us, to improve the Game, and are never sold or shared.

Flight recordings

On a share of visits, chosen at random, the Game also records an anonymous replay of the visit and sends it to the same statistics service, about every twenty seconds, so we can watch how the Game plays and fix what goes wrong. A recording notes:

• Your flight — about ten times a second, your aircraft's position, heading, speed and damage, and the positions of the aircraft near you.
• What you did in the Game's window — where the mouse pointer (or your finger) was and when you pressed, and which keys you pressed while playing (as key positions such as “W” or “Space”). Nothing is recorded while a text box such as the callsign or chat field has focus, so nothing you type is ever recorded.
• The screen it ran on — the size of the Game's window, and whether touch controls were on.
• The Game's own saved settings and progress at the start — for example your graphics and control settings, experience points and equipped weapons — so the replay starts from the same place. Your callsign and the anonymous device number are left out.
• In multiplayer, what the game server told your browser — for example the scoreboard and when a match started — with every player's name replaced by “Pilot 1”, “Pilot 2” and so on, and chat removed.
• Game events such as shots fired, kills, crashes and screen changes.

A recording is tied only to that visit's random session number. It contains no callsign (yours or anyone else's), no username, account, chat, typed text or IP address, and on game portals no identifier that lasts beyond the visit. Recordings are watched only by us, replayed inside the Game; they are never sold or shared, and they are deleted automatically within 90 days.

Multiplayer

Multiplayer is optional. The Game connects to our game server when it opens, so that matchmaking and the lobby’s player counts work, and while you play solo it tells the server only which mode you are in. Everything below about matches applies once you join one.

When you join a multiplayer match, your browser opens a connection to a game server we operate (located in Virginia, United States, rented from OVHcloud). Over that connection the server receives:

• Your IP address. Unavoidable — it is how the connection reaches you. We also use it to limit how many connections one address may open, which is what stops a single machine flooding the server.
• Your callsign, the name you type before playing. It is shown to the other players in your match. Choose something that is not your real name if you would rather not share one.
• Your aircraft's position and state while a match is running, so other players can see you fly, plus a small amount of diagnostic information we use to find synchronisation faults.
• Chat messages you send, which are relayed live to the other players in your match.

The game server writes none of this to a database. Match state, callsigns and chat exist only in the server's memory for the length of the match, and are gone when it ends or the server restarts. We do not build a profile from them. If your visit is one of those with a recording (above), the recording made by your own browser includes the positions of the aircraft around you in a match and what the server told your browser, with every name replaced and chat removed.

The one exception is the server's web access log, which records connection times and IP addresses. It is kept for seven days and then deleted automatically, and is used only to investigate abuse and faults.

Other players in your match can see your callsign, your aircraft, and any chat you send. That is the nature of a multiplayer game rather than a data practice, but it is worth stating plainly.

Children's privacy

The Game is intended for a general audience. We do not knowingly collect personal information from children under 13. If you believe a child has provided us information, contact us and we will address it.

Your rights

We keep very little that could relate to you: anonymous statistics and flight recordings tied only to a random session number (or, on flakkar.io, a random device number), and seven days of server access logs. None of it carries a name or account, so we cannot tell which of it is yours, and all of it is deleted on the schedules above. If you have questions about your rights under the GDPR, CCPA, or similar laws, contact us at support@flakkar.io.

Changes

We may update this policy; material changes will be reflected by the “Last updated” date above.

Governing law: the State of Colorado, United States.