Privacy Policy
Outpost-Pi is open-source software. It does not provide or operate a shared relay; every relay deployment is run by its own operator.
1. Scope
This policy describes the Outpost-Pi website and the standard open-source software distribution. It does not cover a relay you run yourself or a relay run by another operator. That operator is responsible for its infrastructure, configuration, retention, and any privacy notices that apply to it.
2. Data and relay deployments
Outpost-Pi does not require an account, email registration, payment information, analytics, or tracking telemetry. Pairing keys are generated locally on your devices.
The mobile app stores paired-peer information — public keys, a name you choose, and the relay URL — in platform secure storage (iOS Keychain or Android Keystore). This data remains on your device unless you send it to your own relay as part of normal operation.
A self-hosted relay necessarily handles connection metadata and the encrypted-in-transit envelopes it forwards between paired devices. It also stores signed mesh-membership blobs in its configured database so devices restoring the same Owner key can recover their peer list. Configure retention, logging, backups, access controls, and any required notices for your deployment.
Message payloads are not application-layer end-to-end encrypted in the current MVP. The included relay source forwards payloads rather than requiring them to be persisted, but a relay operator could access plaintext in memory while forwarding. Run the relay only on infrastructure you control and use a VPN or equivalent network restriction when appropriate.
4. Security and trust model
Outpost-Pi uses TLS for relay connections and Ed25519 challenge-response during pairing. These controls authenticate paired devices and protect traffic in transit, but they do not add application-layer end-to-end encryption to message payloads.
Your relay's operator controls the server and can therefore affect its availability and privacy posture. Keep its database on persistent storage, protect administrative access, and restrict network reachability to the devices you intend to pair. See the project documentation for Docker and VPN deployment guidance.
5. Your choices
You control whether to pair a device, which relay URL to configure, and when to revoke a pairing. You can remove paired peers from the app or extension and remove the data in your self-hosted relay according to your own operational procedures.
6. Policy updates and contact
This policy may change as the project changes. The current version is published on this site. For project questions or to report a privacy concern in the software, open an issue in the Outpost-Pi repository.