Ecosystem philosophy, not a universal product policy

Ecosystem privacy model

Different software needs different disclosure

Shared principles establish questions every project should answer. They do not apply one unsupported claim to browser tools, desktop software, AI runtimes, and libraries.

Processing location

A product may describe one or more processing models:

• Browser-local: supported work happens inside the browser.
• Desktop-local: work happens in an installed local application.
• Local model inference: models execute on the user's device.
• Hybrid: local and remote processing are both involved.

No single model is asserted for every Secure Tools product.

Network behavior

Product documentation should distinguish ordinary and runtime-specific requests, including:

• static website delivery for HTML, CSS, JavaScript, and local assets;
• model or application downloads;
• optional remote resources or user-initiated actions;
• application update checks; and
• runtime network activity required by a feature.

Storage

A product may use memory, local files, browser cache, browser application storage, or installed-application storage. It should explain what is retained, why, for how long, and which controls are available.

Telemetry

Every product should state whether telemetry exists and, when it does, whether it is optional, enabled by default, or required. “Local-first” is not a substitute for this disclosure.

Product-specific guarantees take precedence

Release-specific documentation is the source of truth for processing, network, storage, telemetry, supported formats, dependencies, and limitations. Ecosystem language must not be used to overstate those guarantees.