This is a translation for your convenience. The German version (/datenschutz) is legally binding.

Privacy policy

Last updated: 13 November 2026

Note on your right to object: You can object at any time to processing based on my legitimate interest. Details in section 10.

1. Controller

Ramon Früh, Horststr. 11, 48607 Ochtrup, email: hallo@fpvrates.com

2. Your blackbox file stays with you

The analysis of your blackbox file (.bbl/.bfl) runs entirely in your browser. The file is not transferred to a server and not stored. It is analyzed only in your browser, I never see it. Technically: the file is loaded into a Web Worker in the browser, decoded and analyzed there. There is no upload.

3. Hosting and server logs

The website is hosted by IONOS SE, Elgendorfer Straße 57, 56410 Montabaur, on servers in Germany. With every request, IONOS automatically stores in server log files: the requested address (page or file), the address of the page you came from (referrer), browser type and version, operating system, time and your IP address, which according to IONOS is anonymized. If you return from the payment or open a login or unlock link, the requested address contains a purchase or unlock identifier. If you come via a Google ad, it contains a click identifier from Google (gclid, gbraid or wbraid). This serves my legitimate interest in a secure, stable and fast delivery of the site (Art. 6(1)(f) GDPR). This data is not combined with other data sources. IONOS deletes the log files after eight weeks at the latest. A data processing agreement is in place with IONOS.

4. Local storage

fpvrates stores the following in your browser's local storage: your language choice, your choice on measurement with Google including the version of the notice text you agreed to (section 4d), your choice between light and dark design, your choice between the simple and the detailed result view, the unlock status of the Tuning Pass (token, time, drone name), the names you give drones without a craft name and, per drone, the round history of the last 64 rounds (date, flight date, start times of the logs, rates, highest measured yaw rate, three metrics of your stick use, proposal, done signal). The analysis results themselves are not stored and are gone after a reload. After an unlock on the home page, your browser's session storage carries the confirmation message once to “My pass”; it is deleted when you close the tab. With your consent (section 4c), the session storage also keeps the type of source of your visit (for example “Google search”), likewise only until you close the tab. Without a Tuning Pass this data is not transferred to me, with a Tuning Pass see section 4a. Storing this is strictly necessary for the site to provide the functions you request (§ 25(2) no. 2 TDDDG). You can delete it at any time by deleting the site data for this domain in your browser. Without your consent, no cookies are set and no third-party analytics services are loaded; with consent see section 4d, for my own audience measurement section 4c.

4a. Tuning Pass: round history on the server

So that your Tuning Pass survives a change of device or deleted browser data, I store the following per pass on the server at IONOS in Germany: the identifier of the purchase (for card, Apple Pay and Google Pay the checkout session at Stripe, for PayPal the PayPal order number and a random purchase reference, for unlock links the unlock code), the start time, the number of drones of the pass and the identifiers of booked add-ons, the names of the drones (craft name and board from the log header, for drones without a craft name the name you enter) and, per round, date, flight date, start times of the logs, rates, highest measured yaw rate, three metrics of your stick use (unused stick travel, share of normal flying, steepness), proposal and done signal. If I move the binding of a drone (terms, section 1), the time of the last move and the previous name of the drone are added for that drone. For PayPal purchases, a pseudonymized check value (HMAC hash) of your PayPal email address is added so that "Log in" can find your purchase (4b). Your blackbox file, GPS data and your email address in plain text are not part of it. Your browser syncs this data with the server when you open the page and after every new round. When you log in and every time your browser syncs the pass, the server checks with Stripe or PayPal whether the purchase was refunded and then blocks the pass. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). Per quad I keep the last 64 rounds; older rounds drop out of the history, the pass and its quads stay. I delete the round history automatically twelve months after the last use. The purchase identifier, the package and the bound drones are stored as long as your pass is valid (terms, section 4), so you can use it again after a long break. On request I delete everything earlier; the pass can then no longer be used.

Gift codes. For every code I store on the IONOS server in Germany a check value (hash) of the code, the package, the time it was issued, whether and when the code was redeemed and whether it is blocked, plus the purchase identifier as above, for PayPal purchases also the check value of your PayPal email address, so that “Log in” finds your purchase (4b). I send the gift code to the email address of the purchase (4b). Whoever redeems a code does not have to provide anything for it. I receive no data about the person given the gift from the buyer. After the redemption, what is written above applies to the pass. I store the data on the code as long as the code or the pass from it is valid; for a blocked code as long as it would otherwise be valid. The legal basis is the performance of the contract with the buyer and, from the redemption, of the usage contract with you (Art. 6(1)(b) GDPR). So that nobody tries out codes, I store a pseudonymised check value (HMAC hash) of your IP address for one hour when you redeem (Art. 6(1)(f) GDPR).

