Technada Remote Privacy Notice
This notice explains what Technada Remote sends, what stays on your device, and what happens while a remote support session is active.
Effective August 23, 2026
Who operates Technada Remote
Technada Remote is operated by Technada Services Inc.. It is a modified open-source remote support application used to provide authorized support to customers.
Technada Remote uses Technada-operated rendezvous and relay infrastructure at remote.technada.ca. The application is built so customers cannot redirect it to another rendezvous server.
Information used to establish a connection
Technada rendezvous and relay server
The client sends its Technada Remote peer ID, public-key exchange information, and network connection candidates to remote.technada.ca so the two endpoints can find and verify each other. If a direct peer-to-peer path cannot be established, the support session may pass through the Technada relay. Relayed session traffic is encrypted between the two endpoints.
Public STUN services
On startup, the client sends standard STUN binding requests to public STUN services operated by Google, Cloudflare, and Nextcloud. These requests are used for NAT traversal so a direct connection can be attempted.
The STUN request contains no remote-session content and no Technada account identifier. The STUN operator can observe the source IP address making the request.
technada.ca
Technada Remote does not automatically send usage information to technada.ca. Product, support, documentation, privacy, source, and legal pages open in your browser only when you choose the corresponding link.
No analytics or automatic update telemetry
- Technada Remote contains no analytics SDK or usage-tracking SDK.
- It contains no crash-reporting service that automatically uploads crash data.
- It does not automatically send your hostname, signed-in username, hardware inventory, or installed-software inventory to Technada.
- It does not perform an automatic update check or download an update from an upstream service.
Information stored on your device
Technada Remote keeps configuration and logs locally on the device. These folders are not automatically transmitted to Technada.
Configuration can contain the device peer ID, encryption key material, preferences, and an unattended-access password if you choose to set one. The unattended password is stored in hashed form rather than as readable text.
Logs contain connection and NAT-traversal events, peer IDs, peer IP addresses, and error information. Logs rotate daily and are retained locally for 31 days.
Logs do not contain your screen content, keystrokes, clipboard content, or the contents of transferred files.
What happens during a support session
Technada Remote supports attended sessions, where a person at the device accepts the incoming connection, and unattended sessions where the device owner has deliberately configured a permanent password. No Technada build ships with a default permanent password.
Session visibility and control
An active session is shown on the controlled device. The customer can end the session from the Technada Remote session panel. Ending the session terminates the remote party's access.
Permissions
Depending on the session and platform, remote support capabilities can include screen viewing, keyboard and mouse control, clipboard access, file transfer, audio, terminal access, remote restart, screen recording by the remote side, and blocking local input. The customer can revoke supported session permissions from the active-session panel.
Clipboard and display state
While a session is active, the client can subscribe to the local clipboard so clipboard transfer works, and it keeps the display awake so the machine does not sleep during active support. The clipboard listener is removed when the session ends.
Session recording
Automatic session recording is off by default. Technada Remote does not silently enable automatic recording as part of installation.
Infrastructure used by the client
The connection process uses Technada's own remote-access server plus the public STUN services described above.
Technada Remote is based on RustDesk open-source software. The client does not use RustDesk's public rendezvous infrastructure or RustDesk's upstream updater in a Technada build.
Your choices
- You can decline an attended support request.
- You can revoke supported permissions during an active session.
- You can end an active session from the customer-side Technada Remote panel.
- You can choose whether to configure unattended access.
- You can uninstall Technada Remote when you no longer want the software installed.
Security
Technada Remote uses cryptographic peer verification and encrypted session transport. Technada also fixes the client to Technada-managed rendezvous infrastructure and disables alternate-server routing and upstream self-update behavior in Technada builds.
Changes to this notice
When this notice is updated, the effective date at the top of the page identifies the version currently published for Technada Remote.
Privacy questions
Contact Technada Services Inc. if you have a question about Technada Remote or this notice.
Contact Technadahello@technada.ca
205-10255 Yonge St, Richmond Hill, ON L4C 3B2