Avyn
Get Avyn

VERIFY AVYN

Don’t trust us. Verify it.

You should be able to understand how Avyn communicates. Here is the path to checking it for yourself.

Tested versions. This guide was verified on 22 October 2026 on Windows 11 with the direct download (Avyn Agent 0.1.0-alpha.42) and the Microsoft Store version (1.2.5.0), using an Android phone. Results may vary with your network, your Windows version and the Avyn version.

  1. Identify the Agent's connections.

    Avyn Agent runs as Avyn.Agent.exe. In the direct download it is in %LocalAppData%\Avyn.Agent\current; in the Microsoft Store version, inside C:\Program Files\WindowsApps. In PowerShell, Get-NetTCPConnection -OwningProcess (Get-Process Avyn.Agent).Id lists its TCP connections and Get-NetUDPEndpoint -OwningProcess (Get-Process Avyn.Agent).Id its UDP ports.

  2. Separate local traffic from external traffic.

    At rest, the Agent listens on TCP 47821 (connection with the phone) and UDP 47822 (discovery on your local network); the optional unlock service listens on TCP 47822. At startup, the Agent also probes TCP port 8002 on the addresses of your subnet (up to 254) to look for Samsung TVs, even if you have none paired: this is local traffic and does not leave your network. With a phone controlling the PC, we saw connections only from the phone's address (192.168.1.150 in the test) to port 47821.

  3. Understand the legitimate exceptions.

    In the direct download, the Agent checks for updates at startup and every 6 hours. In the test it contacted api.github.com, github.com and release-assets.githubusercontent.com on port 443; GitHub receives your PC's IP address, as any website does. The Microsoft Store version does not declare Internet access and, in 80 seconds of observation, opened no connections: the Store updates it. If a Samsung TV is present, the Agent talks to it inside your network. For now there is no setting to turn off the update check; if you do not want it to run, block the Agent's Internet access (next step).

  4. Restrict Internet with Windows Firewall.

    From an administrator PowerShell, this rule blocks the Agent's outbound connections to the Internet and keeps the local network: New-NetFirewallRule -DisplayName 'Avyn Agent - sin Internet' -Direction Outbound -Program 'RUTA\Avyn.Agent.exe' -Action Block -RemoteAddress Internet. Replace RUTA with the path of your installation. To undo it: Remove-NetFirewallRule -DisplayName 'Avyn Agent - sin Internet'. In the test, with the rule in place, the Agent's connections to GitHub no longer left the PC; Windows still queried DNS for those names, because a system service makes those queries, not the Agent. Also, the first time the direct download runs, Windows shows a firewall prompt; until it is allowed, the phone cannot connect. With the rule in place the Agent cannot check for updates either: install new versions manually.

  5. Repeat everyday actions.

    With the Microsoft Store version, an already paired phone and the blocking rule in place, pointer control, volume and browsing the shared folders worked. Also try pairing, file transfers and unlocking with the rule in place, and record what works, what changes and which product version you used.

  6. Read the source code.

    Avyn's source code is still private. The public repository github.com/pablopramparo/avyn-releases only contains the installers and the update manifest. We will add a link to the code once it is public.

Evidence, not a blanket promise.

This guide lists the tested versions, the conditions and the limitations. It does not claim that every feature works with all Internet traffic blocked: check the ones you use.

Public source link coming later.