Aster runs inside your process, has no telemetry, opens no network connections in its default build, and stores no data of its own; each claim below is paired with a way to check it.
The claims
| # | Claim | How it is enforced | How you verify it |
|---|---|---|---|
| 1 | Aster runs in-process as a library. It starts no service, daemon or helper process. | The core crates contain no std::process. | tools/trust/no-io-check.sh (source scan) |
| 2 | No telemetry, analytics, crash reporting or update checks. | No such code and no such dependency in the default build. | tools/trust/no-io-check.sh (dependency graph) and read the dependency list in rust/Cargo.lock |
| 3 | No network access in the default build. | std::net and socket types appear only in rust/crates/aster-appkit/src/sync/tcp.rs, compiled only with the Cargo feature net-sync, which is off by default. | tools/trust/no-io-check.sh; cargo tree -p aster-appkit -e normal shows no network crate |
| 4 | Aster stores no data. It does not read or write files in the default build. | The only filesystem code is rust/crates/aster-appkit/src/app/persist.rs, compiled only with the feature persist, which is off by default. | tools/trust/no-io-check.sh |
| 5 | Configuration is not read from the environment. | The guard fails on std::env::var* and related calls in the guarded crates. | tools/trust/no-io-check.sh |
"Default build" means cargo build with no feature flags, for the crates aster-ui, hudlife-core, hudlife-cpu, hudlife-opentype (the core) and aster-appkit. These checks have so far covered the core crates; extending them to the shipped native runtime, CLI, browser module and Aster MD is open work and the EULA's no-data sentence must wait for it.
What the host application still controls
Aster is a rendering and UI toolkit. Your application decides what is drawn, loaded and saved:
- Fonts, images and documents are supplied by the host. Aster takes bytes or values in and produces pixels or layout out.
- If you enable
net-sync, Aster's collaborative sync can open TCP connections that your code asks it to open. It never opens one on its own, and the transport is a plain length-framed byte stream with no encryption (see Export control self-assessment). - If you enable
persist, Aster writes the document files in the directory your code names. - Platform shells (Windows, Android, the lab and demo binaries) use operating-system APIs for windows, input and presentation. They are not part of the core and are outside the guard. The guard's scope is listed in the script.
Check it yourself
Because the runtime source is private, you check a binary rather than the source. The source-level guard (tools/trust/no-io-check.sh) is an internal control; its result for each release is stated in the release notes.
Run the binary under your own monitoring: on Linux strace -f -e trace=network,file aster ..., on Windows Process Monitor or an outbound firewall rule, in a container with no network. A build of the default runtime should make no network calls and write files only to paths your code names. Check the licence inventory and SBOM in the release for the dependency list.
Last verified
On 2026-11-11, at the commit that introduced the guard, tools/trust/no-io-check.sh printed PASS (source scan, gating check and cargo tree with default features for the five guarded crates), and cargo test -p aster-appkit passed with net-sync and persist enabled for the crate's own tests. Re-run the script for any version you rely on; this line is a dated record, not a guarantee.
Limits of this claim
- The guard is a source and dependency check, not a proof about every compiled byte. It does not inspect your application or the operating-system libraries beneath the Rust standard library.
std::thread, clocks and memory allocation are used and are not considered data egress.- Sandboxing at runtime (seccomp, firewall) remains the stronger control and is compatible with Aster.
- The platform shells and tools in the repository are not covered. Do not link them into a product that needs the claim.
- The project website and repository host are separate from the software and have their own privacy practices, which are not covered here.
See also: Aster Trust Center for the Trust Center index.