Security
How WollConnect secures a session
Remote support means someone sees a screen that is not theirs and operates it. Anyone offering that should be able to answer who can read along, who is allowed to connect, and what can be reconstructed afterwards. This page answers that without marketing vocabulary.
Ask a security question See cloud plans
End-to-end encrypted between viewer and agent
Viewer and agent agree on a session key directly with each other, using a Diffie-Hellman exchange on curve P-256. From the shared secret both sides derive the working keys with HKDF-SHA256 and confirm them to each other before any payload moves. Encryption is AES-256-GCM, so it is authenticated: modified data is detected and discarded.
The server relays the connection but does not hold the key. Screen content, input and transferred files pass through it as opaque packets. That is the difference between "encrypted in transit" and "end-to-end encrypted": transport encryption protects against someone on the wire, but not against the intermediary itself.
In production over the relay this is not optional but required, and falling back to unencrypted payloads cannot be switched on there. Keys are rotated during a running session.
Nothing has to be opened in the firewall
Agent and viewer each connect outbound and meet on the relay. No inbound rule and no port forwarding are required on the customer's network.
The practical gain is not convenience. It is that no permanently reachable entry point exists for someone outside to find — including during the weeks when nobody is supporting anything.
Who may connect is decided in advance
Rights sit on the individual user and are granted one at a time: access to assigned machines, access to all, managing assignments, deploying software, writing scripts, running scripts, patching. A technician sees a customer's machines only if assigned to that customer.
Portal sign-in supports two-factor authentication. For attended sessions the user confirms the connection on their screen and can end it at any time.
- Sessions are recorded with time, technician and machine
- Job output is retained in full, including weeks later
- Credentials are stripped from collected logs before they are stored
Data protection and location
WollConnect is developed in Germany and operated from a German data centre. For cloud use we provide a data processing agreement under Article 28 GDPR.
If you would rather not hand that over at all, run WollConnect yourself — your own database, your own certificates, your own relay. Then no traffic leaves your network.
Frequently asked questions
Can the operator read the screen content?
No. The session key is negotiated between viewer and agent (ECDH P-256, HKDF-SHA256) and payloads are encrypted with AES-256-GCM. The relaying server does not hold that key.
What happens if end-to-end encryption cannot be established?
In production over the relay the session does not start. Falling back to unencrypted payloads cannot be enabled there.
Where is the data processed?
In a German data centre. For cloud use we provide a data processing agreement under Article 28 GDPR. With the on-premises edition all data stays inside your own network.
Does the firewall have to be opened?
No. Both sides connect outbound to the relay; inbound rules are not required.