Privacy Policy
This policy explains how XIUSoft handles personal data when you use the LiveSSH app and LiveSSH Cloud. It applies to users in every country. The short version is in the summary table; the sections below give the detail and the rules that apply in specific regions. The XIUSoft account itself (sign-in, profile, sessions), the account pages (account.xiu.kr) and the company website (xiu.kr) are covered by the XIUSoft Privacy Policy; this policy covers what is specific to the LiveSSH app and LiveSSH Cloud.
Last updated: 2026-10-09 · Effective date: 2026-10-09 · Version: 2.2
This is the previous version (2.2). It applies until 2026-10-09; from 2026-10-10, version 2.3 applies. Earlier version: 2.1.
Updated on 2026-10-09 without a new version number: daily encrypted database backups kept for 7 days (sections 6, 10 and 11) and the end of the automatic free trial for new accounts (sections 2 and 6).
Related: Terms of Service · Support
The English text is the original of this document. If a translation differs from it, the English text is used to interpret the meaning only where the law of your country allows this; otherwise the version in your own language is the binding one. Your mandatory rights never depend on the language you read.
Summary
| Topic | In short |
|---|---|
| Who is responsible | XIUSoft (Republic of Korea), contact@xiu.kr. See section 1. |
| Without an account | SSH, SFTP and the other local features need no account. Nothing about your servers is sent to us. |
| With an account | We store the email address and sign-in identifier that your Apple or Google account provides (there is no separate email sign-up), an end-to-end encrypted vault, push-notification device tokens and your subscription status. See section 2. |
| What we cannot read | Your host addresses, user names, passwords, private keys, snippets and other synced items are encrypted on your device before upload. We cannot decrypt them. Exception: the host label used for notifications, which is user@address for a host without a name (see Push notifications). |
| Push notifications | Notification text (title, body, tmux session name, host label) is not end-to-end encrypted. It passes through our server and Google (Firebase Cloud Messaging) and, on iOS, Apple. See section 2. |
| Notification settings and approvals | If you set quiet hours or mute notifications, those settings and your device’s time zone are stored on our server so that it can decide whether and how to send each push. The approval history (audit log) stays on your device only, 30 days by default. See sections 2 and 3. |
| Crash reports | Off until you agree (Android and iOS only). Sent to Google Firebase Crashlytics and kept 90 days. You can turn them off at any time. |
| Ads, analytics, tracking | Apps: none. No advertising or usage-analytics SDKs, no advertising identifier, no sale or sharing of app data. Website (livessh.xiu.kr): pages show Google ads, and Google uses advertising cookies. See section 12. |
| Where data is processed | On our server in Osaka, Japan (Oracle Cloud) and with the service providers in section 4, mainly in the United States. See sections 4 and 5. |
| Backups | Daily, encrypted, for disaster recovery only, kept 7 days on our server in Japan. Data you delete is gone from every backup within 7 days. See section 6. |
| Your rights | Access, correction, deletion, portability, objection and more, depending on where you live. Write to contact@xiu.kr. See section 7. |
| Delete everything | In the app: Settings > LiveSSH Cloud > Delete account. It takes effect immediately; copies in our encrypted backups are gone within 7 days. See section 11. Except for two hash-only records that cannot identify you (deletion record and, if your account had the former automatic free trial, trial claim): see section 6. |
| Minimum age | 16. See section 9. |
| Users in mainland China | Your data is stored in Japan and handled by the overseas recipients in section 4, only with your separate consent where the law requires it. Some Google-based features may not work there; SSH and SFTP do. See section 8. |
1. Who we are
The controller (the party that decides how your personal data is used) is XIUSoft (Korean name: 시우소프트), Republic of Korea. Representative: Ga Ram Jung (정가람). Business registration number: 752-41-01398. Address: 901-401, 33 Dongtanjungsimsangga 1-gil, Dongtan-gu, Hwaseong-si, Gyeonggi-do, 18455, Republic of Korea. Telephone: +82 507-1432-9182.
Contact for all privacy matters, including requests to exercise your rights: contact@xiu.kr. We have not appointed a Data Protection Officer because the law does not require one for our size and activities. The contact point for data protection matters, for you and for the authorities (the role of a DPO contact), is our representative, Ga Ram Jung (정가람), at the same email address and telephone number. In the Republic of Korea this person is also our person in charge of personal information protection (개인정보 보호책임자).
Representatives: if the GDPR or the UK GDPR requires us to have a representative in the EU or the UK, we will appoint one and publish the name and address here. If another country requires a local representative or contact point, we will do the same. Until then, write to contact@xiu.kr and we will deal with your request.
2. What we collect, why, and on what legal basis
The table lists everything we process. Legal bases are given for users in the EEA, the UK and Switzerland (GDPR). Anything not listed is not collected.
Items marked “with an account” are processed only if you create a LiveSSH Cloud account; the features that need a subscription are described in the Terms of Service. Providing the data is voluntary, but without it we cannot provide the feature concerned.
| Data | What exactly | Why | Legal basis (GDPR) |
|---|---|---|---|
| Account (with an account) | If you sign in with Apple or Google: the provider name, the provider’s account identifier and the email address the provider gives us (for Apple this may be a private relay address), and the name the provider gives us if you allow it. A random user ID, creation time, display name and language setting, and sign-in/session data. | Create and secure your account. | Contract (Art. 6(1)(b)) |
| Encrypted vault (with an account) | A keyset (your data key wrapped by your master password and by your recovery key) and ciphertext of synced items such as hosts, snippets, SSH keys and profile pictures. We can see each item’s type, ID, size, timestamps and deletion marker, and how many items you have. We cannot see the content. | Sync your items between your devices. | Contract (Art. 6(1)(b)) |
| Push-notification data (with an account, if you enable notifications) | Device token and platform (Android, iOS or macOS) with the time it was updated; a SHA-256 hash of your notification hook token with a label (the host display name, stored in plain text; for a host without a name of its own this is user@address, that is, your SSH user name and the host address; to avoid this, give the host a name before you install the hook), and when that token was created and last used (recorded at most once an hour). Each notification: title, body (up to 300 characters), tmux session name and host label. The server does not write notification bodies to its logs. With Live Activities on iOS, a Live Activity push token is also stored, and the server sends the same title, body and host label, and for an approval the project (folder) name, to that activity through Apple. Newer notification hooks may also send a request ID, the project (folder) name, the agent name (for example Claude Code), the tool name (for example Bash) and a risk level; these travel with the notification, are not written to the database and are held in the server’s memory for at most 10 minutes only to suppress duplicate notifications. | Deliver push notifications from your servers to your devices. | Contract (Art. 6(1)(b)); your device’s notification permission |
| Notification settings (with an account, if you change them in the app) | Whether quiet hours (do not disturb) are on; their start and end times and days; your device’s time zone (an identifier such as Europe/Paris); which notifications still get through during quiet hours; the notification kinds you muted; per-host settings keyed by the name you gave the host (muted or not, allowed notification kinds and agents; hosts without a name of their own are left out); and the time of the last change. | Decide on our server, right before each push, whether to send it and whether to send it silently, so that your settings apply even while your device is off or the app is closed. | Contract (Art. 6(1)(b)) |
| Subscription status (with an account) | Your user ID is used as your RevenueCat app user ID. RevenueCat and the store (Apple, Google, Microsoft) process the purchase. We store the store name, product, transaction identifier, status, start and expiry times, whether it renews, and whether it is a test purchase. We never receive your card or payment details. | Check that a paid feature is available to you. | Contract (Art. 6(1)(b)) |
| Crash reports (only if you agree; Android and iOS only) | Stack trace, operating system and app version, device model, crash time, and the identifiers and basic device state that Firebase Crashlytics adds (for example a Firebase installation ID). Error messages are cut to their first line and email addresses, URLs, file paths, IP addresses and host names are masked before sending. Never included: host addresses, user names, passwords, keys, commands, terminal output, file names. | Find and fix crashes. | Consent (Art. 6(1)(a)), which you can withdraw at any time in Settings > Security |
| Server logs | IP address, request time, requested path, response status and the browser or app identifier (user agent) of requests to our servers. | Security, abuse prevention, troubleshooting. | Legitimate interests (Art. 6(1)(f)): keeping the service secure. Necessary because the IP address and request line are the least data needed to detect and investigate attacks; kept only 7 days. |
| Account deletion record | When you delete your account we write a record containing a one-way hash of your user ID (not your email), the time and which deletion steps succeeded. It cannot identify you. | Prove that deletions were carried out and finish steps that failed. | Legitimate interests (Art. 6(1)(f)): being able to show that a deletion was carried out. Necessary because a hash is the least data that can prove it; kept up to 3 years, then purged. |
| Trial claim (accounts that had the former automatic free trial) | Until October 2026 every new account got a free trial automatically. To allow one such trial per Apple or Google account we stored a one-way hash with a secret key (SHA-256) of your sign-in provider and the provider’s account ID, and the time the trial was claimed. We no longer collect this for new accounts; free trials are now offered by the app stores. The existing hashes cannot be reversed to the ID, are not your email address, and are kept for 1 year after the trial was claimed, even if you delete your account. | Prevent repeated free trials (fraud and abuse prevention). Only for hashes stored before the automatic trial ended. | Legitimate interests (Art. 6(1)(f)): preventing abuse of the free trial. Necessary because a keyed hash is the least data that can recognise a returning account; kept 1 year, then deleted automatically. |
| Support and rights requests | The email you send us and our reply. | Answer you and keep a record of your request. | Legitimate interests (Art. 6(1)(f)): answering you and defending legal claims. Necessary because we must be able to show what we answered; kept up to 3 years after closing. Legal obligation (Art. 6(1)(c)) where the law requires a record. |
We do not use your data for automated decisions with legal effect, for advertising, or to train AI models. We do not collect advertising identifiers, location, contacts, photos (other than a profile picture you choose, which is stored encrypted) or any special categories of personal data. For each legitimate-interest item we weighed our interest against your rights and expectations and keep only the data shown; you may object (section 7).
3. What stays on your device
The following is never sent to us unless you turn on LiveSSH Cloud sync, and even then only as ciphertext that we cannot read:
- SSH host addresses, ports, user names, passwords, private keys and passphrases, kept in your device’s secure storage (Keychain on iOS and macOS, Keystore-backed storage on Android, Windows credential storage). Exception: if you install the notification hook for a host without a name of its own, its label user@address (user name and host address) is stored on our server in plain text (see section 2).
- Snippets, settings, saved host-key fingerprints, port-forwarding rules, agent activity history (kept on the device for 30 days) and terminal scrollback.
- Terminal input and output, command history and files you transfer over SFTP. These go directly between your device and the server you choose.
- If you enable biometric unlock, your master password is kept in your device’s secure storage. Your fingerprint or face data is handled by the operating system; the app never receives it.
- Approval history (audit log): which agent request was approved or denied (by you or by an auto-approval rule you created), when, on which host and session, how (in the app, from a notification, with Siri or Shortcuts, or on Apple Watch), the tool, the risk level and a short summary (up to 300 characters) in which secrets such as tokens and passwords are masked. It is kept only on the device, for at most 30 days by default, and is not synced. You can export it (CSV or JSON) and clear it in the app. The notification hook on your own server also keeps a size-limited record of its decisions on that server (~/.livessh/audit.jsonl); we never receive it.
- Siri, Shortcuts and Apple Watch: approving or denying with Siri or Shortcuts is carried out by the app on your device, directly over SSH to your server; nothing about it is sent to us (Siri voice requests are processed by Apple under Apple’s privacy policy). If you use LiveSSH on Apple Watch, your iPhone sends the watch a short summary of pending requests, agents and server status (no credentials, commands or diffs; a host appears under the name you gave it, or as user@address if it has none) over Apple’s WatchConnectivity link between your paired devices, and your answer on the watch goes back to the iPhone, which answers over SSH. Our servers receive no additional data for this.
Deleting the app deletes this local data (on iOS, secure-storage entries can survive reinstallation; use Sign out and Delete account before uninstalling if you want them removed).
4. Who receives data (processors and recipients)
We do not sell your data and do not share the data of the apps and LiveSSH Cloud for advertising (for ads on the website, see section 12). We use the providers below to run the service. They act on our instructions (as processors, or “entrusted parties”) except where noted.
| Recipient | Purpose | Data | Location | Transfer safeguard (EEA, UK, Switzerland) |
|---|---|---|---|---|
| XIUSoft server (self-hosted Supabase Auth and database on Oracle Cloud Infrastructure; Oracle Corporation is the hosting provider) | Accounts and sign-in, vault, push-device table, subscription records, server logs | As in section 2 | Osaka, Japan | Japan: adequacy decision. Oracle (host): data processing agreement, with Standard Contractual Clauses where Oracle staff outside an adequate country can access the data. Switzerland: Swiss addendum. |
| Google Workspace (Google LLC); our email provider | Receiving and answering support emails | Your email address and the email content | United States and other Google locations | EU-US Data Privacy Framework (Google LLC is certified); otherwise Standard Contractual Clauses in Google’s data processing terms, with the UK Addendum and Swiss addendum. |
| Google Firebase Cloud Messaging (Google LLC) | Delivering push notifications to Android and, on iOS, relaying to Apple | Device token, notification title, body, session and host label | United States and other Google locations | As for Google Workspace. |
| Apple Push Notification service (Apple Inc.) | Delivering push notifications and Live Activity updates to iOS | Same as above | United States and other Apple locations | Standard Contractual Clauses (Apple states it uses them for data from the EEA, UK and Switzerland), with the UK and Swiss addenda. |
| Google Firebase Crashlytics (Google LLC) | Crash reports (only with your consent) | As in section 2 | United States and other Google locations | As for Google Workspace. |
| RevenueCat, Inc. | Subscription management and verification | App user ID (your user ID), purchase and entitlement information | United States | Standard Contractual Clauses in RevenueCat’s data processing agreement, with the UK Addendum or IDTA and the Swiss addendum. |
| Google (Google AdSense; Google LLC, and Google Ireland Limited for users in the EEA and Switzerland) | Serving and measuring ads on the LiveSSH website. Independent controller (section 12). | For website visitors: IP address, browser and device information, pages visited, cookie identifiers, ads shown and clicked. No app data. | United States and other Google locations | EU-US Data Privacy Framework (Google LLC is certified); otherwise Standard Contractual Clauses relied on by Google. |
| Apple (App Store, Sign in with Apple), Google (Google Play, Sign in with Google), Microsoft (Microsoft Store) | Distribution, payment, sign-in. These companies are independent controllers under their own policies. Apple and Google are the merchants of record for purchases; for Microsoft Store purchases, Microsoft processes the payment on our behalf. | Purchase and sign-in data | Worldwide | Their own mechanisms, set out in their privacy policies. |
We may disclose data to authorities, courts or advisers where the law requires it, or to protect our rights, and to a successor if the business is transferred (we would tell you and the rules in this policy would continue to apply).
5. International transfers
XIUSoft is based in the Republic of Korea. Our server is in Japan and our other providers are in the United States and other countries, so your data is transferred across borders wherever you live. Most transfers happen only if you create an account, enable notifications or agree to crash reports; the local features of the app transfer nothing to us.
For users in the EEA, the UK and Switzerland: transfers to the Republic of Korea and to Japan are covered by European Commission adequacy decisions (Korea: Decision (EU) 2022/254; Japan: Decision (EU) 2019/419) and by UK adequacy regulations. For the United States we use, for each provider, the safeguard in the last column of the table in section 4: the EU-US Data Privacy Framework (and its UK and Swiss extensions) where the recipient is certified, and otherwise the Standard Contractual Clauses (Decision (EU) 2021/914) with the UK Addendum or International Data Transfer Agreement and, for Switzerland, the Swiss addendum. You can ask for a copy of the safeguards at contact@xiu.kr.
For users in Korea, Japan, Brazil, mainland China and elsewhere: your data is processed in the countries listed above, under the safeguards and notices in section 8. You may refuse a transfer by not using the feature concerned or by deleting your account.
6. How long we keep data
| Data | Retention |
|---|---|
| Account, vault, push tokens, hook-token hashes, subscription records | Until you delete your account. Deletion from our database is immediate and complete; copies in our encrypted backups disappear when those backups expire, within 7 days at the latest (see “Backups” below). Push tokens are also removed when you sign out of the app or the push provider reports the token invalid. We do not delete inactive accounts automatically. The only exceptions are the two hash-only records below (account deletion record, trial claim). |
| Notification settings and Live Activity tokens | Until you change the settings or delete your account; they are deleted with the account, and copies in our encrypted backups are gone within 7 days. A Live Activity token is also removed when the activity ends, when you sign out, or when Apple reports it invalid. |
| Approval history (on your device only) | At most 30 days by default, after which it is removed on the device. You can export it (CSV or JSON) and clear it in the app. It is never sent to us; deleting the app removes it. |
| Backups | The whole database is backed up once a day. Each backup is compressed and encrypted on our server in Osaka, Japan with a public key, so the server itself cannot decrypt it. Backups are kept 7 days and then deleted automatically. Data you delete, or that is deleted with your account, is therefore gone from every backup within 7 days. Backups are used only to restore the service after a failure or disaster. |
| Server logs (IP address, request time, path, status) | Rotated daily and deleted after 7 days (at most 8 days in total). Kept only to detect and investigate abuse. |
| Crash reports | Held by Firebase Crashlytics for 90 days (Google’s default retention). Turning crash reports off deletes reports not yet sent. |
| Account deletion record (hash only) | Up to 3 years, then purged. It lets us show you and the authorities that a deletion was carried out, and finish steps that failed. It does not identify you. |
| Trial claim (hash only) | No longer collected for new accounts (the automatic free trial ended in October 2026; free trials are now offered by the app stores). Existing claims are deleted automatically 1 year after the trial was claimed, even if you deleted your account earlier. It is a keyed one-way hash that cannot be reversed to your account ID and does not contain your email address. |
| Support emails and rights requests | Up to 3 years after the request is closed, then deleted. Needed to handle follow-up questions, to prove that we answered and to defend legal claims that can arise within that time. |
| Purchase and payment records | Held by Apple and Google as merchants of record, by Microsoft, which processes Microsoft Store payments on our behalf, and by RevenueCat, under their own policies and the law that applies to them. We keep no payment records of our own; our copy of your subscription records is deleted with your account, and we delete your RevenueCat subscriber record at the same time. |
7. Your rights
Depending on where you live you have some or all of these rights over your personal data: to know what we hold and get a copy (access); to correct it; to delete it; to restrict or object to processing; to receive it in a portable format; to withdraw consent at any time (this does not affect processing before the withdrawal); and not to be subject to decisions based solely on automated processing (we make none). We apply these rights to every user, whatever your country, unless a law makes an exception.
How to use them: use the in-app controls (delete account, crash-report switch, notification settings) or write to contact@xiu.kr from the email address of your account. We may ask you to confirm your identity. We answer without undue delay, within the period required by applicable law and in any case within 30 days (shorter periods apply in some places, for example 10 days under Korean law), and tell you if the law allows and we need more time. Requests are free unless they are clearly unfounded or excessive.
Because the vault is end-to-end encrypted, we can export or delete your ciphertext but we cannot show you its contents; use the app to read your own data.
If you are unhappy with our answer you may complain to the data protection authority where you live or work. Examples: Personal Information Protection Commission (Korea, PIPC); Personal Information Protection Commission (Japan, PPC); Autoridade Nacional de Proteção de Dados (Brazil, ANPD); the national authorities of EEA states (list at edpb.europa.eu); the Information Commissioner’s Office (UK, ICO); the Federal Data Protection and Information Commissioner (Switzerland, FDPIC); the California Attorney General and California Privacy Protection Agency; the Office of the Privacy Commissioner of Canada; the Office of the Australian Information Commissioner (OAIC); the Personal Data Protection Commission (Singapore, PDPC); the Data Protection Board of India. We would appreciate the chance to resolve your concern first.
8. Rules for specific regions
European Economic Area, United Kingdom, Switzerland (GDPR, UK GDPR, FADP)
Legal bases are in section 2 and transfers in section 5. You have the rights in section 7 and may complain to your supervisory authority. Where you have given consent, you may withdraw it at any time. You may object at any time to processing based on legitimate interests; we will stop unless we have compelling grounds or need the data for legal claims. If a personal data breach is likely to put you at risk, we will inform you and the authorities without undue delay and within the legally required period (for example 72 hours to the supervisory authority under the GDPR).
California and other US states (CCPA/CPRA and similar laws)
In the last 12 months we collected these categories: identifiers (email address, account identifiers, device push token, IP address); commercial information (subscription records); internet or network activity (server logs); device information (crash reports, if you agreed); and, as stored but unreadable by us, other information in your encrypted vault. Sources: you, your device, and the stores and providers in section 4. Purposes: those in section 2. We keep each category as long as stated in section 6.
We do not sell personal information and do not share the data of the apps and LiveSSH Cloud for cross-context behavioral advertising. Google’s personalised ads on the LiveSSH website may count as “sharing”; you can opt out as described in section 12. We have no actual knowledge of selling or sharing the data of anyone under 16. We do not use or disclose sensitive personal information (which includes account log-in credentials) except to provide the service you asked for. Disclosures for a business purpose go to the processors in section 4.
You may ask to know, access, correct, delete and port your information, to opt out of sale/sharing (we do neither with the data of the apps and LiveSSH Cloud; for Google’s personalised ads on the website, see section 12) and not to be discriminated against for using these rights. You can use an authorized agent; we will verify the agent’s authority and your identity. We respond within 45 days (extendable once by a further 45 days with notice). If we refuse a request, you may appeal by replying to our decision at contact@xiu.kr. We do not offer financial incentives for data. Other US state laws (for example in Virginia, Colorado, Connecticut, Texas) give similar rights, which we honor in the same way.
Republic of Korea (PIPA)
This policy is also our privacy policy under the Personal Information Protection Act. Items collected: section 2 (required for the account: email address or sign-in identifier; collected automatically: IP address, service-use records, device token, and crash information only with your consent). Purposes: section 2. Retention: until you delete your account or withdraw consent, after which data is destroyed immediately in an irreversible way; the periods in section 6 apply to the other data.
Entrustment of processing and overseas transfer: the entrusted parties and recipients are listed in section 4 with their purposes, items and country. Transfer takes place over the network at the time you use the feature concerned (sign-up or sign-in, notifications, crash reports, purchases) and is kept for the periods in section 6. You may refuse the transfer by not using that feature or by deleting your account; this may make the feature unavailable. For questions to an overseas recipient, write to us at contact@xiu.kr.
Person in charge of personal information protection: Ga Ram Jung (정가람), representative; contact@xiu.kr, +82 507-1432-9182. Safety measures: section 10. Complaints and remedy: the Personal Information Infringement Report Center (privacy.kisa.or.kr, 118), the Personal Information Dispute Mediation Committee (kopico.go.kr, 1833-6972), the Supreme Prosecutors’ Office Cyber Crime Investigation Division (spo.go.kr, 1301) and the National Police Agency Cyber Bureau (ecrm.police.go.kr, 182). Users under 14 cannot use the service (section 9).
Japan (APPI)
We handle personal information, and personal data we hold, as a business operator handling personal information under the Act on the Protection of Personal Information. Purposes of use are in section 2. We do not provide personal data to third parties other than the entrusted parties in section 4. Information on foreign transfers: our servers are in Japan; XIUSoft is in the Republic of Korea, whose Personal Information Protection Act is a comprehensive data protection law enforced by an independent commission; our providers in the United States are bound by their own privacy programs and by our contracts to protect the data and to use it only for the stated purposes, even though the United States has no single comprehensive federal data protection law. You may ask us for further information on the system of a foreign country and on the measures a recipient takes, and for disclosure, correction, suspension of use and deletion, by writing to contact@xiu.kr. Security measures: section 10.
Brazil (LGPD)
The controller is XIUSoft (section 1); the contact point (encarregado) is contact@xiu.kr. The legal bases are those in section 2 mapped to the LGPD: performance of a contract (Art. 7, V), consent (Art. 7, I), legitimate interest (Art. 7, IX) and compliance with legal obligations (Art. 7, II). You have the rights listed in Article 18 (confirmation, access, correction, anonymization, blocking or deletion, portability, information about sharing, information about refusing consent and its consequences, and revocation of consent). You may complain to the ANPD. International transfers rely on the mechanisms in LGPD Article 33, in particular specific contractual clauses, and your specific consent where needed for the transfers described in section 5.
Mainland China (PIPL)
If you are in mainland China, the Personal Information Protection Law (PIPL) may apply. We process the personal information of users in China on the basis of your consent, and where necessary to provide the account or subscription you ask for. Your data is stored on our server in Osaka, Japan; we have no server in mainland China. It is processed by XIUSoft in the Republic of Korea and by the overseas recipients in section 4 (Google, Apple, RevenueCat and, for hosting, Oracle), in the countries shown there, for the purposes in section 2 and for the periods in section 6. The local features of the app transfer nothing; transfers happen only if you create an account, enable notifications or agree to crash reports.
Where the law requires it, we ask for your separate consent, as its own choice in the app and before the data leaves mainland China, for (a) the cross-border transfer described in this policy and (b) any processing of sensitive personal information. We do not intentionally process sensitive personal information, and we do not process the personal information of children under 14. If you do not consent, the features that need our server are unavailable, but SSH, SFTP and the other local features still work. You may withdraw consent at any time by turning the feature off or deleting your account; this does not affect earlier processing.
To exercise your PIPL rights (to know, to decide, to restrict or refuse processing, to access and copy, to transfer, to correct, to delete, and to ask us to explain these rules), including against an overseas recipient, write to contact@xiu.kr from your account email; this is our contact channel for PIPL matters. We answer within the period the law requires and in any case within 30 days. If you think we have infringed your rights, you may complain to the competent authority in China. Where the PIPL requires us to designate a personal-information protection officer or a dedicated institution or representative in mainland China, we will designate one and publish the contact here. We do not state that any filing, registration, standard contract or security assessment exists; we complete those the law requires for our situation before we offer the app in the mainland China app stores.
Some features depend on services that may be unreachable from mainland China: Google’s push service (Firebase Cloud Messaging) for Android notifications, Firebase Crashlytics crash reports and Sign in with Google. The core SSH and SFTP features work without them and without an account.
Canada (PIPEDA), Australia (Privacy Act), Singapore (PDPA), India (DPDP Act)
Canada: we obtain your consent for the collection, use and disclosure described here; your information may be processed outside Canada and may be accessible to foreign authorities under local law. You may withdraw consent or access and correct your information, and complain to the Office of the Privacy Commissioner of Canada.
Australia: we handle personal information in line with the Australian Privacy Principles. When we disclose information to overseas recipients (section 4) we take reasonable steps to make sure they handle it consistently with the APPs. You may ask for access or correction and, if we do not resolve a complaint, complain to the OAIC.
Singapore: we collect, use and disclose personal data with your consent or as the PDPA allows, and transfer it overseas only with protection comparable to the PDPA. Contact for data protection matters: contact@xiu.kr. You may complain to the PDPC.
India: we process your personal data on the basis of your consent and for the legitimate uses the Digital Personal Data Protection Act allows. You may access, correct, complete and erase your data, withdraw consent, nominate another person to exercise your rights, and use our grievance contact (contact@xiu.kr; we answer within 30 days). You may complain to the Data Protection Board of India after you have used our grievance process.
Hong Kong, Taiwan and other regions
Users in Hong Kong (PDPO), Taiwan (PDPA) and every other country have the rights in section 7 to the extent their law provides, and may contact us at contact@xiu.kr or complain to their local authority. Where local law gives you a stronger right than this policy, the local law applies.
9. Children
LiveSSH is not directed at children. You must be at least 16 years old to create an account or use LiveSSH Cloud. We chose one global age of 16 because it is the highest default age of digital consent in the EU (member states set it between 13 and 16) and it also exceeds the thresholds in Korea (14), the United States (13, COPPA), Brazil and Japan, so one rule works everywhere. If your country sets a higher age for consent or for entering contracts, that age applies to you.
We do not knowingly collect personal data from anyone under 16. If you believe a child has given us data, write to contact@xiu.kr and we will delete it without delay.
10. Security
- End-to-end encryption of the vault on your device with XChaCha20-Poly1305; keys derived from your master password with Argon2id (64 MiB, 3 iterations) or from your recovery key. See the Security page for details and limits.
- TLS for traffic between the app and our server; Let’s Encrypt certificates.
- Database row-level security so each account can reach only its own rows; server ports closed to the Internet except the HTTPS entry point; administrative access only over a private network.
- Hook tokens are stored as SHA-256 hashes; notification bodies are kept out of server logs.
- Daily database backups are encrypted as they are made, with a public key; the private key needed to decrypt them is not on the server.
- No system is perfectly secure. The app’s source code is not public and has not been audited by a third party. If a personal data breach affects you, we will notify you and the authorities without undue delay and within the legally required period (for example 72 hours to the authority under the GDPR).
11. Deleting your account and data
In the app: Settings > LiveSSH Cloud > Delete account. After a fresh sign-in and typing a confirmation, your account and everything stored on our server for it is deleted immediately: email or sign-in identifier, encrypted vault, push tokens, hook-token hashes and subscription records. Copies in our encrypted backups disappear within 7 days, when those backups expire (section 6). Two hash-only records remain, as stated in section 6: the deletion record (up to 3 years) and if your account had the former automatic free trial, the trial claim (1 year after the claim). Neither can identify you.
If your account uses Sign in with Apple, we revoke the Apple sign-in token during deletion, and we delete your RevenueCat subscriber record. If a step cannot be completed, we tell you in the app and finish it manually on request within 30 days at contact@xiu.kr. You can also remove the connection in your Apple ID or Google account settings.
Deleting the account does not cancel a store subscription. Cancel it in the App Store, Google Play or Microsoft Store first (see the Terms of Service).
If you cannot use the app, write to contact@xiu.kr from your account email and we will delete the account after verifying it is yours, within the period required by applicable law and in any case within 30 days.
Crash reports contain no information that directly identifies you; to have them deleted anyway, write to us. Data on your device is removed when you uninstall the app.
Step by step: step-by-step guide to deleting your account.
12. Website, cookies, advertising and tracking
The LiveSSH website pages load no external fonts or analytics. They show Google AdSense ads: acting as an independent controller, Google uses cookies and similar technologies in your browser to serve and measure ads, prevent fraud and, where allowed, personalise them. What Google collects, how long it is kept and how to refuse it (including the consent message in the EEA, UK and Switzerland, Google My Ad Center and the US state opt-out) are described under Website advertising in the XIUSoft Privacy Policy. We set no tracking or advertising cookies ourselves. The pages set two first-party preference cookies, xiu_theme (system, light or dark display) and xiu_lang (language), but only when you choose a theme with the theme button or a language in the language menu; merely viewing a page sets nothing. They last 1 year and are readable on .xiu.kr so that your choice carries over between xiu.kr, livessh.xiu.kr and account.xiu.kr. They contain no identifier and are never used to recognise or track you. They are strictly functional (they remember a choice you made yourself), so they need no consent under the ePrivacy rules, including the French CNIL guidance on preferences chosen by the user. You can delete them at any time in your browser settings; the pages then show the defaults (your device’s display mode, your browser’s language). The cookies and browser storage of the account pages (account.xiu.kr) are described in the XIUSoft Privacy Policy. The apps do not track you across apps or websites and do not use an advertising identifier (Apple App Tracking Transparency does not apply).
13. Changes to this policy
We will post the new version here with a new date and keep earlier versions on request. For material or adverse changes, such as new kinds of data, new purposes or new recipients, we will tell you in the app or by email at least 30 days before they apply, and ask for consent where the law requires it. For changes that are not adverse to you (for example a clarification or a change in your favour) we give at least 7 days’ notice.
14. Contact
Privacy questions and requests: contact@xiu.kr. Telephone: +82 507-1432-9182. Postal address: XIUSoft, 901-401, 33 Dongtanjungsimsangga 1-gil, Dongtan-gu, Hwaseong-si, Gyeonggi-do, 18455, Republic of Korea. Support and security reports: see the Support page.