4b. Contract confirmation and login by email link

After the purchase I send you one email with the contract confirmation. I get the address from Stripe for card, Apple Pay and Google Pay (section 6), from PayPal for PayPal (6a). On further devices you request a login link via "Log in": you enter the email address of your purchase, I compare its check value with the stored PayPal purchases and ask Stripe for paid purchases for this address. The request to Stripe goes out with every login request, even if you paid with PayPal. I only send links if a purchase was found, and only to the address entered. If you bought a gift code, instead of a login link I send you the code again as long as it has not been redeemed, after that only the note that it was redeemed. You have no access to the pass of the person you gave it to. Every login link works once and for 30 minutes; until then I store a hash of the link with the identifier of the pass, after that it is deleted. I do not store the address itself. To prevent abuse, I store a pseudonymized check value (HMAC hash) of the email and IP address with the time of the request for one hour. The emails are sent via the IONOS mail server. The legal basis is Art. 6(1)(b) GDPR, for abuse prevention Art. 6(1)(f) GDPR.

4c. Audience measurement without cookies

To see how the site is used and which platforms bring visitors, I count page requests on my server at IONOS in Germany, without third parties and without cookies. When a page is requested, it is counted from the information your browser sends to the server for that request anyway: which page, the domain of the page you came from (for example reddit.com, for Reddit also the subreddit), for a move within fpvrates.com the previous page, your language setting with region (for example es-MX), browser, operating system and whether you use a phone, a tablet or a desktop. Whether a request comes from a browser that wants to display the page, the server recognizes from the request type browsers send along (the “Sec-Fetch-Mode” or “Upgrade-Insecure-Requests” headers); requests without it are counted separately as probable robots, by the same characteristics, as are requests from the network of a data centre (network operator, see below). To detect robots posing as browsers, the server also checks whether further headers your browser sends on its own match that identification and the referring page (“Sec-CH-UA”, “Sec-CH-UA-Mobile”, “Sec-Fetch-User”, “Sec-Fetch-Site”, “Accept”, “Accept-Encoding”, the number of languages in “Accept-Language”); if they do not match, the request is also counted separately as a probable robot, with the reason as a total per day. Until 17 November 2026 the server also counts the result of this check, together with the major version of browser and operating system, the language and the network operator, as a total per combination and day. The server does not request any additional information for this. The server also determines, based on your IP address, the country the request comes from and the network operator (number and name of the autonomous system, for example “AS3320 Deutsche Telekom AG”), using two databases on my server ("IP to Country Lite" and "IP to ASN Lite" by DB-IP, no query to third parties); only the shortened address is looked up (IPv4 without the last block, IPv6 only the first 48 bits); only the country and the network operator are counted, the IP address is not stored for this. Your browser sends nothing extra for this, nothing is stored on or read from your device for this, and identifiers in links are not evaluated. Sitelinks in my Google ads carry the fixed suffix “?ad=1”; the server only uses it to count that the visit came from an ad. It is not an identifier. For a Google click identifier (gclid, gbraid, wbraid) the server only checks whether one is in the address and then likewise counts the visit as coming from an ad; the identifier itself is neither evaluated nor stored. The server also counts whether the example was opened, an analysis was started (your browser loads the analysis software from the server for this), an order was started, a pass was bought (and whether with PayPal), a withdrawal was sent, a login link was requested or used, an unlock link or a gift code was redeemed, a gift code was bought. If someone requests an address on fpvrates.com that does not exist, the server counts the path of that address without any appended parameters, so that I can find broken links. To protect the site against attacks, for such requests, including those from robots, and for wrong passwords for my administration access, the server also counts: the type of request by its path (for example a search for WordPress or for access credentials), the type of program according to the browser identification (for example browser, script, known scanner), the request method, the hour, country and network operator as above and, per hour, whether the sender appeared for the first time in that hour. For this, as for abuse prevention (see below), the server stores a pseudonymized check value (HMAC hash) of the IP address with the times of the requests for one hour; it also works as a brake so that a single sender cannot flood the count. If the analysis of your log fails, you can send me the type of reason with "Report the reason anonymously" (e.g. "firmware not supported"), nothing from your file. Without that click I learn nothing about it. If you choose "Allow" in the "Measurement with Google" notice (4d), your browser sends this to my server with your consent, with whether the choice was made on an ad landing page or after an ad click; only the total is counted. "Decline" is not reported. I use it to extrapolate the numbers from Google Analytics and Google Ads, which only include visitors who consented. Only totals of these values per day and per hour are stored, and for a live view also per minute; the per-minute values are deleted after 60 minutes, the daily totals after 25 months. Once a day the server sends me these totals as a report to my own address hallo@fpvrates.com. No IP address, no identifier, no profile: visits can neither be linked to a person nor followed across several pages. To prevent abuse, I store a pseudonymized check value (HMAC hash) of the IP address for one hour. So that my own visits are not counted, the server compares such a check value of your connection with the one of my connection; yours is not stored for this. The legal basis is my legitimate interest in measuring the reach of the site and in protecting it against attacks and abuse (Art. 6(1)(f) GDPR, see also Recital 49 GDPR). The server deletes expired data automatically at the next request to the site after the period ends, usually within a few minutes; this applies to all short periods named in this policy.

