Privacy Policy
Last updated: September 3, 2026
This Privacy Policy explains how Triage ("Triage," "we," "us," or "our"), a project of Astra Deus LLC, handles information when you download the tool from this website or run it on your machine.
$ The short version: Triage reads your system's hardware and software state to diagnose it, and every part of that stays on your device. Nothing it finds about your computer is sent to us, to a cloud service, or to anyone else, including when the AI diagnostic feature explains what it found. The tool has no HTTP client in it at all and cannot contact us even in principle. One check does open a connection to test whether your internet works, and --offline turns even that off. Organizations running the Enterprise fleet features send a summary to their own console, never to us; section 4 spells out exactly what that covers.
1. Triage runs locally
Every diagnostic Triage performs, reading CPU load, memory pressure, disk health, crash and hardware-error logs, thermal and power state, network reachability, and hardware identification, happens entirely on the machine you run it on, using standard tools your operating system already provides. The results are printed straight to your terminal. None of it is written anywhere except your own screen unless you choose to redirect the output yourself (for example, piping it to a file).
| What Triage reads | Where it goes |
|---|---|
| CPU, GPU, memory, disk, and network state | Printed to your terminal only |
| Crash and hardware-error history (e.g. kernel panics, WHEA events) | Printed to your terminal only |
| Machine model, board, and OS version | Printed to your terminal only |
| Whether your internet connection works | Opens a connection; sends nothing about you |
That last row is the one exception worth being precise about, because a security team running a packet capture will see it. Triage's connectivity check resolves a well-known hostname and opens a TCP connection to a public DNS resolver to confirm the machine can reach the internet. It transmits nothing about your system: the fact that a connection succeeded is the diagnostic. It contacts neither us nor anything we operate.
Running triage --offline, or setting TRIAGE_OFFLINE=1, skips that check entirely, and a packet capture across the whole run will then be empty. We would rather you verify that than take our word for it.
Everything else is verifiable from the code itself: Triage does not import an HTTP client anywhere. The binary has no ability to make a web request, so it cannot report on you even if a future version were built to try.
2. What we don't collect
Triage has no account system, no login, and no server component that the diagnostic tool itself talks to. Running it does not:
- Send analytics, usage statistics, or crash reports back to us;
- Transmit any of your diagnostic results anywhere;
- Identify you personally in any way;
- Track how often, or on what machines, you run it.
We have no record of what Triage finds on your computer, because it never reaches us.
3. The AI diagnostic feature
Where available, Triage's AI-assisted diagnostic feature is designed to run using a language model on your own device, not a cloud API. The diagnostic data it summarizes is handed to that local model and back, without leaving your machine. If this ever changes for a future feature, we'll update this policy first and be explicit about exactly what would be sent and why, rather than changing this behavior silently.
4. Enterprise fleet features
Everything above describes Triage as an individual runs it, and it stays true on every device under an Enterprise license too: the diagnostics and the AI analysis still run locally on each machine.
The difference is that fleet mode reports a summary to a console the organization operates. That summary is limited to the device identifier the organization already assigned, the check results, and their severity. It does not include the raw diagnostic output, file contents, browsing activity, keystrokes, screen contents, or anything about what a person was doing on the machine. Triage is a hardware and system-health tool, and fleet mode does not turn it into employee monitoring.
That summary goes to the organization, not to us. Astra Deus LLC does not host, receive, or have access to a customer's fleet data. Where an organization is the one deploying Triage, that organization is the data controller for what it collects, and its own policies govern how long it keeps that data and who can see it.
Enterprise deployments can run fully air-gapped, including the on-device model, so that no part of Triage requires outbound internet access.
5. Licensing and your device
A paid license is checked entirely on your own machine. Licenses are cryptographically signed documents, and Triage verifies that signature offline. It does not contact a licence server when it starts, or ever, so the tool keeps working with no network and we get no record of when or how often you run it.
To stop one personal license being used across unlimited machines, activation ties it to a single device. Triage derives a device fingerprint: it reads the machine identifier your operating system already assigns, and stores only an irreversible hash of it. That hash cannot be turned back into a serial number, a name, or an address, and it is not derived from anything about you.
Activating a personal license is the one moment that fingerprint is shared with us, it happens only because you ran the activate command, and it is not sent during any diagnostic run. We record the license and the fingerprints activated against it so the device limit can be enforced and so support can help when you replace a machine. Enterprise site licenses are deployed by the organization and involve no activation step with us at all.
6. Downloading the installer
Getting Triage onto your machine, whether via the install command on this site or a direct download, is a normal file download. Our hosting and content-delivery providers may log standard technical information about that request, such as IP address, timestamp, and user agent, the same way any web server logs a file download. We use this only for operating and securing the download infrastructure, not to build a profile of you, and we don't cross-reference it with anything Triage does after it's installed, because we have no visibility into that at all.
7. This website
The Triage website does not currently use cookies, analytics, or third-party trackers. If that ever changes, this section will say so specifically, including what's collected and why.
8. Children's privacy
Triage is a technical tool intended for general use and isn't directed at children. We don't knowingly collect personal information from anyone, and that applies equally to children under 13.
9. Changes to this policy
If we update this policy, we'll change the "Last updated" date above. Any change that would mean Triage starts sending diagnostic data off your device will be called out clearly here and in the tool itself, not folded quietly into a routine update.
10. Contact us
Questions about this policy? Reach us at [email protected].