Effective Date: April 17, 2026 | Last Updated: April 17, 2026
This privacy policy describes how Amni-Connect, an end-to-end encrypted remote desktop tool developed by Amni-Scient ("we", "us", "our"), handles user information.
We collect nothing. Amni-Connect has no account system, no registration, no sign-in, and no cloud backend operated by Amni-Scient. The application binary contains no analytics SDK, no crash reporter, no usage pings, and no telemetry of any kind. Screen frames, keystrokes, and mouse input never pass through any server operated by Amni-Scient.
All media (screen video, audio if enabled, and input events) travels over WebRTC between the host and viewer directly. WebRTC uses DTLS-SRTP, which encrypts payloads end-to-end with keys negotiated peer-to-peer. The signaling server that helps the two peers find each other sees only session-description metadata (IP candidates, codec offers) — it never sees frames or keystrokes.
Amni-Connect ships a Node.js + Socket.IO signaling server (server.js) that you host yourself on any machine — a VPS, a home Raspberry Pi, your LAN, anywhere. The default port is 3389. This server:
Because you run the signaling server, Amni-Scient has no visibility into who connects, when, or to what. We do not operate any hosted signaling service.
The Rust input daemon (amni-control) listens on 127.0.0.1:7878 — localhost only, never bound to a public interface. It receives JSON input events over that local socket and calls enigo to synthesize mouse and keyboard actions. The daemon does not read the screen, does not open files, and does not make outbound network requests of any kind.
Amni-Connect stores very little on disk:
.env file on the signaling host for configuring port and allowed originsThere is no "cloud backup", no sync folder, and no auto-upload.
Amni-Connect does not record sessions. Frames are transient WebRTC media — rendered on the viewer, discarded after the browser jitter buffer ages out. Closing either the host app or the viewer tab ends the session and releases all memory associated with it.
The application opens network sockets for the following purposes only:
No traffic routes through Amni-Scient servers at any point. We literally have no way to observe your sessions.
Amni-Connect depends on upstream open-source libraries (Electron, Socket.IO, the enigo crate, the WebRTC implementation shipped with Electron/Chromium). Each has its own license and privacy behavior; by default, none of them phone home in the configuration Amni-Connect ships. Review each project’s own policy if you enable optional features (e.g., telemetry flags, auto-updaters) that ship with those libraries upstream.
The amni-scient.com website that hosts this policy displays advertisements provided by Google AdSense. Google’s AdSense SDK may collect and process data (cookies, device info, IP, ad interactions) as described in Google’s Privacy Policy. This applies only to the website. The Amni-Connect desktop application contains no advertisements and no AdSense code.
We do not sell, trade, share, or transfer any user data to third parties — because we do not collect any user data from the application in the first place. The only third-party data processing is through Google AdSense on the website (Section 9), governed by Google’s privacy policy.
We retain no user data. Any session state lives only in the memory of your own signaling server and your own devices until processes exit or machines reboot.
Amni-Connect relies on the native WebRTC DTLS-SRTP stack for media encryption and on the operating system’s TLS implementation for signaling transport. Input traffic between the Electron host and the Rust daemon stays on loopback (127.0.0.1) and never leaves the machine. You are responsible for securing your own signaling server (firewall, TLS reverse proxy, origin allowlist).
Amni-Connect is not directed at children under 13. Because the application collects no data at all, there is no child-specific data collection to disclose.
Since we collect no personal data, there is no personal data held by Amni-Scient to access, modify, export, or delete. Your session metadata is fully under your control — it lives on your own signaling server and your own devices. To manage AdSense data collection on the website, use an ad blocker, adjust browser cookie preferences, or opt out of personalized ads via Google Ad Settings.
We may update this privacy policy to reflect changes in the application or applicable laws. The "Last Updated" date at the top will be revised accordingly. Continued use of Amni-Connect after changes constitutes acceptance of the revised policy.
For questions or concerns regarding this privacy policy: