English
English日本語

Screen Dos Product-Specific Privacy Information

Version 1.0 Language: English (Authoritative Version) Established and Effective Date: September 1, 2026 Operator: Nagori Soft

1. Scope

  1. This Product-Specific Privacy Information explains specific handling of communications, local storage, logs, communications with the Nagori Soft API, and other User Information in Screen Dos.
  1. The Nagori Soft Privacy Policy also applies to Screen Dos.
  1. The Nagori Soft Privacy Policy establishes privacy principles common to Nagori Soft Services. This document provides more specific information concerning Screen Dos. Where the descriptions differ, this document controls with respect to processing specific to Screen Dos.
  1. “User Information” has the meaning described in the Nagori Soft Privacy Policy.

2. Communication Overview

  1. Screen Dos Version 1.0 provides screen sharing between a Host device and Viewer devices over a trusted local network or a private VPN managed or selected by the User.
  1. For screen sharing, the Host starts a local HTTP/WebSocket server for connection handling and signaling. After signaling, video is transmitted directly between the Host and Viewer using WebRTC. WebRTC media communications are protected by DTLS-SRTP.
  1. Nagori Soft, the Nagori API, Cloudflare, and other Nagori Soft infrastructure are not part of the Screen Dos screen-sharing path and do not relay or store shared-screen content.
  1. Remote-input functionality is not implemented in Version 1.0.
  1. Communication with the Nagori Soft API currently occurs only when the User explicitly:

(a) registers or changes a Contribution Code; or

(b) performs an update check from the Help menu.

  1. Merely launching Screen Dos, leaving it idle, starting or continuing ordinary screen sharing, or ending a sharing session does not by itself cause automatic communication with the Nagori Soft API.

3. Screen Sharing over LAN and Private VPN

  1. When Screen Dos is used on a local network, communications occur between the Host device running Screen Dos and Viewer devices to which the User permits access.
  1. Where a User uses a private VPN that the User manages or selects, Screen Dos uses a LAN-equivalent connection method over the private network established by that VPN.
  1. The local sharing server uses HTTP and WebSocket. This local signaling path does not use an HTTPS server certificate. Screen Dos is therefore intended to be used on a trusted local network or an appropriately protected private VPN.
  1. Screen Dos Version 1.0 does not use a mechanism under which the local sharing server obtains, is issued, receives, or renews an HTTPS server certificate from Nagori Soft.
  1. Screen Dos does not use STUN, TURN, or an external ICE server for screen sharing. The current WebRTC configuration uses `iceServers: []` and does not hard-code a third-party host or relay service for screen sharing.
  1. Version 1.0 therefore does not provide screen sharing through a public Internet relay operated by Nagori Soft. Users should not expose the local sharing server directly to an untrusted public network.
  1. If a User uses a VPN service, processing of IP addresses, connection records, authentication information, or other information by the VPN provider depends on that provider’s service and privacy terms and is not controlled by Nagori Soft.

4. Information Handled by the Host When a Viewer Connects

  1. When a Viewer connects to the Host, the Host receives the Viewer’s source IP address and User-Agent information sent by the Viewer.
  1. Screen Dos may derive browser and operating-system display information from the User-Agent information and display it together with the Viewer’s source IP address on the Host approval screen. This is used to help the User identify the connecting Viewer.
  1. This information is network metadata handled directly between devices participating in the screen-sharing session. It is not transmitted to the Nagori Soft API merely to establish ordinary screen sharing.
  1. A Viewer IP address and certain other connection information may be recorded in the local application log described in Section 9.

5. Nagori Soft API and Cloudflare

  1. Screen Dos connects over HTTPS to the following Nagori Soft API only when required for Contribution Code verification or an update check:

