Your screen

Video travels directly between your browser and each viewer's browser over WebRTC, which encrypts it in transit. It is not recorded, relayed or stored by the server.

If a direct path cannot be found and a TURN relay is configured, the encrypted stream may be bounced through that relay. The relay still cannot read it.

What the database holds

For each share: the title you typed, your display name, your email address if you gave one, the share code, and the times it started and ended.

For each invitation: the recipient's email address, when it was sent, whether sending failed, and when the link was first opened.

For each viewer: the name they typed, their IP address, their browser's user-agent string, and when they joined and left. This exists so a host can see who watched their desktop.

Share codes and host keys

The share code in a viewing link is the whole of the access control, so it is generated from a cryptographic random source and is not guessable.

The host key that lets you drive a share is separate, never appears in a viewing link, and is kept in your browser tab rather than in the address bar.

Cookies and tracking

No advertising or analytics cookies are set. The app uses browser session storage to hold your host key for the tab you are sharing from, and that entry disappears when the tab closes.

Invitation emails

An address you type into the invite box is used to send that one message and is stored against the share so you can see who you invited. It is not added to any list.

If you gave your own email address when creating the share, it is set as the reply-to on those invitations so replies reach you rather than a no-reply mailbox.