Your data is not the product.

Privacy policy · Effective October 18, 2026 · Tom Hardy

I value my privacy. I value yours just as much.

I, Tom Hardy, and everyone who helps build or shape AirWitness and the FOX family of tools commit to never selling, renting, trading or otherwise profiting from your personal data. I build tools to help you do your job. I don’t need a copy of your working life to do that.

This policy covers my AirWitness and FOX tools and the websites, accounts, licensing, downloads, beta program and support services I operate for them.

What stays with you

Your network investigations, packet captures, terminal sessions, project files and ordinary work belong with you. Installation and license reporting is not a feed of the networks you visit, the commands you run, your packet traffic, or your physical location.

When you ask a tool to run a network test, contact a device or use an external service, that connection still goes to the destination you selected or the test’s configured service. This promise does not make those connections invisible to that destination.

The beta’s small phone-home

Private beta access is permission to test a build, not permission to install it on dozens of devices. Limited installation and license records help me administer that access and spot installs beyond what we agreed. I think that is a fair trade, and I want it stated plainly.

Depending on the product and build, those records can include a locally generated installation ID, license identity, product and version, installation or license-import timestamps, and—for activation-based builds—the computer name and first/last license check-in times. A reinstall that clears local state can create a new installation ID. Newer import-reporting builds queue an import event while offline and send it when a connection is available.

These are installation and licensing records, not a record of your day-to-day work. They are not GPS or a map of where you use the tool. As with any online request, the network address used to contact the service can appear in ordinary server logs.

A valid supported license file can still be loaded offline. Reporting does not turn that offline import into a requirement to contact me first. Available beta access, platform permissions and any agreed installation limits still apply.

Optional wireless hardware profiles

When your build includes Hardware profile, collection happens locally and you can review the complete details before choosing Send profile. The profile contains the app/OS version, architecture, wireless adapter model and available driver, firmware, radio or band information. It contains no account, license or installation ID, computer/user name, serial number, network name, MAC/IP address or location.

The service groups matching configurations and records submission counts and first/last receipt times to help with compatibility work. Counts are reports, not unique people or devices; a report does not certify compatibility. Profiles are available to authorized staff, not automatically published. Nothing is queued for automatic sending if a submission fails. Normal service access logs may still contain the connection’s IP address, and an unusual hardware configuration can be distinctive.

Accounts, applications and downloads

If you create an account, apply for testing or receive a license, I keep the information needed to manage that relationship: for example, your name, email, application answers, permissions, agreement acceptance and license details. Passwords are stored as password hashes, not readable passwords.

The download service records which product and version was delivered and when. Where available, the record is associated with the signed-in account or the license link used. That helps me understand which builds are reaching testers; a download count does not tell me what you did with the software or prove who used a shared link.

If you send a website question or email, I receive the contact details and message you choose to provide so I can answer.

Crashes, errors and help fixing a problem

Beta AirWitness builds can automatically send queued crash reports when the service is reachable. A report can contain the app version, operating system and runtime details, error and stack trace, report identifiers and a timestamp. A verified license can associate it with your tester account. Reports can be sent without a verified license too; that does not make the network connection anonymous.

The current crash reporter attempts to remove user-profile names from paths, but that is not a guarantee that every error message is free of sensitive details. Screenshots are not automatically captured by this crash-reporting mechanism.

Automatic beta crash reports become posts on the beta feedback board. Approved participating testers and staff can read that board. Messages, screenshots and attachments you post there are visible to that audience too. The board requires access; it is not a public webpage. If something is sensitive, contact me directly instead of putting it on the board.

If you choose to send screenshots, logs, a show tech, configuration details or hardware information for troubleshooting, I use them to reproduce problems, fix bugs, understand what does not fit your workflow and improve the product. Please sanitize them first: remove passwords, keys, tokens, customer details and anything you are not authorized to share. Do not assume automatic redaction will do it for you.

What I use the information for

Only to operate and protect these services, administer accounts and beta access, deliver licenses and builds, answer you, and make the tools better. Limited installation and download records help show which products and builds are being tried. Error reports and information you choose to share help explain how they can be improved.

I do not sell your information to advertisers or data brokers, build advertising profiles from it, or give it away for someone else’s unrelated use. Access by people helping me is limited to the work they need to do under this same privacy commitment.

Who may handle it

Running a website and answering an email involve hosting and email providers. They may handle the information needed to deliver those services. That necessary handling is different from selling or giving your data away for their own use. Beta-board visibility is explained above; choose what you share there accordingly.

I will not publish your private support materials or use them for marketing without your permission. If disclosure is legally required, I may have to provide information I actually hold. This policy cannot promise that no lawful demand will ever arrive. My separately dated warrant canary states what I have personally confirmed as of its stated date.

Websites and cookies

The public product and documentation pages do not use advertising trackers. Account services use cookies needed for sign-in, session security and form protection. Web services can retain ordinary access and security logs, including an IP address, requested address, time and browser information, to deliver the service and investigate faults or abuse. Those logs are not a record of what you do inside the desktop tools.

Links to other companies’ websites take you to their services and their own privacy policies.

Keeping information and asking for help

I keep information for the account, license, support, security or legal purpose it serves. There is currently no single automatic deletion deadline covering every record. Backups may retain older copies until they rotate out.

You can email me at admin@airwitness.net to ask what information I hold about you, correct it, request deletion, or discuss a private way to troubleshoot. I may need to verify that it is yours. I will explain if a record must be kept for an active license, security or legal obligation, or if a backup copy cannot be removed immediately.

If our collection or purposes change, this page will be updated with a new effective date. I will not quietly turn information entrusted for support into a product for someone else.

Your trust matters more than another data point. If something about a tool’s behavior or this policy does not sit right with you, let’s talk.