# RelaySSH Privacy Policy
**Effective date:** September 12, 2026
**Last updated:** October 2, 2026
RelaySSH (the “App”) is developed and published by **Toni Nedyalkov, publishing as Diki Software Solutions** (“Developer,” “we,” “us,” or “our”). This Privacy Policy explains how RelaySSH accesses, uses, stores, transmits, and protects information when you use the App.
RelaySSH is an SSH terminal and SFTP client. It connects directly from your device to computers and services that you select. The Developer does not operate an intermediary SSH service and does not receive your SSH credentials, terminal sessions, or transferred files through a Developer-operated server. Optional artificial-intelligence features communicate directly with the curated official OpenAI, Anthropic, or DeepSeek API selected by you, using an API key supplied by you. Voice transcription and speech generation currently use OpenAI.
## 1. Information RelaySSH Handles
### 1.1 Saved hosts and connection configuration
When you create a host, RelaySSH stores information you provide, which may include a display name, hostname or IP address, port, username, authentication method, jump-host relationship, tags, favorite status, and an optional login script and its execution settings.
This information is stored locally on your device so that RelaySSH can display saved hosts and establish connections you request. Hostnames, IP addresses, usernames, and login scripts may constitute personal or sensitive information depending on their contents and context.
### 1.2 Authentication information
RelaySSH may store SSH passwords, private keys, and private-key passphrases that you choose to save. These credentials are stored using the operating system’s protected credential storage. The App also stores trusted SSH host-key information locally to help identify unexpected server-key changes.
Authentication information is used only to connect to hosts selected by you. During password authentication, the password is communicated to the selected SSH server within the encrypted SSH connection. During public-key authentication, the private key is used locally to create authentication proofs and is not intentionally uploaded to the selected server.
### 1.3 Terminal and command information
RelaySSH processes text you type, terminal output received from connected hosts, command history observed or imported for autocomplete, snippets, snippet-variable values, and optional login scripts. This information is used to provide terminal display, input, autocomplete, snippets, session previews, and related functionality.
Terminal contents are ordinarily processed in memory and remain on the device except when:
1. you send commands or other input to a selected SSH server;
2. you copy terminal text to the system clipboard;
3. you choose an optional AI feature and authorize relevant context to be transmitted to a configured provider; or
4. the remote host itself records commands, output, or connection activity under policies controlled by that host’s owner or administrator.
### 1.4 Files and file metadata
When you use SFTP, RelaySSH accesses files and folders that you select through the operating system’s file picker and files available on the selected remote host. File names, paths, sizes, timestamps, contents, and transfer status are processed as necessary to browse directories and perform uploads or downloads.
Uploaded file contents are sent directly to the SSH/SFTP server selected by you. Downloaded file contents are written to the destination selected by you. RelaySSH does not upload these files to a Developer-operated storage service.
### 1.5 Optional AI-provider features
RelaySSH provides optional AI assistance, speech transcription, speech generation, and terminal-bound agent functionality through a curated list of the official OpenAI, Anthropic, and DeepSeek APIs. Provider endpoints, API protocols, and model identifiers are fixed by the App and cannot be supplied by users. These features are disabled until you supply an API key for the relevant provider and initiate or authorize use. Allowing a provider to receive terminal context and allowing it to participate in autonomous actions are separate per-provider settings.
Depending on the feature, selected model, and your choices, RelaySSH may transmit the following directly to the official OpenAI, Anthropic, or DeepSeek API:
- prompts, questions, and conversation history;
- bounded portions of recent terminal output;
- the selected host’s display or connection context, which may include a username, hostname or IP address, and port;
- proposed commands, tool arguments, objectives, execution results, and reviewer requests;
- microphone audio submitted for speech transcription; and
- text submitted for speech generation.
The selected provider also receives ordinary request and connection information needed to operate its API, which may include the source IP address, request time, request identifiers, model and token usage, and information associated with the provider account or API key used for the request. Providers may use this information for service delivery, billing, abuse prevention, security, and legal compliance under their applicable terms and privacy practices.
RelaySSH applies content-safety screening to AI requests and generated responses. A local prefilter runs first. When OpenAI is selected, content that passes the local prefilter may be sent to OpenAI's moderation endpoint. When Anthropic or DeepSeek is selected, RelaySSH may make a separate structured classification request to that same selected provider. RelaySSH does not send Anthropic or DeepSeek conversations to OpenAI for moderation. Safety-classification requests use the API key you supplied for the selected provider and may contribute to that provider's usage accounting, except where a provider offers moderation without charge.
Full autonomous mode is separately gated in Settings and requires affirmative acceptance of an in-app warning. Each selected provider must also be explicitly allowed to receive terminal context and participate in autonomous actions. When enabled and when you authorize a run, bounded terminal context and proposed actions may be sent to the selected planner and reviewer providers, and qualifying commands may be executed without approval before every individual command. RelaySSH currently restricts unattended execution to commands accepted by its conservative read-only policy and an independent AI review. AI systems and command classification can make mistakes and cannot guarantee safety or confidentiality.
For OpenAI Responses API requests, RelaySSH sets `store: false`. This option does not apply to every protocol or provider and does not necessarily eliminate all processing or retention. Each provider processes information under the account, organization, service terms, data controls, and retention practices applicable to the API key you supply. Review those terms before enabling a provider. For OpenAI, see [OpenAI’s policies](https://openai.com/policies/) and [OpenAI API data controls](https://platform.openai.com/docs/guides/your-data). For Anthropic, see [Anthropic’s privacy information](https://www.anthropic.com/legal/privacy). For DeepSeek, see [DeepSeek’s privacy policy](https://cdn.deepseek.com/policies/en-US/deepseek-privacy-policy.html).
Do not submit passwords, private keys, authentication tokens, confidential file contents, or other information you do not want processed by the selected provider. RelaySSH attempts to limit sensitive disclosure but cannot reliably identify or redact every secret contained in terminal output or user-provided text.
#### Reporting harmful AI output
Each AI response in the general assistant and terminal assistant includes an in-app report control. If you choose to submit a report, RelaySSH sends the report category, up to the first 4,000 characters of the selected AI response, up to 1,500 characters of any proposed command displayed with that response, the configured model identifier, the AI surface from which the report was submitted, the device platform, the submission time, and up to 500 characters of your optional comment to the Developer's HTTPS report receiver hosted as a Google Apps Script web application. The receiver forwards the report through Google Mail to dikisoftwaresolutions@gmail.com. RelaySSH does not add your prompt, conversation history, terminal transcript, host address, username, credentials, advertising identifier, or other device identifier to the report. Review the selected response and proposed command before sending because text produced by an AI provider could itself contain sensitive information.
Submitting an AI report is voluntary. Google may process ordinary connection metadata, such as the source IP address and request time, when operating the Apps Script and Gmail services. The Developer uses reports to investigate harmful or policy-violating generated content, improve safeguards, and address abuse. Reports are retained only as long as reasonably necessary for moderation, abuse prevention, legal compliance, and resolving related complaints.
### 1.6 Microphone audio
RelaySSH accesses the microphone only after you initiate voice input and grant the operating-system microphone permission. Audio is captured to provide the requested transcription and is transmitted to OpenAI when you submit the recording for transcription. RelaySSH does not use the microphone for advertising or background surveillance and does not intentionally retain microphone recordings as permanent local files.
### 1.7 Diagnostic information
RelaySSH maintains a bounded diagnostic log on the device to identify failures and application lifecycle events. Diagnostic records may include a timestamp, severity, component category, event code, exception type, and limited error detail. The log is stored using protected device storage and is limited to 500 events and 256 KiB; older entries are removed as those limits are reached.
RelaySSH is designed to exclude credentials, commands, terminal output, host addresses, usernames, remote paths, file contents, and stack traces from exported diagnostic reports. Error messages can nevertheless contain unexpected information supplied by operating systems, remote services, or third-party libraries. Review any diagnostic report before sharing it.
Diagnostic information is not transmitted automatically to the Developer. If you choose to copy a redacted diagnostic report, it is placed on the system clipboard and may then be accessible to other software according to your device’s clipboard rules.
### 1.8 Application settings and local content
RelaySSH stores application and terminal preferences, AI settings and consent version, snippets, known-host records, and similar configuration locally. Retained live sessions and terminal backbuffers are primarily maintained in application memory and may be lost when the operating system terminates the App.
### 1.9 RelaySSH Pro purchases
On Google Play distributions, RelaySSH offers an optional, non-consumable RelaySSH Pro purchase. Google Play processes the payment and supplies the App with the product identifier, purchase status, and purchase-verification information needed to grant and restore access. RelaySSH stores a local indication of the most recently verified Pro entitlement so that a temporary network or Play Store interruption does not immediately remove previously verified access. Payment-card details are handled by Google Play and are not provided to or stored by RelaySSH.
### 1.10 Advertising and consent information
RelaySSH may display a banner advertisement on its main host screen using Google AdMob. AdMob mediation may permit Google, InMobi, and ironSource Ads (a Unity service) to participate in filling the same advertising placement. Depending on your region, consent choices, device settings, and the network that serves an advertisement, these providers may process information such as the advertising identifier, App Set ID, other device or account-related identifiers made available by the advertising SDK, IP address, device and operating-system information, app identifiers, general network information, approximate location inferred from an IP address, app launches and product interactions such as taps or video views, advertisement impressions and interactions, consent signals, and diagnostic or performance information. This information may be used for advertisement delivery, personalization where permitted, measurement, analytics, reporting, frequency control, security, and fraud prevention.
RelaySSH uses Google's User Messaging Platform to request current consent information and show required privacy messages before requesting advertisements. Where required, an **Advertising privacy choices** entry appears in Settings so that you can review or change the available choices. RelaySSH configures the ironSource integration in a conservative do-not-sell mode. The availability and effect of particular choices also depend on the advertising provider and applicable law.
RelaySSH does not intentionally provide SSH passwords, private keys, API keys, terminal contents, commands, saved-host details, transferred files, microphone audio, or AI conversations to advertising providers. Advertising providers receive information through their own SDKs and process it under their respective policies. See [Google's Privacy Policy](https://policies.google.com/privacy), [InMobi's Advertising Privacy Policy](https://advertising.inmobi.com/privacy-policy), and [Unity's Game Player and App User Privacy Policy](https://unity.com/legal/game-player-and-app-user-privacy-policy).
## 2. How Information Is Used
RelaySSH uses information only as reasonably necessary to:
- establish and maintain SSH, SFTP, jump-host, and tunnel connections requested by you;
- authenticate to selected hosts;
- display terminal output and transmit terminal input;
- browse, upload, and download user-selected files and folders;
- provide autocomplete, snippets, login scripts, terminal settings, and retained-session features;
- provide optional multi-provider AI assistance and agent review, plus OpenAI transcription and speech features;
- protect against unexpected SSH host-key changes;
- enforce configured AI execution limits and safety checks;
- provide, restore, and maintain RelaySSH Pro entitlement status; and
- display, mediate, measure, and protect the main-screen banner advertisement where consent and applicable law permit; and
- diagnose failures locally.
The Developer does not sell SSH credentials, terminal contents, transferred files, AI conversations, or other personal or sensitive application content to data brokers or use that content to select advertisements. Advertising providers may process or share advertising and device information under their own policies. Some laws may classify certain advertising-related disclosures as a “sale” or “sharing” of personal information even when no money is exchanged. RelaySSH uses available consent and privacy controls, including a conservative do-not-sell or share signal for the ironSource integration, but the effect of those controls depends on the provider, region, and applicable law.
## 3. When Information Is Transmitted or Disclosed
Information may be transmitted or disclosed to the following recipients:
### User-selected servers
Connection information, authentication exchanges, commands, terminal input, and transferred files are sent to SSH/SFTP servers selected by you. The owners and administrators of those servers may independently log, store, inspect, or disclose this information. Their practices are not controlled by RelaySSH or the Developer.
### AI providers
Information described in Section 1.5 is sent only when you use or authorize an AI or voice feature. It may be sent to the official OpenAI, Anthropic, or DeepSeek API selected by you. Each provider processes information under its own terms and privacy practices. Voice audio and speech text are currently sent to OpenAI when you use those voice features.
### Google Play
Google Play processes RelaySSH Pro purchases, restores prior purchases associated with the user’s Google account, and provides purchase and entitlement status to the App. Google processes payment and account information under Google’s own terms and privacy policy. RelaySSH does not receive the user’s complete payment-card details.
### Advertising providers
Google AdMob and enabled mediation partners, currently including InMobi and ironSource Ads, may receive and process the advertising and device information described in Section 1.10 when RelaySSH requests or displays an advertisement. Which provider receives a request can vary by mediation configuration, geography, consent status, and advertisement availability. These providers act under their own privacy policies and legal obligations.
### Developer AI-safety report receiver
When you voluntarily report an AI response inside RelaySSH, the report information described in Section 1.5 is transmitted to a Google Apps Script HTTPS receiver and forwarded through Gmail to the Developer for moderation and safety handling. Google processes this information as a service provider under its applicable terms and privacy policy. No AI report is sent merely because you use an AI feature.
### Operating-system services and applications chosen by you
RelaySSH uses system file pickers, document providers, secure credential storage, audio services, and the clipboard. If you select a third-party document provider, share or paste information, or copy information to the clipboard, the selected service or receiving application may process that information under its own privacy policy.
### Legal and safety requirements
The Developer may disclose information actually available to the Developer if reasonably necessary to comply with applicable law, legal process, or enforceable governmental requests, or to protect users, the Developer, or others from fraud, abuse, security threats, or violations of law. Because RelaySSH does not operate an application backend, the Developer ordinarily does not possess your locally stored connection content.
We do not sell personal or sensitive user data.
## 4. Device Permissions and Capabilities
RelaySSH may request or use the following Android or iOS permissions and capabilities:
- **Internet and local-network access:** to connect to SSH/SFTP hosts and AI-provider endpoints selected or enabled by you;
- **Microphone:** to record audio when you initiate voice transcription;
- **Prevent-sleep behavior:** to keep the display awake while a terminal is visible when you enable that preference; and
- **File and document picker access:** to access only files and destinations you select through system interfaces, rather than requesting unrestricted storage access.
Permission availability and behavior may differ by operating-system version. You may revoke runtime permissions through device settings, although the related feature may stop working.
## 5. Data Retention and Deletion
Saved hosts, credentials, known-host keys, settings, snippets, local Pro-entitlement status, and local diagnostic information remain on your device until you remove or replace the relevant item, clear the App’s data through the operating system, or uninstall the App. Android application backup is disabled in the current build. Google Play separately retains purchase records under the terms applicable to the user’s Google account.
Deleting a saved host removes its saved host configuration and associated credentials through the App’s host-management flow. Files downloaded to locations outside the App remain in the destination you selected and must be managed using the operating system or relevant document provider. Data already transmitted to a remote SSH/SFTP server is controlled by that server’s owner. Data sent to an AI provider is retained or deleted according to the settings and terms governing the configured provider account.
Voluntarily submitted AI-content reports are retained by the Developer only while reasonably necessary to investigate the report, improve safeguards, prevent abuse, comply with legal obligations, and resolve related complaints. Reports are periodically reviewed and deleted when they are no longer needed for those purposes. You may use the privacy email in Section 12 to request deletion of a report actually held by the Developer, subject to legal, security, fraud-prevention, and record-preservation requirements.
RelaySSH does not currently provide or require a RelaySSH online account. Consequently, there is no RelaySSH cloud account to delete. If account functionality is introduced, this Policy and the App’s deletion controls will be updated before that functionality is released.
You may contact us using the information in Section 12 to request access to, correction of, or deletion of personal data actually held by the Developer. We cannot delete information held solely on your device, by a remote server administrator, by your document provider, or by an AI or advertising provider; requests relating to those systems must be directed to the relevant controller or provider.
## 6. Security
RelaySSH uses SSH encryption for SSH and SFTP sessions and requires HTTPS for configured AI-provider API communications. Saved credentials, AI-provider API keys, and the diagnostic ledger use operating-system protected credential storage. SSH host-key verification is used to help detect changes in server identity.
No security measure is perfect. The security of remote servers, user-selected commands, imported private keys, clipboard contents, device backups, rooted or compromised devices, and third-party services is outside the Developer’s complete control. You are responsible for protecting your device, API keys, SSH credentials, and remote systems.
## 7. International Processing
Remote hosts, document providers, AI providers, advertising providers, and gateways may be located in countries other than your country of residence. When RelaySSH communicates with those services, information may be processed in those jurisdictions under the provider’s terms and applicable law.
## 8. Legal Bases for Processing
Where applicable law requires a legal basis, RelaySSH processes information as necessary to provide functionality you request, including establishing connections, transferring files, processing purchases, and sending content to a provider you select. Optional AI, voice, and personalized-advertising activities rely on your choices or consent where required. The Developer may also process limited information for legitimate interests in securing the App, preventing abuse, diagnosing failures, moderating voluntarily submitted AI reports, and complying with legal obligations, provided those interests are not overridden by applicable rights.
## 9. Children’s Privacy
RelaySSH is intended for adults and is not directed to children or minors. We do not knowingly collect personal information from children. If you believe a child has provided personal information to the Developer, contact us so that we can address the request as required by law.
## 10. Your Choices and Rights
You can choose whether to save credentials, enable login scripts, use AI features, share terminal context, activate Full autonomous mode, grant microphone access, copy information to the clipboard, or transfer files. You can disable Full autonomous mode in AI Settings; doing so revokes the stored autonomous-consent version. Where an advertising privacy entry point is required, you can open **Settings > Advertising privacy choices** to review or change the choices offered through Google's User Messaging Platform. You can also reset or limit the device advertising identifier through operating-system settings where supported.
Depending on where you live, you may have legal rights concerning personal data controlled by the Developer, such as rights of access, correction, deletion, restriction, objection, withdrawal of consent, or portability. RelaySSH primarily stores data locally, so many requests can be completed directly by editing or deleting local items or clearing the App’s storage. You may submit a request using the privacy email below. Where applicable, you may also lodge a complaint with the data-protection authority responsible for your location.
## 11. Changes to This Privacy Policy
We may update this Privacy Policy when RelaySSH’s features, data practices, service providers, or legal obligations change. The “Last updated” date will identify the latest version. Where required, material changes will be communicated in the App and renewed consent will be requested before newly using sensitive information.
## 12. Developer and Privacy Contact
**Developer:** Toni Nedyalkov, publishing as Diki Software Solutions
**Privacy email:** dikisoftwaresolutions@gmail.com
Questions, privacy requests, and complaints may be submitted to the privacy email above. Include sufficient information to identify the request, but do not email passwords, private keys, API keys, terminal transcripts, or other secrets.