The short version. There is no sign-up, no account, no payment and no advertising. We do not ask for your name, email or phone, and we do not collect them another way.
What is collected is anonymous: how many people opened the site, which map they picked, what kind of device they were on and how long they stayed. None of it identifies anyone.
Your simulator settings, the stick calibration and the throttle mode, stay in your browser and are never sent anywhere.
1. Who handles the data
fpv0 is a non-commercial project. Questions about this policy, or about data, go to hello@fpv0.com.
2. What is collected
2.1. Visit statistics
The Russian version of the site carries a Yandex.Metrica counter. It records anonymous visit data: the page opened, where the visit came from, device type and screen resolution, browser and operating system, a rough region from the IP address, and the time and length of the visit. It uses cookies and
localStorage to tell repeat visits from new ones. This counter is not used on the English version.
That data is handled by Yandex under their own privacy policy. You can opt out with their official opt-out tool, by blocking cookies in your browser, or with any tracker blocker.
2.2. Gameplay statistics
To see which maps and modes people actually use, and where to put effort next, we count the flights themselves, anonymously:
- which map and which track were opened;
- device type, phone, tablet or desktop, and screen size;
- control method: keyboard, on-screen sticks, gamepad or transmitter;
- whether the site is open in a browser or as an installed app;
- how long the session lasted, whether you took off, how many crashes;
- gameplay numbers: drone class, whether prop damage is on and how many hits damaged the props, gates passed, lap time, top speed and altitude;
- browser language and time zone;
- country: worked out on the server from the IP address as the event arrives, and stored only as a two-letter code such as RU or DE. City and finer location are not worked out;
- utm tags from the page address, if the link you followed had them, for example the name of a newsletter or an ad campaign;
- the domain you arrived from, without the specific page address.
If your browser sends Do Not Track or Global Privacy Control, none of this is collected. The site checks for both and sends nothing.
Visitor ID, only with your consent. On your first visit the site asks whether it may remember this browser. If you allow it, the browser stores in its localStorage a random 16-character identifier, the visit number and the time of your last action. The ID is sent along with the gameplay statistics and shows whether visitors come back, where they first came from and how they move between the Russian and international versions of the site. It contains no name, email or IP address and is not linked to data from other sites. It is the only thing kept in the browser that is sent to the server: the settings from section 2.3 stay on the device.
If you decline, the browser remembers only your answer, and statistics are collected as before, without an ID. The ID lives in the browser for no longer than 13 months and is then replaced with a new one. When you follow a link between the Russian and international versions of the site, the ID travels in the part of the address after the # sign, which is not sent to the server and does not end up in logs. You can give or withdraw consent at any time right here:
Pilot account, only if you create one. You can fly without signing in. If you sign in to save records, earn achievements and take part in challenges, we store your email address, callsign, country if you provide it, language, flight results (lap times, flight time, number of flights, gates and crashes, top speed and altitude, drone class and control method), the achievements you have earned and your participation in challenges. When you sign in with Google or Microsoft, we receive from them only your account ID, email address and name, which we use to suggest a callsign; the password for those accounts is never passed to us. The site has no passwords of its own: you sign in with a one-time code sent to your email.
Other pilots can't see your email. Your callsign, records, achievements and challenge results are visible to everyone: that's the point of the leaderboards. Your sign-in key is stored in your browser's localStorage and sent to the server with pilot page requests. Your account and email are stored on a server in Russia. We only email you sign-in codes and, if you haven't turned them off, challenge notifications: when you're invited or overtaken, no more than three a day; you can unsubscribe via the link in the email or on your pilot page. Accounts are for ages 14 and up; younger pilots fly without signing in.
What is never collected or stored: name, email, phone, your actual IP address, advertising identifiers, clipboard contents, browsing history or anything from other sites. No cookies are used for this.
The IP address is used twice on the server and stored neither time: it gives the country and the visitor identifier. After that the address is discarded. To tell one visitor from another without keeping an IP address, the server derives a one-way hash from the IP and browser details, salted with a value that changes every day. The IP cannot be recovered from it, and tomorrow the same visitor gets a different identifier.
Where this data lives. Gameplay statistics are received by a server in Germany, then moved to a server owned by the site operator and kept there. No third-party analytics service ever sees it.
2.3. Settings that stay in your browser
The simulator stores only settings in your browser localStorage : the axis calibration for a connected transmitter, your throttle preference on a phone, the drone class you picked, and whether prop damage is on. None of it leaves the device or reaches us or anyone else. Clearing site data removes it.
2.4. App cache
If you have installed the site as an app , or simply opened it in a modern browser, the map files are cached on your device, about 1.4 MB, so the simulator runs offline. They are ordinary site files and contain nothing about you. The cache goes when you remove the app or clear site data.
2.5. Server logs
Like any site, fpv0 runs on servers that keep request logs including IP addresses. They exist to diagnose faults and fend off attacks, are kept for a limited time, and are not used to study visitor behavior.
2.6. Mobile app
The fpv0 app for Android and iOS collects the same gameplay statistics as the site (section 2.2) and sends them to the same server. Each event gets only two extra fields, the platform (Android or iOS) and the app version number, so we can see which build broke what.
The app has no Yandex.Metrica, no advertising identifiers, no cross-app tracking, no third-party analytics libraries, no ads and no push notifications. It asks for no permissions other than internet access to send the statistics. Without internet the app works fully, the statistics are simply not sent.
Transmitter calibration, throttle mode, graphics quality, your own tracks and the chosen language are stored on the device inside the app and are deleted with it.
3. Why any of it
| Data | What it is for |
|---|---|
| Visit statistics | How many people arrive and from where, and whether the site behaves the same for everyone |
| Map and track | Which locations get flown and which do not, and what to build next |
| Device and control method | Where to put the effort: phone controls, transmitter support or graphics |
| Session length and crashes | Finding spots where a map is too hard, or where something is broken |
4. Who else sees it
Nothing is sold, rented or handed to anyone for advertising or marketing. Two parties are involved: the hosting provider whose servers run the site, and, on the Russian version only, Yandex.Metrica for visit statistics. There are no ad networks, no social pixels and no third-party trackers.
From Google Search Console and Bing Webmaster Tools we receive only general summaries: which queries the site appeared for in search and how many impressions and clicks each page got. These summaries contain nothing about individual visitors, and we do not pass anything about visitors to the search engines.
Sign-in code emails and challenge notifications are sent by the site's hosting provider in Russia. If you sign in with Google or Microsoft, they can see that you are signing in to this site and handle that under their own policies.
5. How long it is kept
Anonymous gameplay statistics are kept in aggregate with no time limit, since they are not personal data. Yandex.Metrica retention follows their own rules. Server logs are kept for a limited period set by the hosting provider.
Events with a visitor ID are kept while consent is in force. When consent is withdrawn, the ID is detached from all events on the server, and they become as anonymous as those of visitors without an ID.
Account data is kept for as long as the account exists. You can delete your account on your pilot page: your email, sign-in methods, flights, records and achievements are erased immediately; in other players' challenges your row stays, without a callsign, so the table doesn't break.
6. Children
The site is not designed to collect anything about children and does not ask for an age, because it collects no personal data from anyone.
7. What you can do
- Turn off visit statistics on the Russian version with a tracker blocker, by blocking cookies, or with the official Yandex.Metrica opt-out. The English version has no such counter.
- Turn off gameplay statistics by enabling Do Not Track or Global Privacy Control in your browser. The site sees it and stops sending.
- Remove local settings and the cache by clearing site data, or by deleting the installed app.
- Give or withdraw consent to the visitor ID: with the button in section 2.2 of this page, at any time.
- you can export all your account data as a single file and delete your account on your pilot page, without writing to us;
- Ask a question by writing to hello@fpv0.com.
Because the data is anonymous and not tied to you, we cannot find and delete "your" records on request. There is nothing in them that points at a particular person.
The exception is the visitor ID, if you allowed it: withdrawing consent with the button in section 2.2 detaches all events on the server from it. If you no longer have the browser with that ID, write to hello@fpv0.com with the ID and we will detach it by hand.
8. Changes to this policy
If what we collect changes, this page is updated and the date at the top changes with it. Anything substantial will be flagged on the home page.