`https://api.nagorisoft.com`

  1. The Nagori API is operated using Cloudflare Workers and related Cloudflare infrastructure.
  1. As of the Established and Effective Date, Workers Logs and Workers Traces are disabled for the Production Nagori API. The Nagori API source does not implement ordinary application logging of request bodies, Contribution Codes, Receipts, or other secrets, and does not include an external analytics SDK or Logpush transmission logic.
  1. The Nagori API Production D1 database does not store the raw Contribution Code. For a Code, it stores an HMAC-SHA-256-derived value and information necessary to operate the Code lifecycle.
  1. The Production D1 database is not designed to store Contribution Code verification history, a device ID, User name, PC name, MAC address, a list of User IP addresses, shared-screen content, or a telemetry ID.
  1. At Cloudflare’s network layer, source IP addresses, request information, routing information, and other technical metadata may be processed as part of ordinary HTTPS, security, and delivery operations. Nagori Soft does not state a specific retention period in this document for individual items processed by Cloudflare at that network layer where such a period is not determined by Nagori Soft.
  1. The Nagori API is not used as a relay for Screen Dos shared-screen video.

6. Update Checks

  1. Screen Dos requests Update information from the Nagori Soft API only when the User explicitly selects Help → Check for updates or performs an equivalent update-check action.
  1. Screen Dos does not perform update checks automatically at startup, in the background, or at periodic intervals.
  1. Portable and Setup distributions use a GET request in the following form:

`GET https://api.nagorisoft.com/v1/apps/screen-dos/latest?channel=<portable|setup>&platform=windows-x64`

  1. The Update check uses the ordinary `Accept: application/json` HTTP header. Under the current request contract, the distribution channel and platform are sent as query parameters. The installed Screen Dos Version, User name, device ID, shared-screen content, and other User-created content are not sent as part of this request.
  1. Screen Dos verifies signed Update metadata received from the Nagori API, including the signature, applicable application, channel, platform, Version, URL, and, where applicable, artifact SHA-256 information.
  1. After verification, if the User chooses to continue, Screen Dos opens the official release page or Release Notes in the operating system’s default web browser. Screen Dos does not itself download an artifact or automatically update itself.
  1. If the User opens a Nagori Soft official website or Direct Download in the browser, the browser may connect to `nagorisoft.com`, `downloads.nagorisoft.com`, or another displayed Nagori Soft endpoint, and Cloudflare or other delivery infrastructure may process IP addresses and other technical metadata. This browser communication is separate from the Screen Dos Update API request.

7. Contribution Code Registration

  1. When a User explicitly registers or changes a Contribution Code in Screen Dos, Screen Dos connects over HTTPS to the Nagori Soft API Contribution verification service.
  1. The current request includes:

(a) the Contribution Code entered by the User;

(b) the `appIdentifier` identifying Screen Dos;

(c) the Screen Dos `appVersion`; and

(d) the applicable `channel`.

  1. Although the Contribution Code is transmitted to the Nagori API for verification, Screen Dos does not persist the raw Contribution Code locally.
  1. The Nagori API Production D1 database also does not store the raw Contribution Code. It stores the derived value and Code-lifecycle information described in Section 5.
  1. If the Code is valid, the Nagori API returns a signed Receipt. The Receipt may contain a Version, identifiers, applicable application, scope, Contribution type, issuance time, and information identifying the Code as necessary to verify and use the Receipt as a Contribution record.
  1. Screen Dos verifies the Receipt’s signature and contents and stores the Receipt locally as the Contribution record.
  1. Under the current API contract, the Contribution verification request does not include the User’s name, email address, payment-card number, or other payment information.
  1. If a Contribution Code is revoked on the server, future verification of that Code will fail. Under the current architecture, however, a valid signed Receipt already obtained and stored locally is not automatically deleted remotely merely because the Code is later revoked.
  1. Remove from this device or an equivalent Screen Dos action deletes the locally stored Contribution Receipt and local Contribution state. It does not revoke the Contribution Code on the server.
  1. Whether a Contribution Code or Contribution record is present does not affect access to normal Screen Dos functionality.