Additionally, with your consent: measurement in the browser. Only if you chose “Allow” in the “Measurement with Google” notice (section 4d) does fpvrates additionally measure in your browser and send to my server: how long a page was visible (until you first leave or hide it, rounded to seconds, at most 30 minutes), which sections of the home page came into view (for example pricing or FAQ), clicks on important buttons (“Get the pass”, “See an example”, “Free check”, log in, language switch, enlarging the Betaflight picture), that a file was chosen for the free check, the result of a free check as a category (counted, or the reason it was rejected, for example “no acro”; nothing from your file) and, for the path to purchase, the type of source you came from (Google ad, Google search, Reddit, direct or other), and whether you then started a free check, opened the order page or bought. Your browser keeps the type of source in its session storage for this until you close the tab. Here too, the server only stores totals per day (for the live view per minute, deleted after 60 minutes; the daily totals after 25 months), without IP address and without identifier; individual visits can neither be linked to a person nor combined. The legal basis is your consent (§ 25(1) TDDDG, Art. 6(1)(a) GDPR). You can withdraw it at any time via “Cookie settings” at the bottom of every page; after that your browser no longer sends these values. Without consent, only the counting on the server described in the paragraph above takes place.

4d. Measurement with Google Analytics and Google Ads (only with consent)

Only if you click "Allow" in the "Measurement with Google" notice does your browser load the Google tag (gtag.js) from Google. Before that and after "Decline", the site loads nothing from Google and sends nothing to Google. The same choice applies to the measurement in the browser without Google described in section 4c. The provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

