RCAT Systems
  • Open a Log
  • Sign In
Flight Insight

Privacy Policy

Effective October 1, 2026

The AeroKore Telemetry Parser is run by RCAT Systems ("we", "us"). It is made up of the website at insight.aerokore.com and the AeroKore radio app for Spektrum iX14 and iX20 radios. This policy explains what we collect when you use them, why, who can see it, and how long we keep it.

What we collect

Logs you open

  • When you open a telemetry log on the website, it's read in your own browser. The log isn't uploaded and we never see it, unless you choose to save or share a flight from it, or to share the log with the developers (below).
  • We do count each log opened, so we know how the site is used. The count includes the file's size, how long it took to read, how many flights it held, the log format, and which kinds of sensors it had (for example "airspeed" or "GPS"). We don't record the file, its name, the model name, or your IP address with these counts.

Logs you share with the developers

  • On the website, "Share this log with the developers to help improve the tool" is off unless you tick it. While it's ticked, each log you open is sent to us whole: every session in it, including any GPS positions, its file name, whether it opened, and, if you're signed in, your account.
  • We use these logs only to find and fix problems and to improve how logs are read and analyzed. We may keep small excerpts, with GPS positions removed or moved, as test cases.
  • Sharing is optional: everything on the website works without it, and nothing is given in return (see the Terms of Use).

When you sign in

  • You sign in with your Google account. We receive your name, email address, profile photo link, and an account ID from the sign-in provider. We never see your Google password.
  • We create your account the first time you sign in.

Flights you save

  • The part of the log that belongs to that flight, exactly as your radio recorded it. That's every sensor reading in it, which can include speed, height, temperatures, battery and receiver readings, stick and switch positions, and the date and time.
  • GPS position: some logs, for example FrSky and RadioMaster logs from a model with a GPS sensor, include the model's position every second. A saved flight keeps that position, and it shows where you fly.
  • The file name, the model name stored in the log, when you saved it, and whether it came from the website or the radio app.
  • A summary of the flight worked out by your browser or the radio: the flight recap, key numbers such as top speed or peak temperature, and the numbers used to compare your flights.
  • A fingerprint (hash) of the flight's data, so the same flight isn't saved twice.
  • Flights you share: when you make a share link, the flight's log (including its GPS path, if it has one), its model name and times are stored so anyone with the link can open it. If you're signed in, the link is tied to your account; if not, nothing about you is kept with it.
  • Equipment and notes you add: the equipment you tag a flight with (for example a prop, battery or fuel) and any notes you write. Your list of equipment is kept so it can be suggested next time. Notes are free text, so only write in them what you're happy to store with the flight.

Your models

  • The models your flights are grouped under, the names you give them, and which radio model names are linked to each one.

Your preferences

  • Your time zone and units.

The radio app

  • You sign in to the radio app with your Google account, as above.
  • The app reads the log files on your radio and works out each flight on the radio itself, so it also works without internet. It sends a flight to your account only when you save it.
  • The radio keeps a list of which flights are already saved to your account, so it can show that offline. Signing out of the app clears that list.
  • Charts and CSV files you make in the app stay on the radio.

Technical information

  • Like most websites, our hosting provider records each request to our servers: your IP address, browser type, the address requested, the time, and the response. We use these records to keep the service running and secure.

Testers of the radio app

  • If you test pre-release versions of the radio app, we use your email address to invite you and to deliver new versions.

Cookies and browser storage

  • Sign-in cookie: keeps you signed in until you sign out or close your browser.
  • Sign-in provider: the sign-in page stores your sign-in state in your browser while you sign in with Google.
  • Viewer settings: the website remembers some settings for each model in your browser's storage, such as how many pulses per revolution your RPM sensor sends and which type of air sensor you use. It also stores the date of your last visit, so we count you as one visitor per day without giving you an ID. This stays in your browser and isn't sent to us.
  • Website analytics: we use an analytics service to understand how many people visit and which parts of the site they use.
    • It sets cookies with a random identifier and records the pages you view, your approximate location (from your IP address), and your device and browser type.
    • We don't send it your name, email, file names, model names or flight data, and we remove identifiers from page addresses before they're sent.
    • We've turned off the service's advertising features, and we don't use advertising cookies.
    • To opt out, block cookies for this site in your browser settings or use a browser add-on that blocks analytics. The analytics provider may also offer its own browser opt-out add-on. The site works the same without analytics.

