MANIC
TRASH PANDAGames Lab
Flight Control

HOTAS Project

Privacy notice

Last updated 2026-11-08 · Notice version 2026-11-08. Questions or suggestions: [email protected]

The short version

  • The profiler reads which axes, buttons and hats your controllers report to Windows. It does not record what you press or play.
  • The hardware profile (a JSON file) contains no machine identifier and no information that identifies you: no name, no email, no serial numbers, no Windows username, no computer name, no file paths.
  • You can see exactly what is sent. Use Preview exactly what will be shared before you submit, and a copy of the JSON is saved on your own computer so you can inspect it afterwards.
  • Nothing is uploaded until you tick the consent box and press Submit profile. You can save the file instead and never upload anything.
  • The only personal information the project ever handles is an email address, and only if you apply for the physical HOTAS testing beta. It is stored separately from the hardware profile and never published.

What the profiler reads

When it starts, the profiler asks Windows for the game controllers (joysticks, throttles, pedals, gamepads) that are connected. For each one you leave ticked, it reads the device's declared capabilities: its names, how many axes, buttons and hats it has, and their numeric ranges. It does not install anything, change any setting, or modify any driver, binding or game file.

If you choose Help label the controls, it also listens to the controllers you selected, on your computer only, to notice which control you moved. The live values are used on screen and then discarded. Only a summary is kept in the profile, never a history of your inputs.

What is in the hardware profile

  • Device model information: product name and manufacturer name as the device reports them, and its USB vendor ID and product ID. These identify the model of a device, the same for every unit sold, not your individual unit.
  • Capability data: for each axis, button and hat: standard numeric usage identifiers, report IDs, declared value ranges, and a status (declared, observed, identified or skipped).
  • If you used Help label: the names you chose or typed for controls, and for axes the lowest and highest value seen, and for hats the directions seen. Do not type personal information into a name.
  • Tool details: capture mode (quick or detailed), the profiler's name and version, and your Windows major version (Windows 10 or 11), not the build number, edition or product key.
  • Device numbers inside the file ("device-1", "device-2") are made up fresh each time and mean nothing outside that file.

What is not in the hardware profile

The profile contains no machine identifier and no user-identifiable information. Specifically it does not contain:

  • your name, nickname or email address;
  • device serial numbers, or Windows device paths and instance IDs (which can be unique to your computer);
  • your computer's name, Windows username, machine or hardware ID, or any file path;
  • your IP address;
  • a record of what you pressed, how you moved, or any gameplay or flight data.

The server also rejects any profile whose text looks like an email address, a Windows path or a web link, as an extra safeguard against accidents.

A copy stays on your computer

So that you can check for yourself, the profiler saves a copy of the hardware profile JSON on your computer:

  • when you press Submit profile, a copy of exactly what was sent is saved in Documents\Flight Control HOTAS Profiler\, named hotas-hardware-profile-v1-<id>.json;
  • when you press Save file instead, it is saved wherever you choose.

These copies never include your beta email and are never uploaded automatically. They are ordinary files: open them in any text editor, keep them, or delete them whenever you like. The profiler does not run in the background and does not retry uploads on its own.

Beta application: the only personal data

Applying for the physical HOTAS testing beta is optional and separate from sharing a profile. If you tick the box, you enter an email address, which is used only to contact you about physical HOTAS testing. Applying does not guarantee an invitation.

  • The email is sent in a separate part of the request from the hardware profile and is stored in a separate private database table. It is never written into the profile file, the stored profile, or any public data.
  • The two are linked only by the random contribution ID your submission receives, so that a withdrawal or removal request can be honoured. Only the project maintainer can access that table.
  • Beta emails are never published, sold or shared.
  • You can withdraw your application at any time (see "Your choices").

Technical data handled by the upload service

Uploads go to a Cloudflare Worker at manictrashpanda.dev. As with any internet service, Cloudflare processes technical connection data such as your IP address to deliver the request and protect the service from abuse (for example, limiting how many submissions one address can make per minute). The project's own code does not store your IP address with your submission and does not enable request logging or analytics. Cloudflare may keep its own network logs under its own policies. We cannot promise that no network metadata is processed.

What the project stores per submission: a random contribution ID, a fingerprint (hash) of the profile used only to spot duplicates, the review status, the capture mode, the number of devices, and the calendar date (no time of day) of submission, plus the profile itself in private storage. A random submission token generated by the app for that upload prevents accidental duplicates if you retry; it is not linked to your computer.

How profiles are used and published

Submitted profiles are held privately and reviewed before use. Approved profiles are used to develop and test HOTAS support for Flight Control, and approved, sanitized hardware profiles (including any control names you chose) may be made publicly available as a reusable hardware-profile library. Profiles that are pending or rejected are never public.

How long data is kept

  • Hardware profiles: kept for a maximum of one year from submission, while HOTAS support is under development. They are deleted earlier if they are no longer needed, for example once the HOTAS features are built into the game. An automatic daily clean-up removes anything past one year.
  • Rejected submissions: deleted within 30 days.
  • Beta applications and emails: kept only until the beta ends, or until you withdraw, whichever comes first (and never longer than the one-year limit above, since the email is removed together with its profile).
  • Service and security logs: the project keeps none. Cloudflare may keep its own network logs under its own policies.

Copies saved on your own computer are yours and are not affected.

Your choices

  • Choose which controllers to include, stop at any point, and review the full JSON before sending.
  • Save the file instead of uploading.
  • Withdraw a beta application, or ask for a submitted profile to be removed: email [email protected] and include your contribution ID (shown after upload and in the saved file's name). Because the profile contains nothing that identifies you, the contribution ID is how it can be found.
  • Limits: once an approved profile has been published, copies others have already downloaded cannot be recalled. Because the data is released under CC0, those copies may be reused by anyone.

Reuse of your control names

By submitting names or descriptions you entered for controls, you permit the project to store, adapt and redistribute that annotation data for hardware-compatibility testing, including in public profile files, under the CC0 1.0 Universal public-domain dedication, meaning anyone may reuse it freely. Only submit names you are entitled to share. Hardware facts reported by a device (names, IDs, ranges) are not claimed as anyone's property.

If the profiler or service changes what it collects, this notice and the in-app consent text will change first, and the profiler will ask for fresh consent (the upload service only accepts the current notice version).

Questions and suggestions

Privacy questions, concerns and suggestions: [email protected]