Legal

Privacy.

Short by design. The website and the desktop app collect different things; both pages are documented here.

Last updated 2026-10-27.

Two products, two privacy surfaces

This page covers the website and the desktop application. Linux and Windows 1.1.0 installers are offered from the download page. macOS is not in this release. The source repository stays private. The desktop statements below describe the public 1.1.0 Linux release.

What this website collects

The contact form collects a name, email address, and message when you send one. Hexify Technologies Ltd emails that message to hello@bastionterminal.com and sends you a short confirmation. This website does not keep a copy. We do not run analytics scripts, set cookies, or embed third-party trackers.

If we add analytics in the future, it will be Cloudflare Web Analytics or a self-hosted Plausible instance — both cookie-less and configured to not identify individual visitors. Any change to that posture will be reflected on this page.

This site is served at www.bastionterminal.com. This repository does not add analytics scripts, cookies, or third-party trackers. The host may keep request logs under its own policy. A retention period is not stated here.

What the desktop application stores

In the development source, hosts, groups, tags, snippets, and settings are stored in a local SQLite database. SSH private keys are stored in the operating system keychain (Credential Manager, Keychain, or Secret Service). Passwords entered for an SSH connection are held in memory for that session. Terminal scrollback for a session is kept in memory.

No crash reporter was found in that source. A telemetry flag is stored in the local settings row, and the settings save path forces the flag off. No code was found that transmits the flag. This is a source review, not a third-party audit.

Where the data lives

Bastion does not operate an account system or a sync service for host data. Host records stay in the local database unless you turn on an optional AI provider.

When AI is enabled, the desktop app sends the request, including the context attached to that question, directly to the provider you configure. Version 1.1.0 calls OpenAI, Anthropic, Google Gemini, OpenRouter, or an OpenAI-compatible endpoint you set. Bastion does not proxy those calls through a Bastion server. Version 1.1.0 builds a redacted context pack before the call. That redaction was not independently audited, so do not treat it as a guarantee that every secret is removed.

Update checks read latest.json from downloads.bastion.hexifytech.com. That check does not upload the host list.

Sync

Version 1.1.0 does not sync hosts or keys to another device. A future sync design has not been confirmed, so this page does not describe one.

AI providers

AI assistance is in 1.1.0. Ask, Fix, and Plan are the modes in the panel. Fix and Plan show proposed commands and wait for approval before those commands run. The question itself is sent to the configured provider when you submit it. An OpenAI-compatible endpoint can point at a server you run. Named offline products such as Ollama are not a separate integration in this build.

Reporting an issue

If you believe this site or the desktop application leaks data in a way not described here, please use the contact form. Messages are sent to hello@bastionterminal.com. This page does not promise a response time.

Changes to this policy

If we make material changes, we will update the "Last updated" date and add a note to the changelog. Non-material changes (typos, clarifications) will not be flagged.