# Security

## Reporting a vulnerability

Email **founders@nodeau.ai**. Please do not open a public issue for a security
problem.

Include what you did, what happened, and what you expected. If it is remotely
exploitable, say so in the subject line.

## What Nodeau Alpha does to your machine

The installer's threat model is that you should not have to trust us very much.

**The bootstrap script** (`install.sh`) downloads one file, verifies its
SHA-256 against a published manifest, and unpacks it into a directory you own.
It refuses to run as root. It does not call sudo. If the checksum does not
match, it installs nothing and says so.

**`nodeau install`** shows you what it intends to change and asks first. It
uses your distribution's official package sources and pinned versions. It will
not modify the NVIDIA driver, Secure Boot, the bootloader, partitions, or an
existing Kubernetes cluster.

## Network exposure

Nodeau Alpha opens **no** externally reachable ports.

The local inference endpoint binds `127.0.0.1` and nothing else. It is not a
NodePort, and there is no configuration option to bind another interface. This
is enforced in code and covered by a test that finds this machine's routable
address and asserts the endpoint does *not* answer there.

## Credentials

A local API key is generated with a CSPRNG and stored `0600` in
`$XDG_CONFIG_HOME/nodeau/api-key`. It is never printed unless you ask for it,
never logged, and excluded from support bundles by both path and content
scanning.

## Support bundles

`nodeau support bundle` is generated only when you run it, stays on your
machine, and is sent nowhere automatically. Content is redacted for API keys,
bearer tokens, kubeconfig credentials, PEM material and K3s node tokens, and
weights, kubeconfigs and key files are excluded by path.

Redaction is a safety net, not a guarantee about a file we have never seen.
Read yours before sending it.

## Telemetry

There is none. Nodeau Alpha sends nothing anywhere.