8. Local Settings and Browser Storage

  1. Screen Dos Host settings are stored as JSON in `settings.json` within the operating-system-specific user data directory provided by Electron. In source-code terms, the path is `app.getPath('userData')/settings.json`. The specific absolute path varies by operating system and environment.
  1. `settings.json` may currently contain the locale, appearance, first-run state, selected network-interface information such as interface name and local address, whether the PIN feature is enabled, image quality, connection URL suffix, trusted VPN CIDR, the signed Contribution Receipt, and other settings necessary for Screen Dos operation.
  1. The raw Contribution Code is not retained as a persistent local setting.
  1. Screen Dos does not maintain a dedicated database or settings field for persistent connection history. Certain connection information may nevertheless be written to the application log described in Section 9.
  1. In the Viewer browser, the locale is stored in browser `localStorage`.
  1. A session ID and token needed for Viewer reconnection may be stored temporarily in browser `sessionStorage` and are designed to be deleted when the session reaches its ended state.
  1. Screen Dos provides an in-app function for deleting the Contribution Receipt. As of Version 1.0, Screen Dos does not provide an in-app function that deletes all settings at once. If a User chooses to remove application data through the operating system, the User should first exit Screen Dos and independently determine whether any settings should be backed up.

9. Application Logs and Diagnostic Reports

  1. Screen Dos stores a local application log. In source-code terms, the location is `app.getPath('logs')/Screen Dos.log`; the actual absolute path varies by operating system and environment.
  1. The application log may contain connection events, Viewer IP addresses, shortened session IDs, local network-interface addresses, image-quality settings, connection or application state, error information, and other technical information useful for diagnostics.
  1. Log files rotate at approximately 2 MiB per file. The design retains the current log and up to five prior generations. There is no fixed day-based retention period.
  1. Users can open the log folder from the Help menu. Screen Dos does not provide a dedicated in-app function to delete all logs; a User who wishes to delete them does so manually using the operating system.
  1. A diagnostic report is saved only when the User explicitly chooses to save one and is written as a JSON file to a location selected by the User. The report is designed to redact information including IP addresses, URLs, PINs, tokens, and screen or window names.
  1. A diagnostic report is not automatically transmitted to Nagori Soft. Nagori Soft does not receive it unless the User chooses to provide it, for example when contacting Support.
  1. Screen Dos does not automatically transmit telemetry, analytics, advertising data, crash reports, or shared-screen data to Nagori Soft or another external service.

10. Information Not Received by Nagori Soft During Ordinary Use

Based on the currently verified Screen Dos Version 1.0 and Nagori API architecture, Nagori Soft does not receive, store, or relay the following information for ordinary screen sharing:

  1. video or image content of a shared screen;
  1. User files or file contents;
  1. Screen Dos connection PINs, Viewer reconnection tokens, or other secrets used to participate in a screen-sharing session;
  1. usage telemetry or analytics transmitted merely because Screen Dos starts, remains idle, or is used for ordinary screen sharing; or
  1. content of the screen-sharing session processed directly between the Viewer and Host.

Because remote-input functionality is not implemented in Version 1.0, Nagori Soft also does not collect or relay remote-input content.

A Contribution Code is transmitted to the Nagori Soft API when the User registers it and therefore is not included among the categories described as not received above. When a User performs an Update check, the channel, platform, and other request information described in Section 6 are transmitted.

11. User Choices and Third-Party Services

  1. If a User does not register or change a Contribution Code, no Nagori API communication occurs for Contribution verification.
  1. If a User does not perform an Update check, no Nagori API communication occurs for that Update check.
  1. Under the current design, unavailability of the Nagori API does not prevent normal Screen Dos startup, screen sharing over a trusted local network or private VPN, or use of local settings.
  1. A previously stored valid Contribution Receipt can be verified locally without a continuous connection to the Nagori API.
  1. Users may use the relevant Screen Dos action to delete the Contribution Receipt and local Contribution state stored on the current device.
  1. If a User explicitly opens a License, Privacy, Support, Release Notes, or other web link, the operating-system default browser or another applicable browser may connect to the Nagori Soft official website or another displayed website.
  1. If a User uses a VPN, the VPN provider’s terms apply to that provider’s handling of network metadata and other information.

12. Contact and Language

  1. Questions concerning User Information handled by Screen Dos or this document may be sent to:

privacy@nagorisoft.com

  1. For general usage or technical support concerning Screen Dos, Nagori Soft Support is available at support@nagorisoft.com.
  1. Both the Japanese and English versions of this document are authoritative versions.
  1. The two language versions are intended to have the same content and legal effect.
  1. If there is any difference in wording or question of interpretation between the Japanese and English versions, they will be read together and interpreted in the manner that best gives effect to their common intent. Where applicable law requires a particular treatment, that law will apply.

Nagori Soft