1. Scope
SSH Studio is an iPhone and iPad app providing SSH terminals, file management, code editing, media previews, and extensions. This policy explains the information the app stores on your device or sends to perform its functions, and the controls available to you.
Your chosen SSH server, Files provider, extension registry, and any AI or sign-in services connected to extensions may process information in their own ways. Local storage in the app is separate from those services' retention and use of information.
2. Server connections and file operations
When connecting through SSH, the app sends your username and authentication requests to your selected server. Password authentication takes place within the SSH connection, and public-key authentication signs requests using the private key on your device. The private key itself is not uploaded to the server for authentication.
Commands and input entered in the terminal, paths requested through SFTP, and file content transferred through SFTP are processed on your selected server. When you use an SSH tunnel, traffic to the service you connect to may pass through that server.
The app does not automatically upload this material to an operator-controlled server for advertising or usage analytics. The server operator manages retention and deletion of the server's access logs, files, and account information.
Local projects are stored on your device. Folders selected through Files are edited in place rather than as separate copies, so changes may be sent to the provider's service if cloud synchronization is enabled.
3. Information stored on your device
| Information | Purpose and storage |
|---|---|
| Server profiles | Host, port, username, starting path, approved server key fingerprints, and connection settings are stored for future connections. |
| SSH credentials | Passwords, private keys, and private-key passphrases are stored in the device's Keychain. They are not synchronized to other devices and are configured so that new reads from Keychain are unavailable while the device is locked. |
| Projects and settings | The app stores local project files, registered folder information, editor and keyboard settings, and recent or favorite folders. |
| Snippets and command history | The app stores snippets you create. Command history is off by default; when enabled, it retains up to the 100 most recent commands submitted through the command input field. It does not automatically record all terminal input and output. |
| Local extensions | Downloaded extension packages and installation information are stored on your device. Installation and activation are separate steps. |
| Media cache | The app copies images, video, audio, and PDFs to your device for preview without changing the original. Each workspace uses up to 512 MiB, with cache entries from closed tabs removed first. |
Passwords or tokens you enter directly in a profile's startup command, snippets, or project files are not automatically separated into Keychain items. The command history's secret-value filter cannot identify every secret, so check sensitive values before entering or recording them.
Unsaved edits used for reconnection recovery are kept in memory and are not automatically saved to disk. They may not be recoverable if the app process terminates.
4. Open VSX and extensions
Searching for extensions sends your search terms to Open VSX. Installation requests the extension ID, version, and target platform, then downloads packages from Open VSX or an allowed package CDN. Local extension packages are downloaded on your device; server extension packages are downloaded on the connected SSH server.
Recipients of these requests can see the source IP address and request information. Settings that avoid permanently storing request history on your device do not prevent external services from retaining their own logs.
Extensions running on your device
Activated local extensions can read your selected project and edit or save open documents. The current local extension runtime, preview content security policies, and native bridge restrict external network requests and use nonpersistent web data stores. These measures are not a complete security boundary that guarantees the behavior of all third-party code.
Extensions running on your server
Server extensions run with your SSH user's permissions and can access server files, processes, and networks. The runtime also provides extensions with a session identifier and a runtime identifier derived by hashing the server storage path. Requests may be sent to Node.js distribution services to obtain required server executables.
If an extension connects to an external service, such as an AI or sign-in service, it may send code, file content, chats, and account-related information to that service. Server extension files, state, and authentication information are managed separately from the app's device Keychain.
Check each provider's official policy and the relevant feature settings for retention periods, purposes of use, user association, and tracking. The absence of the app's own automatic analytics uploads does not mean that an extension's own collection or transmission is blocked.
- Open VSX and related package providers: Eclipse Foundation Privacy Policy
- Node.js-related providers: OpenJS Foundation Privacy Policy
- Extensions, AI and sign-in services, and Files providers: the official privacy policy of the provider you choose
This policy's descriptions of device storage and deletion do not apply in place of external providers' server logs or account information. Use of external services and deletion of their information are governed by each provider's policies and procedures.
5. Retention and deletion
- Server profiles: Deleting a profile deletes that profile on your device and the associated SSH credentials managed by the app. Removing the app alone does not guarantee that Keychain items are deleted, so delete profiles before removing the app.
- Projects and external folders: You can manage local projects in Files. Closing a workspace releases the app's active access to an external folder, but its registered folder information remains. This does not delete files stored by the provider.
- Command history and snippets: You can delete these in the terminal tools. Turning command history off does not delete existing entries.
- Media cache: Closing a tab may leave cached content for reopening. Closing the workspace or choosing to clear the cache deletes its owned cache. The cache uses device file protection and is excluded from backups. The OS may clean up cache left after a force quit; immediate deletion is not guaranteed.
- Extensions: Disabling an extension leaves its installed package in place. Server extension installation files and state, and external service records, must be managed separately on that server or service.
Deleting a profile or removing the app does not delete original files on an SSH server, cloud files held by a Files provider, or account and conversation history held by external services. Unlike media caches, not all ordinary project and settings files are excluded from backups. OS backups and Files synchronization depend on your settings and the provider's policies.
6. Advertising, diagnostics, and sharing you choose
The current app has no built-in advertising network, advertising tracking, or automatic uploads for usage analytics. This statement does not describe the data practices of every server, Files provider, extension, or AI service you connect to.
Network diagnostics check a connection target you choose. Copying version information for support includes only the app version and iOS or iPadOS version; server profiles, file paths, and command history are not attached automatically.
If you choose to share files, terminal output, screens, or diagnostic information, that content is sent to your chosen recipients and apps. Before sharing, check for passwords, tokens, personal information, and internal server addresses.
7. Support requests and this website
Email support
When you contact us by email, your sender email address and the message and attachments you provide are delivered to the support mailbox. The operator uses this information only to respond to your inquiry, investigate and resolve the issue, and carry out follow-up needed for that inquiry. It is not used for advertising or user analytics.
Information is retained only until the inquiry and necessary follow-up are complete. Once it is no longer needed, the operator promptly and permanently deletes copies in the operator-managed mailbox, saved attachments, and trash. If another law requires retention, only the required information is kept separately for the required period, and the reason and retention period are explained.
Include only the minimum information needed to resolve your issue. Do not send messages or attachments containing passwords, private keys, tokens, personal information, or internal server addresses. The support address is reagan9@naver.com and uses NAVER Mail. See the NAVER Privacy Policy for the mail provider's processing. Deletion from the operator's mailbox is separate from the provider's retention of its own records and backups.
Website visits
This static website does not include its own analytics scripts, advertising, contact forms, external fonts, or embedded third-party content. It is hosted on GitHub Pages. Request information and logs, including IP addresses processed by the hosting provider to serve pages, are separate from the app's device storage and are subject to the GitHub Privacy Statement.
8. Requests for access, correction, deletion, or restriction of processing
To request access to, correction or deletion of, or restriction of processing for your information held by the operator, contact reagan9@naver.com. Identity checks use only the minimum information necessary, such as your existing inquiry email address. We do not request copies of identity documents or unnecessary credentials.
The operator reviews your request and informs you of the outcome in accordance with applicable law. If all or part of a request cannot be fulfilled, for example because retention is legally required, we explain the reason and the scope affected.
You can directly manage device-only information through the app's profile, terminal tools, and workspace menus, and through Files. The operator does not access your device, SSH server, or external services without authorization. For information held by your chosen server, Files provider, extension, AI service, or sign-in service, contact its administrator or provider.
9. Contact and policy changes
The operator and privacy contact is 구래건 / Reagan Koo, reachable at reagan9@naver.com. Send privacy questions, rights requests, and concerns to this address.
This policy takes effect on October 12, 2026. If it changes, the changes and effective date will be posted on this page. Important changes to the handling of personal information will be announced on this website before they take effect, with an in-app notice when needed.