← DeskJoin Control

DeskJoin Control · Legal

Privacy Policy

Effective September 13, 2026 · Last updated October 14, 2026

1. Scope

This Privacy Policy explains how DeskJoin ("DeskJoin," "we," "us," or "our") handles information in connection with DeskJoin Control, its pages at deskjoin.app/control, downloads, update services, and support communications (the "Service"). DeskJoin Control is available for Windows and macOS. Supported systems and features vary by version; see the product's download and release-notes pages.

2. Information processed on your devices and local network

To discover a computer, establish a session, and transfer control, the app may process computer names, operating-system information, local network addresses, service records, connection settings, session identifiers, pointer movement, mouse buttons, scrolling, keyboard input, and modifier-key state.

A computer name can contain a person's name and may be visible to other devices during local discovery. Input events may reveal sensitive material when you type into the connected computer. Choose the destination computer carefully before moving control.

3. Information DeskJoin receives

App workflow reports and analysis

Versions with reporting send limited operational events to DeskJoin over HTTPS. The current reporting endpoints count successful pairings and successfully established control connections. Connection counts measure sessions, including successful reconnections, not the number of people or devices currently online. We use these statistics to understand aggregate feature use and workflow activity and to guide product improvements, not to analyze what you type or do on the connected computer.

A report identifies the event type and count and may include a random per-event identifier to prevent duplicate counting when a request is retried. This identifier identifies an event, not a person, account, or device. We store event identifiers, event types, counts, receipt times, and daily and cumulative totals in our Cloudflare-hosted database.

Workflow report payloads do not collect information about you personally, such as your name, email address, phone number, or account details. They also do not include computer names, persistent device identifiers, local network addresses, pairing credentials, keystrokes, typed text, pointer movements, mouse clicks, screen content, clipboard content, or files. A report that a pairing or connection succeeded does not send the paired device's identity or the content exchanged during that connection.

Cloudflare processes routine connection information, including the request IP address, to deliver reports and limit repeated requests. Our workflow counters do not store IP addresses. These reporting requests are separate from the direct local-network connection that carries keyboard and mouse input between your computers.

Website visits, downloads, and updates

DeskJoin does not receive keyboard, mouse, or local discovery data through the control connection. Website, download, and update requests are separate internet connections. Hosting providers may process routine request information such as IP address, browser or user-agent details, requested page or file, referring page, and request time to deliver and protect these services.

The product page and download buttons send a page or download identifier to our counters. We store daily and cumulative totals, not a visitor or device identifier. Download counts measure button clicks, not completed downloads or installations. Control pages do not load the Google Ads tag. Desktop update checks use Sparkle on macOS and WinSparkle on Windows and may include app or operating-system information in request headers.

Local diagnostics

The desktop apps keep technical logs locally. Depending on the platform and version, these may include computer names, device and session identifiers, local network addresses, connection and pairing status, errors, and pointer or button activity. The current macOS packet logger omits keyboard-event details but can record mouse buttons, movement, scrolling, and modifier-key state. Local logs are separate from the limited workflow reports described above and are not automatically uploaded with them.

Support communications

If you contact support by email, we receive the address, message, diagnostics, and attachments you choose to provide. Review diagnostic information before sending it and do not include passwords or confidential input.

The macOS Bug Report action prepares an email with app and operating-system version information and a local log attachment. It opens a mail composer rather than automatically sending the report. Review or remove attachments before sending: logs may contain the local device and input-activity details described above.

If you use the website Support form, we receive your selected topic, message, and optional reply email address. We store these with the product name, a random submission reference, receipt time, and handling status in our Cloudflare-hosted database. Messages are private and accessible through our authenticated support inbox, not a public comment board. You can leave the email field blank, but we cannot reply by email without an address. The form does not automatically collect keyboard or mouse input, screen content, device details, logs, or files.

The Support form page does not load the Google Ads tag. Feedback text and reply email addresses are not sent as advertising conversion events. Cloudflare processes connection information, including the request IP address, to limit repeated submissions; we do not store that IP address in the feedback record. Contact support@deskjoin.app with your message reference for help or to request deletion.

4. Permissions

The app needs local-network access to discover and communicate with nearby computers. macOS also requires Accessibility permission to observe or send supported keyboard and pointer input. Windows Firewall may ask whether the app may communicate on the local network. Denying required access prevents the related feature from working.

5. Sharing and disclosure

Input is sent to the computer you connect to. We do not sell personal information or share it for cross-context behavioral advertising. Limited workflow-report, website, download, update, or support information may be handled by service providers that operate, secure, or maintain those services, including Cloudflare for workflow statistics, or disclosed when required by law.

6. Retention

Connection preferences, such as a remembered computer and its left or right position, may be stored locally on your device. Disconnecting ends the control session but cannot undo input already delivered to the other computer. The current macOS app rotates local diagnostic logs and prunes older files when its logging cleanup runs.

Workflow event types, counts, receipt times, and random event identifiers are retained for usage analysis and retry deduplication; the reporting database has no automatic expiration for these records. Daily and cumulative website and app totals may be retained. These workflow records do not contain personal details or keyboard and mouse content from the event. Support messages and attachments are retained as needed to respond and maintain support history; website feedback records remain until deleted through our administration tools. Routine website and operational records may be retained as reasonably needed for delivery, security, troubleshooting, and legal obligations.

7. Security

DeskJoin Control uses TLS 1.2 for pairing and reliable control traffic, including keyboard and mouse-button events. Device pairing records the peer identity and requires confirmation when a new or changed identity connects.

UDP limitation: pointer movement uses a separate unencrypted UDP path; the macOS implementation also sends scrolling and a low-latency copy of boundary-crossing messages over UDP. Session and sequence checks do not provide the confidentiality or cryptographic integrity of TLS. Someone able to capture or interfere with local traffic may observe or affect this activity. It is not accurate to describe all Control traffic as encrypted.

Use trusted computers on a trusted, secured local network and disconnect when control is no longer needed. No system can be guaranteed completely secure. Keep DeskJoin Control and the operating system current, and review pairing prompts before accepting them.

8. Your choices

You can disconnect or quit the app to stop sharing, deny or remove operating-system permissions, change the computer name shown during discovery, and remove locally saved preferences. Depending on where you live, privacy law may also provide rights regarding personal information controlled by DeskJoin.

9. Children

DeskJoin Control is a general-purpose utility and is not directed to children under 13 or the minimum age required by local law. We do not knowingly collect personal information from children.

10. Changes to this Policy

We may update this Policy as DeskJoin Control's features, security design, or legal requirements change. Revisions will appear on this page with a new last-updated date.

11. Contact

For privacy questions or requests concerning DeskJoin Control, contact support@deskjoin.app.