Show your client the way,
don't explain it in words

Co-browsing is a real-time view of the client's browser. Unlike screen sharing, the client doesn't need to install any software or share their entire desktop — the agent only sees the web page, not other windows or applications.

No. PeekDesk works as a lightweight JavaScript widget embedded on your site. The client clicks a button, gives consent, and it's done. No downloads, browser extensions, or registration required.

Each company receives a unique API key that they place in the snippet on their site. The server verifies the key with every connection and checks if the domain is authorized. Unauthorized connections are immediately rejected.

Domain whitelisting means the PeekDesk widget will only work on pages you've previously authorized in the admin panel. Even if someone copies your snippet to another site, the server will reject the connection because the domain isn't on the allowed list.

No. PeekDesk works in read-only mode. The agent can see the client's screen and point at elements with a cursor or draw with a laser, but cannot click, type, or control the client's browser. Full control always remains with the user.

Nothing — literally. PeekDesk doesn't save recordings, screenshots, or session logs. Transmission data is streamed in real time via WebSocket and never hits the disk. After disconnection, session memory is immediately freed on the server.

Yes. PeekDesk meets GDPR requirements by design: it requires explicit user consent, doesn't collect personal data, doesn't create cookies, doesn't store recordings, and sessions are ephemeral. Data minimization is built into the architecture — no additional configuration needed.

Fields of type and elements marked as sensitive are automatically masked during transmission. The agent sees the interface, buttons, and page content, but never has access to passwords and confidential data entered by the client.

The widget loads asynchronously and weighs just a few kilobytes. Recording (rrweb) and transport (Socket.io) libraries are loaded from CDN only after the button is clicked — before that, only a small button is present on the page. The performance impact is imperceptible.

The PeekDesk server has built-in mechanisms to limit the number of connections per API key and IP address. This protects against both brute-force attempts and DDoS attacks. Each API key has configured limits, and suspicious traffic patterns are automatically blocked.

PIN rotation is an additional security layer. If the agent doesn't join the session within 60 seconds, the system automatically generates a new code. This way, even if someone sees the PIN on the client's screen, it becomes useless after a moment. It's the same mechanism banks use for one-time tokens.