Last updated: September 24, 2026. This Privacy Policy details the data handling, storage practices, and network communications of the Loopia CLI executable and documentation website.
The Loopia CLI binary contains zero tracking code, zero analytics SDKs, and zero telemetry beacons. Developer and agent workflows remain completely private. The application does not collect usage metrics, IP addresses, execution timestamps, or error reports back to any SpaceCorps server. The only network requests made by the tool are outbound HTTPS requests made directly to the Loopia XML-RPC API endpoint (https://api.loopia.se/RPCSERV) to fulfill user-initiated operations.
Authentication credentials (usernames and passwords) are sensitive secrets. Loopia CLI strictly refuses to store passwords in plaintext configuration files by default. Instead, credentials are delegated directly to the secure credential store provided by the host operating system: macOS Keychain Services via the native security subsystem, Windows Data Protection API (DPAPI) encrypted under user-specific credentials, or the freedesktop.org Secret Service daemon via libsecret on Linux.
Non-sensitive configuration metadata—specifically account alias names, username handles, optional customer numbers, and custom endpoints—is stored locally in an owner-restricted YAML file (chmod 0600 on POSIX platforms) located within your standard system configuration directory (~/Library/Application Support/loopia on macOS, ~/.config/loopia on Linux, or %APPDATA%\loopia on Windows). This file can be inspected, backed up, or deleted at any time.
This documentation website is hosted as a static site on GitHub Pages. It contains no tracking scripts, no third-party cookies, and no personal data collection mechanisms. Standard web server access logs are handled directly by GitHub in accordance with GitHub's standard Privacy Statement.