Privacy policy
Android local-workspace builds with cloud accounts and purchases disabled
Your terminal, your servers
Anchor SSH is developed by O. Faruk Bayrak, operating as OFCode Dev. This policy explains the local SSH workspace. Cloud accounts, subscriptions and cloud backups are not available in this release. You do not need an Anchor account to connect to your own server.
The app does not send your SSH credentials, commands, terminal output or connection library to an Anchor-operated server. There is no advertising or third-party analytics or crash-reporting SDK. The optional product-analytics setting is off by default and sends no events while the cloud service is unavailable.
Connections and remote data
When you connect, the app sends your SSH username, authentication exchange, terminal input and terminal-size changes directly to the server you choose, using an encrypted SSH connection. Your private key remains on your device; key authentication sends a cryptographic proof. Password authentication sends the password inside the encrypted connection to your chosen server.
That server can see your network address and the information you send, and may keep authentication logs, shell history, files and tmux sessions according to its own configuration. DNS and network providers may see connection metadata. Anchor does not control those providers or your server's retention practices. Verify the host-key fingerprint before trusting a server.
A saved tmux session can continue running after the app disconnects or is uninstalled. Deleting a local profile does not terminate a remote process or erase server-side history. Manage that data on the server.
Data stored on your device
The app saves host names and addresses, ports, SSH usernames, groups, favorites, trusted host-key fingerprints, session identifiers, command drafts or history, saved commands and preferences so you can return to your workspace. Workspace metadata is encrypted locally. Remembering SSH passwords, private keys and key passphrases is optional and off by default; retained credentials use Android's protected credential storage.
Terminal output is kept in the app's terminal buffers during use. Clear removes the visible local terminal buffer; it does not erase the remote server's history or any log you already exported.
Clipboard, files and sharing
The app reads the system clipboard when you choose Paste. Copy places the selected text or terminal screen on the system clipboard, where your operating system and other permitted apps may access it. Android clipboard protections are used where supported. A timed clear attempt cannot guarantee removal after the app is stopped or the clipboard changes.
A key import reads the file you select. Exporting a terminal log, sharing text or saving an encrypted backup happens only when you request it. The destination app or storage provider then handles that copy. Review terminal logs before sharing: they can contain secrets. Workspace backups exclude SSH credentials and trusted host-key fingerprints.
Device permissions and protection
Network access is used for SSH connections. Optional app lock asks Android to authenticate you with biometrics or your device credential; Anchor does not receive your fingerprint, face template or device PIN. Screen capture protection is enabled by default and can be changed in Settings. Files are accessed through the system picker or share interface. The app does not request access to your contacts, precise location, camera or microphone.
Encryption and platform protections reduce risk but do not guarantee security on a compromised device or server. Keep your device secure and retain an independent backup of important information.
Retention and deletion
Saved profiles, credentials, commands and preferences remain locally until you remove them or clear the app's storage. Uninstalling removes the app's private Android storage. Exported files, shared copies and remote server data remain under your control or the recipient's control and must be deleted separately. Android backup of app data is disabled.
There is no Anchor cloud account to delete in this release. Clearing local storage or uninstalling is permanent for local data unless you have your own usable backup. It does not stop remote tmux processes or remove data from a server.
Support and external services
If you email support, we receive your email address and the message or attachments you choose to send. We use them to respond and resolve the issue. Support correspondence is retained only as needed for that purpose or applicable legal and security obligations. You can request deletion by contacting the address below. Never send passwords, private keys or sensitive terminal logs.
Google Play handles app distribution and may provide the developer with aggregated installation, performance or feedback reports under Google's policies. The app includes Google Play Billing integration, but checkout is disabled in this release. Opening an external website or email app is subject to that service's privacy practices. The privacy and support website is hosted on GitHub Pages, which may process request metadata such as network addresses under GitHub's privacy statement.
Children and policy updates
Anchor SSH is a server administration tool intended for adults. It is not directed to children. We do not knowingly solicit children's personal information.
Any change to the app's data practices will be reflected in an updated policy. Cloud account or payment features require additional disclosures and are not enabled by this policy.
Contact
For privacy questions, support-data deletion requests or security reports, contact O. Faruk Bayrak (OFCode Dev) at ofaruk1991@gmail.com. Include only the information needed to describe the request.
Contact the developer about privacy.
External policies: Google privacy policy and GitHub general privacy statement.