Terms of Service

Nexa Beep · Effective 2026-10-19 · Last updated 2026-10-12

These Terms of Service govern the rights, obligations, and responsibilities between SosomLab (“we”, “us”, or “the Company”) and you in connection with your use of Nexa Beep (the “Software”) and the relay server operated by the Company (the “Official Server”).

Notice of revision (posted 2026-10-12 · effective 2026-10-19) To reflect changes in Software versions v0.3.0–v0.5.0, we have added provisions on license files and tiers (Section 3), the nature and warranty scope of multi-device synchronization (Section 4), and the limitation of liability for synchronized content (Section 10). The revision history is at the end of this page.

1. Definitions

  1. “Software” means the Nexa Beep application distributed by the Company, including its installer, portable, and package-manager distributions and its command-line terminal mode.
  2. “User” means anyone who downloads, installs, or uses the Software.
  3. “Relay Server” means the server program (nexa-beepd) that lets two copies of the Software on different networks find each other and exchange data.
  4. “Official Server” means the Relay Server operated by the Company at beepd.sosomlab.com and registered as the Software’s default.
  5. “Peer” means another User with whom you communicate through the Software.
  6. “License File” means the file (nexa-beep.license) signed and issued by the Company for commercial use.
  7. “Sibling Device” means another of your own devices grouped under the same user by the multi-device identity feature.

2. Acceptance and Amendment

  1. These Terms take effect when you download, install, or use the Software.
  2. The Company may amend these Terms within the limits permitted by applicable law. Amendments will be posted on this page with their effective date, and material changes will be announced at least 7 days in advance. Continuing to use the Software after the effective date constitutes acceptance.

3. License

  1. The Software and the Relay Server program are licensed under PolyForm Noncommercial License 1.0.0. Personal and other noncommercial use is free of charge.
  2. Commercial use requires a separate paid license. For inquiries, contact [email protected].
  3. The full license text is published in the Software’s source repository (LICENSE.md, the authoritative English text; LICENSE.ko.md, an unofficial Korean translation), and the English license text governs in the event of any conflict with this Section.
  4. The Software is licensed, not sold. All copyright and other intellectual property rights remain with the Company.
  5. License Files (v0.3.0+) — Commercial licenses are provided as License Files signed and issued by the Company. You apply by sending the Company a request code created under Help › License… in the Software (or with nexa-beep --license request), and you install the file you receive in the same window (or with --license install). The information the Company processes for an application is governed by Section 7 of the Privacy Policy.
  6. A License File contains the issuance terms — licensee name, tier (Trial, Pro, Org, etc.), term, and the devices (device codes) it may be used on — and those terms follow the license agreement or the guidance given at issuance. Files issued for another device or another product, damaged or altered files, and expired files are not recognized as valid licenses. A License File belongs to the person or organization to whom it was issued and may not be transferred or redistributed without the Company’s consent.
  7. The Software currently does not lock any feature based on whether a license is present, and does not connect to the network to check a license (it checks only the file and its signature). Without a valid License File it runs in the “Free (non-commercial)” state. The fact that no feature is locked does not grant permission for commercial use; whether use is commercial is governed by the license in item 1. The Company may designate certain features as paid-license-only in future versions, in which case it will announce this in that version’s release notes and in these Terms.

4. Nature of the Software

  1. By default the Software operates directly between your device and other devices on the same local network. No Company server is involved in that mode, and the Company provides no account, hosting, or storage service.
  2. The Software sends no personal data to the Company automatically. The Company receives personal data only when you yourself email a commercial-license request code or an inquiry. What is stored on your device and what leaves it over the network is described in the Privacy Policy.
  3. Conversations and files are end-to-end encrypted between devices. The Company cannot access their contents by any route and therefore cannot recover, hand over, or moderate them.
  4. Your identity lives in the key file on your device (identity.key). If you lose it, you will appear to Peers as a different person, and the Company has no way to restore it. Backing up the key file is your responsibility. Conversation history is not kept on any Company server and does not follow you to a new device; to move it, use the Software’s history backup and restore functions.
  5. If multi-device identity is enabled, the user key (user.key) and the pairing passphrase are what let a device with the same values be recognised as “my device” without approval. Managing the pairing passphrase, and replacing the user key when a device is lost (including revoking it in the My Devices list), is your responsibility. Sibling Devices are fully trusted and exchange conversation content with one another, so you must not group devices you do not control.
  6. Multi-device synchronization (v0.4.0–v0.5.0) — sender copies, catch-up, and read-state sync between Sibling Devices are convenience features and not a backup or a means of migrating your full history. Catch-up covers only the most recent 200 lines per conversation, up to 1 MiB per session, text only (file contents are not transferred), and requires the Sibling Devices to be online at the same time. The Company does not warrant the completeness, ordering, or timeliness of synchronized content. Deleting a conversation applies only to that device and is not propagated to other Sibling Devices.

