Privacy Policy

This policy explains what data Pier collects, how it is used, and what controls you have.

Last updated: February 26, 2026

What We Collect

Pier is designed to run locally. The website does not require account creation. The CLI, bridge, and extension store configuration data on your machine (such as host-to-workspace mappings, bridge settings, and local session metadata) so Pier can route terminals correctly. On production website domains, Pier also collects website pageview analytics with PostHog.

How Data Is Used

Stored local data is used only to provide product functionality: starting the local bridge, authenticating local requests, and opening terminal sessions in the mapped project directory. Website analytics data is used to understand documentation and landing-page usage trends.

Website Analytics (PostHog)

Pier website analytics uses PostHog and is limited to pageview events. Autocapture, session recording, and person profiles are disabled. Analytics is enabled only on approved production hostnames.

Data Sharing

PostHog processes website analytics events for Pier. Pier does not send terminal output, workspace paths, bridge tokens, or CLI/extension runtime data to PostHog. If you install from third-party platforms such as GitHub or the Chrome Web Store, those services may collect their own usage data under their own policies.

Security

The local bridge listens on localhost and expects an access token from trusted clients. You are responsible for securing your development machine and rotating credentials if they are exposed.

Your Controls

You can remove local Pier data at any time by deleting Pier config files, host mappings, and extension storage from your machine. You can also uninstall the CLI and extension to stop all processing.

Changes to This Policy

This policy may be updated as Pier evolves. Material updates will be reflected by updating the date at the top of this page.

Contact

For privacy questions, open an issue in the Pier repository on GitHub.