Security & privacy
Security
What protects a session, and what the service can see.
Remote access hands one computer control of another. Here is what actually protects that, in plain terms.
The short version
- Sessions are locked end to end. The keys are made by your two computers. The service never gets them.
- A relay carries locked data. It passes packets it cannot read.
- Only your account gets in. The coordinator introduces devices that belong to the same account, and nothing else.
- Sharing is off until you turn it on.
- Every computer can be revoked. Removing it drops it from your fleet at once.
What the service can see
| It knows | It cannot see |
|---|---|
| Which computers exist and what you called them | Anything on a screen |
| When a session started and how long it ran | Anything you typed |
| Direct or relay | Anything you copied |
| Speed, delay and loss numbers | The contents of any frame |
That split comes from how it is built, not from a promise. Session content is locked between your two computers, so there is no point where it exists in the open.
What is up to you
- Your account password. It is the gate, so it carries the weight.
- Who is in your organisation. See users and teams.
- How long a computer keeps access. Prune Devices when machines change hands.
- Whether to switch on the code check.
- Whether to run it yourself. See self-hosting.