Google Analytics 4 shows me how the site is used. For this, your browser sends to Google: pages viewed and time spent, the page you came from, scrolling to the end of a page, clicks on links to other websites and on files, starting and submitting forms (without what you enter), device, browser, operating system, screen size and language setting, and a purchase (package, price and a hashed purchase number). Google sets the cookies _ga and _ga_CZ9EPBFJP9 with a random identifier for this, stored for two years according to Google. Google derives your approximate location from your IP address; for visitors from the EU, Switzerland and the UK, the IP address is then discarded and not stored, according to Google. I only receive aggregated reports. For Google Analytics, Google processes the data on my behalf (data processing under Google's data processing terms). Event-level and user-level data is deleted after 14 months.

Google Ads shows me whether an ad click leads to a purchase. If you come via a Google ad, the Google tag stores the click identifier from the address in the cookie _gcl_aw and also sets _gcl_au; both last 90 days according to Google. If you buy a Tuning Pass or an add-on or a gift code, your browser reports the purchase to Google with the price and a hashed purchase number, without email address and without name. Google matches the purchase to the ad click, I only see aggregated numbers per ad and search term. For Google Ads, Google processes the data as an independent controller (controller terms, business.safety.google/adscontrollerterms).

Switched off: remarketing and personalized ads, Google Signals, enhanced conversions (no hashed email addresses to Google) and all data sharing settings in Google Analytics. Purchase, unlock and login identifiers in the address are not sent to Google.

Google also processes data in the USA. Google LLC is certified under the EU-US Data Privacy Framework (checked on 30 October 2026 at dataprivacyframework.gov); for certified companies, the European Commission's adequacy decision of 10 July 2023 applies (Art. 45 GDPR). More in Google's privacy policy: policies.google.com/privacy.

The legal basis is your consent (Art. 6(1)(a) GDPR; for cookies and access to your device § 25(1) TDDDG, the German Telecommunications Digital Services Data Protection Act). You can withdraw it at any time via "Cookie settings" in the footer: "Decline" stops the measurement and deletes the Google cookies of this site. The lawfulness of processing before the withdrawal is not affected (Art. 7(3) GDPR). Your browser stores your choice in local storage (section 4) so the notice does not appear on every visit.

5. Logs by email

If you send me blackbox logs by email, for example with a question about your result, I keep them together with your message. In addition to flight data, these files also contain GPS positions (takeoff point and flight path) if a GPS is installed. I use the logs exclusively to answer your question and to check and improve the analysis, do not pass them on and delete them no later than three months after your request is settled, immediately on request. The legal basis is your consent (Art. 6(1)(a) GDPR), which you can withdraw at any time.

5a. Withdrawal via the withdrawal function

If you withdraw via "Withdraw from contract here", I process your name, the email address of the purchase, your choice (pass, only the add-on or gift code), the code, if given, your voluntary details on purchase date and order number and the time of receipt in order to handle the withdrawal, send you the required receipt by email and be able to prove its receipt. The legal basis is Art. 6(1)(c) GDPR in conjunction with § 356a BGB (German Civil Code). The details are stored on the server at IONOS in Germany, and I receive a copy by email. To prevent abuse, I store a pseudonymized check value (HMAC hash) of your IP and email address for one hour (Art. 6(1)(f) GDPR). The data is deleted when the regular limitation period of three years has expired, which begins at the end of the year of receipt (sections 195 and 199(1) BGB).

6. Payment by card, Apple Pay or Google Pay

If you pay this way, Sold through Link, LLC, 354 Oyster Point Boulevard, South San Francisco, CA 94080, USA, a company affiliated with Stripe, handles payment and invoice on my behalf as Merchant of Record (terms of use, section 2). What you enter on the payment page (payment, billing and contact data) is processed by Link as an independent controller; Link's privacy policy applies. I receive from Stripe the information that payment has been made and whether it was refunded, your email address and the country of the billing address, in order to unlock the pass, send you the contract confirmation with the login link (section 4b), answer questions and arrange refunds (Art. 6(1)(b) GDPR). To prevent abuse of the purchase check, I store a pseudonymized check value (HMAC hash) of your IP address for one hour (Art. 6(1)(f) GDPR). If you order the “+5 quads” add-on, I pass a random order number to the payment page and store it with the identifier of your pass, so the payment is credited to your pass (Art. 6(1)(b) GDPR); I delete unpaid order numbers after 30 days. When I check a purchase or you search for your purchases via "Log in" (4b), the purchase identifier or the email address entered goes to Stripe; data may be transferred to Stripe, LLC in the USA. For the USA there is an adequacy decision of the EU Commission for companies certified under the EU-U.S. Data Privacy Framework (Implementing Decision (EU) 2023/1795, Art. 45 GDPR); Stripe, LLC is certified (dataprivacyframework.gov).

6a. Payment with PayPal

If you pay with PayPal, you buy the Tuning Pass directly from me (section 1); the payment is processed by PayPal (Europe) S.à r.l. et Cie, S.C.A., 22–24 Boulevard Royal, L-2449 Luxembourg, as an independent controller. The PayPal privacy statement applies. From PayPal I receive the payment confirmation, the order number, the amount, whether it was refunded, and your PayPal email address. I use the address once for the contract confirmation with your login link (section 4b) and do not store it; with the pass I store the order number and a pseudonymized check value (HMAC hash) of your address so that "Log in" can find you. Until you return from PayPal, the order number sits in a temporary file for at most two days. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR); to prevent abuse, I store a pseudonymized check value (HMAC hash) of your IP address for one hour (Art. 6(1)(f) GDPR). I keep the payment records of PayPal purchases as long as tax law requires, as accounting records for eight years (Art. 6(1)(c) GDPR in conjunction with § 147 AO, German Fiscal Code).

7. Contact

If you write to me by email, your information is stored for processing the request and for follow-up questions (Art. 6(1)(b) GDPR) and deleted no later than one year after my last reply; if the message concerns a purchase, as long as tax law requires (up to six years, § 147 AO).

8. Fonts

All fonts are loaded from the same server as this page. There is no connection to Google Fonts or other external font services.

9. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20) and objection (Art. 21). You can withdraw any consent you have given at any time. You can lodge complaints with the competent supervisory authority, which for me is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen).

9a. Do you have to provide data?

You are not legally obliged to. The free check needs no information from you. For a purchase and a login link I need your email address; without it I cannot assign a pass to you or reply. You redeem a gift code without providing any data. What your browser technically sends with every request (section 3) is necessary to deliver the site. There is no automated decision-making under Art. 22 GDPR; you decide yourself about the rates proposal.

10. Your right to object (Art. 21 GDPR)

I process some data on the basis of my legitimate interest (Art. 6(1)(f) GDPR): the server logs (section 3), the audience measurement and the evaluation of attacks on the server (4c, not the measurement in the browser, which only runs with consent) and the short-lived check values to prevent abuse (4a, 4b, 4c, 5a, 6, 6a). You can object to this processing at any time on grounds relating to your particular situation. An informal message to hallo@fpvrates.com is enough. I will then no longer process the data unless I can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. I do not send advertising by email.