How we use it

  • To run your account and keep you signed in.
  • To store your saved flights and models, show them back to you, and work out trends across your flights.
  • To save flights from the radio app to your account.
  • To count how the site is used (logs opened, flights saved, sign-ups), so we know what to improve. These counts are totals for each day, not records about you.
  • To keep the service secure, prevent abuse, and fix problems.

We don't sell your information or share it for advertising.

Who can see your information

  • You. Your saved flights and models are private to your account.
  • Our developers at RCAT Systems can see logs you chose to share with them.
  • Anyone with a share link you made can open that flight: its log, model name and times, including its GPS path if it has one. They don't see who shared it, your equipment or notes, or any of your other flights.
  • Our administrators, a small number of people at RCAT Systems. They can see your name, email, plan, and your list of saved flights (model names, dates and sizes), so they can support you and manage limits. They open your flight data only when needed to help you, fix a problem, or meet a legal obligation.
  • Service providers that run parts of the service for us, under agreements that let them use your information only to provide their service. They fall into these categories:
    • Cloud hosting and storage providers run the website and store accounts, saved flights and models, in the United States. They handle everything you save, and the technical records of each request.
    • Sign-in and authentication providers let you sign in with your Google account, on the website and the radio app. They handle your name, email address, profile photo link and account ID.
    • Website analytics services count visits and page views, as described above. They handle a random identifier, the pages you view, and technical information such as your IP address, device and browser.
    • App distribution services for testers send invitations and pre-release versions of the radio app. They handle testers' email addresses.
  • When the law requires it, for example to respond to a valid legal request.
  • If the business changes hands, your information may move to the new owner, who must follow this policy for it.

How long we keep it

  • Saved flights and models: until you delete them or close your account. There's no time limit; instead, each free account can keep up to 1,000 saved flights.
  • Your account: until you close it. [Proposal, to confirm: accounts with no sign-in for 3 years are closed and their flights deleted. We'll email you 30 days before.]
  • Logs shared with the developers: kept for up to 12 months, then deleted. Test-case excerpts (with GPS positions removed or moved) can be kept longer.
  • Share links: a 24-hour link and its copy of the flight are deleted after 24 hours. A saved flight's link works until you turn sharing off or delete the flight.
  • Daily usage counts: kept as totals. They don't identify you.
  • Request records from our hosting provider: deleted after [30 days].
  • Website analytics: kept by the analytics service for [14 months], then deleted.
  • Deleted flights: removed straight away, though a copy can remain in our storage provider's recovery area for up to [7 days].

Your choices

  • See and change: you can see your saved flights and models at any time in My Models, rename and merge models, and change your preferences.
  • Delete flights: you can delete any saved flight at any time. That removes its data and summary, and turns off its share link.
  • Sharing logs with the developers is off unless you tick the box. To have a log you shared deleted sooner, email info@rcatsystems.com with its file name and the day you shared it.
  • Stop sharing: you can turn off a saved flight's share link at any time; the link stops working straight away. A 24-hour link runs out on its own.
  • Close your account: contact us at info@rcatsystems.com and we'll delete your account, saved flights and models within 30 days. Logs and charts on your own radio or computer aren't affected.
  • Analytics: you can block analytics cookies as described above.
  • Use it without an account: opening logs and every chart and analysis on the website work without signing in, and nothing is stored unless you make a share link or share a log with the developers.

Security

  • All connections use HTTPS.
  • Sign-in goes through Google, so we never handle your password.
  • Saved flights are stored privately for each account. Saving, reading and deleting flights require you to be signed in.
  • Administrator access is limited to a short list of named accounts.

No system is perfectly secure. If we learn of a breach affecting your information, we'll notify you as the law requires.

Children

The service isn't meant for children under 13, and we don't knowingly collect their information. If you believe a child under 13 has given us information, contact us and we'll delete it.

Changes

If we change this policy in a way that matters, we'll post the new version here with a new date and, for significant changes, email account holders.

Contact

RCAT Systems
812 Asbury St, San Jose, CA
info@rcatsystems.com

Privacy · Terms · Tour · RCATS telemetry · iX radio app (beta)