Security & Privacy

Local data and credentials

Dashboard files, input settings, and dashboard state are stored on your device. Metrix.Bar requires no account and does not sync your dashboards to a cloud database. Dashboards contact their configured data services directly.

Secret inputs are stored in the operating system credential store, separately from ordinary settings. The Local API reports is_set and a null value for secrets. Dashboard scripts can read configured secrets to authenticate with services: install dashboards only from sources you trust, and never put credentials in source files, logs, or test fixtures.

Permissions and connections

Dashboards declare network origins and local file access in <permissions>. Public HTTP requests require HTTPS; plain HTTP is allowed for loopback and local networks. Direct TCP/TLS connections require explicit socket permissions. Extended desktop capabilities require the corresponding <script apis="..."> declaration. See file format for the developer contract.

File dialogs authorize the paths selected by the user. Writing requires a destination confirmed through a save dialog; a file permission declaration alone does not grant write access.

The Local API listens only on 127.0.0.1. Except for the health check, requests require the Bearer token shown in Settings → Agent. Requests carrying an Origin header are rejected. Use the address shown in settings; the preferred default port is 6387.

Usage analytics

Metrix.Bar can send anonymous usage events, app version, and operating system information. A randomly generated installation identifier groups events; it is not an account or hardware identifier. Usage events exclude dashboard metric values and credentials. Requests still reach a remote service, which receives ordinary connection information such as the source IP address.

Turn off Settings → Privacy → Share anonymous usage analytics to stop new usage events. Dashboard data requests and update checks are separate from this setting.