Security, in plain words

Who can get into your computers, what they can see, and what we can’t.

Encrypted end to end, and direct when it can be

Your devices connect straight to each other whenever the network allows it, so no server sits in the middle of your session. Every connection is encrypted end to end, from one device to the other.

For the technically minded: each device makes its own key pair (Ed25519) the first time it runs, and the private key stays on the device. Devices talk over QUIC with TLS 1.3, and each checks the other’s key before anything else happens. The screen stream then sets up keys of its own (X25519) for that session, so every session, and every reconnect, starts with fresh keys.

Relays pass along what they can’t read

Some networks, many office and mobile ones among them, won’t let two devices reach each other directly. Then the connection goes through a relay. The relay forwards traffic that’s already encrypted between your two devices. It never has the keys, so it can’t see your screen or what you type.

The app always shows which path you’re on: Direct or Relay.

Trust is given on the computer itself

A computer lets a device in unattended only after someone at that computer has trusted it and confirmed with Touch ID, Windows Hello or the system password. Nobody can do that from somewhere else.

Unattended access is also a setting on each computer. With Ask each time, someone there approves every session, trusted device or not.

Your phone unlocks before it opens anything

Before your phone opens an unattended session, it asks for your fingerprint or PIN. A lost or borrowed phone can’t open your computers on its own.

A notice on every session

While anyone is connected, the computer shows who it is, how long they’ve been connected, and a Stop button. It shows during unattended sessions too, so anyone at the computer can see what’s happening and end it.

The computer keeps a log

Each computer writes down every session it hosts: which device, when, for how long, view or control, and whether anyone was there. Keystrokes are counted, never recorded. The log is a file on that computer.

One session, as the host computer logged it
{
  "event": "session_end",
  "peer_name": "Your phone",
  "mode": "control",
  "attended": false,
  "started": 1791312086,
  "secs": 754,
  "counts": {
    "clicks": 37,
    "keys": 212,
    "text_chars": 148
  }
}
  1. Nobody was at the computer: an unattended session.
  2. How many characters were typed. Never which ones.

Revoke a device, and it’s out

Remove a device from a computer’s trusted list and its access ends at once. If it’s connected at that moment, the session stops.

Helping someone: their say, every time

Help sessions start from a code the other person shares. Nothing begins until they allow it, they choose view only or full control, and a request nobody answers expires after 30 seconds. They see the notice the whole time and can stop the session whenever they like. A help session isn’t added to your devices.

No AI, and little for us to know

Veolan has no AI features. Your screen isn’t analysed, summarised or used to train anything.

Your Veolan account knows how you sign in and which devices you’ve linked to it. It doesn’t receive your screens, what you type or your session logs.

Your computers, kept yours.

Create an account for early access. If you have a question about how Veolan works, the answer belongs on this page.