Support

Three routes, depending on what you need. All of them reach the same person.

How something works

The manual covers each part of the app - connecting, SSH keys, SFTP, snippets, port forwarding, the sessions that survive a dropped connection, and every setting. It is written against the current release and gets fixed between releases, so it is the first place to look.

The changelog lists every release and what changed in it, which is the quickest way to tell whether something you noticed was deliberate.

A bug, or something you want

Both go in the public issue tracker. It is the quickest route, and it lets the next person with the same problem find the answer instead of asking again.

What makes a bug report answerable:

• The app version, from Settings, at the bottom under About.
• What you did, what happened, and what you expected instead.
• The server side, if it is relevant: what it runs, and which shell.
• Anything on screen when it went wrong - with hostnames and usernames removed, or with the app's Anonymize option turned on, which replaces them for you.

Anything you would rather not write in public

Mail [email protected] and it reaches the developer directly. That includes a security report, which should go there rather than into the tracker - please give the version and enough detail to reproduce it, and time for a fix before it goes anywhere public.

One person answers all of these, so how long it takes varies. Every message is read.

What the app does with your data

Your device connects straight to your own servers - terminal contents, keys and transferred files never pass through a machine belonging to Termphin. What may be collected, and what is not, is listed in the privacy policy; the terms and the about page name who is responsible.