BoostSSH

EFFECTIVE 16 NOVEMBER 2026

Privacy policy

BoostSSH does not collect your personal data for the developer. It does not include developer analytics, advertising, or a developer-operated service that receives your saved connections or terminal sessions.

This policy applies to the BoostSSH Android application, package com.splitice.boostssh, published through the X4BNet project. Optional services and destinations you choose are described below.

Data on your device

BoostSSH stores the connections, hostnames, usernames, identities, private keys, passwords, groups, port forwards, preferences and local logs that you create or use. Saved credential secrets are protected using Android Keystore-backed encryption. This information is used to provide the app’s terminal and connection-management features; it is not sent to the developer.

You control any files, screenshots, logs or credentials you deliberately export or share using Android’s file and sharing controls. Protect those files and choose their recipients carefully.

Kubernetes data

Kubernetes profiles, kubeconfig credentials, groups, preferences, drafts and operation records are stored separately on your device with Android Keystore-backed encryption. Helm draft values and registry credentials are also encrypted locally. Kubernetes data is excluded from Google Drive sync, shared collections and SSH backup files.

Connections to your servers

When you connect, BoostSSH communicates directly with the server or service you specify and sends the authentication information and commands necessary for that connection. The remote operator may retain connection metadata, commands or other information under its own policies. SSH and Mosh encrypt sessions; Telnet does not provide encrypted transport.

Optional Kubernetes features communicate with the cluster and identity provider you configure. Browsing Helm packages can send your search query to Artifact Hub. These are user-requested connections, not data collection by the BoostSSH developer.

Optional Google Drive backup and sync

You can use local terminal features without connecting a Google account. If you enable Drive backup, Google handles account selection and authorization. BoostSSH uses the selected account identifier locally and keeps Google access tokens in memory; Google Play services manages authorization credentials.

Personal SSH connection backups use Google Drive’s application-data storage. Backup contents are encrypted on your device before upload. The developer has no access to your Drive backup or its decryption keys. Google stores the encrypted files and processes the account, access, file and network metadata needed to provide its services.

Personal backup requests the drive.appdata permission. Optional shared collections request the broader drive permission to discover and synchronize files created by different members. BoostSSH’s collection operations are confined to the collection folders it manages. Google’s consent screen describes the permissions you are granting; enabling personal backup does not by itself enable team sharing.

Shared collections

A shared collection combines Google Drive folder permissions with a separate collection code. Collection contents are encrypted before upload and decrypted on members’ devices. Members who have the required access and code can read the information you publish, including credentials if you choose to publish them. Invitations and Drive permissions use the recipient email address you enter and expose membership information to Google and relevant collection participants.

Revoking access or rotating a collection key can restrict future access. It cannot erase copies that a previous recipient already saved. Only share information with people you trust to receive it.

Recovery and Android services

Keep your recovery key in a safe place. The developer cannot recover it or decrypt your backup for you. BoostSSH can store a small account-bound recovery capsule using Android Block Store. Cloud recovery is enabled only when Google reports end-to-end encryption is available; otherwise the app uses the supported device-transfer path and your saved key is needed for cloud recovery. Your device and Google account settings affect whether recovery is available.

The app excludes its connection database and credential files from Android Auto Backup. Google Play, Google Play services and Android may process their own service or device data under Google’s policies and your settings.

Retention, deletion and your controls

Local records remain until you delete them or remove the app’s local data. Uninstalling the app does not automatically delete files already stored in your Google Drive. Use BoostSSH’s backup/account controls to pause sync, disconnect, remove an account or delete a personal backup. You can also revoke BoostSSH access through your Google account and manage the app’s stored data through Google Drive settings.

Backup history normally retains recent snapshots and daily recovery points for up to 30 days. Shared files are controlled by the collection’s Drive owners and permissions. Local exported backups and recipients’ copies remain wherever you saved or shared them. Google’s trash and retention rules may also apply.

Google API data

Information obtained through Google APIs is used only to provide the backup, synchronization, recovery and sharing features you request. BoostSSH follows the Google API Services User Data Policy, including its Limited Use requirements. The developer does not sell this data or use it for advertising.

This website

These pages use no analytics scripts, advertising, tracking cookies or contact forms. GitHub Pages hosts the website and may process ordinary request and security logs under the GitHub Privacy Statement. Google services are subject to the Google Privacy Policy.

Changes and contact

Changes to this policy will be posted here with an updated effective date. For privacy questions about BoostSSH, contact me@mheard.com. Please do not send passwords, private keys, recovery codes or other connection secrets.