Modern SSH client family for Android, Linux, macOS, Windows, and BSD. Open-source and privacy-focused.

Privacy Policy

Your privacy is our priority. Here's exactly what we do (and don't do) with your data.

TL;DR: TabSSH doesn't collect, store, or transmit any of your personal data. Everything stays on your device.

Our Privacy Promise

TabSSH is built with privacy as a fundamental principle, not an afterthought. We believe your SSH connections, server credentials, and usage patterns are private and should remain under your control.

What Information We Don't Collect

We collect zero personal information. This includes:

  • 📱 Device Information: No device IDs, hardware specs, or system information
  • 🌐 Usage Analytics: No app usage statistics, feature usage, or behavioral tracking
  • 🔐 SSH Credentials: No usernames, passwords, SSH keys, or connection details
  • 📊 Connection Data: No server addresses, connection logs, or command history
  • 📍 Location Data: No GPS coordinates, IP addresses, or network information
  • 🆔 Personal Identifiers: No names, email addresses, phone numbers, or account data

Same Privacy Promise on Both Platforms

Both TabSSH Mobile (Android) and TabSSH Desktop (Linux/macOS/Windows/BSD) make the same zero-data-collection commitment. The mechanisms differ slightly per platform:

  • Mobile: No analytics SDKs, no crash-reporter SaaS. Encryption uses Android Keystore. Sync via Storage Access Framework — you pick the storage app.
  • Desktop: No telemetry libraries, no analytics endpoints. Encryption uses the OS keychain (macOS Keychain, Windows Credential Manager, Linux Secret Service). Sync via filesystem watch + your existing sync app (Nextcloud client, Syncthing, rclone, etc.).
  • Both: Open-source, MIT-licensed, auditable. The encrypted sync format is identical, so a sync blob written by mobile decrypts on desktop and vice versa (when desktop sync ships).

No Google Services Dependency

TabSSH does not require Google Play Services or any other Google component.

  • Cloud sync uses Storage Access Framework (SAF): when you turn sync on, you pick whichever storage provider you already have installed (Nextcloud, Dropbox, OneDrive, Google Drive, local storage). TabSSH never talks to any cloud service directly.
  • Sync content is end-to-end encrypted with AES-256-GCM (PBKDF2 100,000 iterations). The storage provider only ever sees encrypted blobs.
  • Cloud host import (DigitalOcean / Hetzner / Linode / Vultr) is opt-in only — you provide an explicit token; tokens live in the Android Keystore, never in the database.
  • No auto-discovery of AWS / GCP / Azure / any cloud — by design.
  • Runs perfectly on de-Googled ROMs (LineageOS, GrapheneOS, /e/OS, CalyxOS).

Open Source Transparency

TabSSH is completely open source, which means:

  • Auditable Code: Anyone can review our source code to verify our privacy claims
  • No Hidden Features: No secret data collection or tracking mechanisms
  • Community Oversight: The open source community helps ensure we maintain our privacy standards

Contact Us

If you have questions about this privacy policy:

Last Updated: April 28, 2026

This policy is effective immediately and applies to all versions of TabSSH.