5. The Official Server

  1. The Official Server is an optional feature that the Company provides free of charge and as a courtesy for Users who wish to communicate with Peers outside their local network. It is used only if you enable it in settings, and the Software is fully functional without it.
  2. The Official Server only relays; it stores no messages, files, or metadata. Consequently, even through the server, data is delivered only while both parties are connected at the same time.
  3. The Company does not guarantee the uptime, latency, throughput, or continued availability of the Official Server. The Company may maintain, change, suspend, or shut the server down without prior notice, and may impose or change abuse-prevention limits such as per-connection bandwidth caps, channel counts, and idle timeouts.
  4. Interruption of the Official Server does not affect communication within your local network. You may at any time run the Relay Server program yourself; a self-hosted server behaves exactly like the Official Server.
  5. The Company accepts no responsibility for Relay Servers that you or any third party operate.

6. User Obligations

You must not:

  1. use the Software or the Relay Server program commercially without a valid paid license;
  2. abuse the Software — for example by repeatedly sending unwanted messages or files, impersonating others, or harassing Peers;
  3. transmit malware, pirated material, or any content that infringes others’ rights or is prohibited by applicable law;
  4. place excessive load on the Official Server, circumvent its abuse-prevention measures such as bandwidth caps or connection limits, or attack it;
  5. attempt to bypass the Software’s safety mechanisms (received-file quarantine, scanning and approval, trust pins, and the like) in order to harm a Peer’s device;
  6. engage in any other conduct prohibited by applicable law or these Terms.

The Company may block connections that abuse the Official Server without prior notice. Because the Company cannot see the contents of communications, it cannot intervene in or mediate disputes, harassment, defamation, or similar matters between Users.

7. Received Files and Security

  1. The Software handles received files through quarantine, scanning, and approval, and never executes them itself. However, opening a file after approval is your decision, and its consequences are your responsibility. Operating-system quarantine markers are an auxiliary measure and do not guarantee safety.
  2. A “scanned (no detection)” indication merely reflects the verdict of the antivirus product installed on your PC; the Company does not warrant that any received file is safe.
  3. Identity verification pins a key on first contact (trust on first use), so a man-in-the-middle attack at the very first contact cannot, in principle, be detected. Where certainty matters, it is up to you to carry out the Software’s fingerprint-comparison procedure with the Peer over a separate channel.
  4. The Company does not warrant protection against threats that the Software’s known-limitations documentation explicitly excludes, including compromise of the device itself, leakage of the key file, an observer on the same network learning of your presence, and relay metadata.

8. Third-Party Components

The Software runs on components provided by the operating system and may interoperate with third-party software such as antivirus products and package managers. Those components are subject to their own licenses and terms.

9. Disclaimer of Warranties

THE SOFTWARE AND THE OFFICIAL SERVER ARE PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. The Company does not warrant that the Software will operate without interruption or error, or that it will be compatible with any particular network environment, hardware, or system configuration. In particular, automatic discovery may not work on some networks, such as enterprise wireless networks.

10. Limitation of Liability

To the maximum extent permitted by applicable law, the Company shall not be liable for any indirect, incidental, special, consequential, or punitive damages, for loss of data, revenue, or business, for non-delivery, delay, or loss of messages or files, for omissions, duplication, or delays in synchronization between Sibling Devices, or for harm caused by received files, arising out of the use of or inability to use the Software or the Official Server. Liability that cannot be excluded by law, including liability for willful misconduct or gross negligence, is not limited.

11. Discontinuation

The Company may change or discontinue distribution of the Software or any of its features, and operation of the Official Server, at any time. Copies already installed may continue to be used under these Terms, and communication within your local network continues to work independently of the Official Server.

12. Governing Law and Jurisdiction

These Terms are governed by the laws of the Republic of Korea. Any dispute arising in connection with the Software shall be brought before the court having jurisdiction under the Korean Civil Procedure Act.

13. Contact

Revision History

PostedEffectiveChanges
2026-10-122026-10-19Reflects Software v0.3.0–v0.5.0 — added definitions (License File, Sibling Device) · provisions on License Files, tiers, and no feature locking (Section 3, items 5–7) · corrected wording on personal data sent to the Company · Sibling Device trust and the nature and warranty scope of multi-device synchronization (Section 4, items 5–6) · limitation of liability for synchronization omissions (Section 10)