Security — ShieldPress Terminal
Last updated: September 6, 2026
Design goals
ShieldPress Terminal is local-first:
- No ShieldPress cloud account for SSH sessions.
- Server profiles live in on-device SQLite.
- Passwords, private keys, and passphrases are stored in the device SecureStore / Keychain (not in plain app files).
- Optional encrypted backups — manual or, on Lifetime Premium, automatic on a schedule you choose — are protected by a password you choose (AES-GCM + PBKDF2). An automatic backup’s password lives only in the device SecureStore / Keychain, never in the app database or in the backup file.
- Optional session recordings (Lifetime Premium) capture a terminal window’s output to a local file for playback; treat a recording the same as terminal scrollback — anything sensitive that appeared on screen (including command output) is captured, so only share a recording with people you’d show that session to directly.
What we do not do
- We do not sync your credentials to our servers.
- We do not operate a cloud backup of your server list.
- We do not use advertising or analytics SDKs that profile your usage.
- Gift-code redeem (if used) only records a code identifier for one-time burn — not your SSH secrets.
Your responsibilities
You are solely responsible for:
- Choosing strong passwords / protecting SSH keys and backup passwords.
- Deciding which hosts to connect to and what commands to run.
- Physical security of your phone/tablet and OS lock screen.
- Enabling optional biometric lock if you want extra protection.
- Not sharing exported backups or gift codes with untrusted parties.
- Keeping the OS and the app updated.
Compromise of your device, OS account, stolen backup file + password, or leaked private key is outside the developer’s control.
Network
SSH/SFTP traffic goes to hosts you configure. Use trusted networks when practical. Host-key verification (known hosts) helps detect server identity changes — review warnings carefully.
Incident / questions
Email support@shieldpress.net. Do not send live passwords or private keys in email.
See also: Privacy Policy · Disclaimer