Nothing to hijack.
Present Tense was designed so that sharing your screen never means handing it over. Here is what that means in practice.
The audience gets a copy, not your session
What reaches your audience is a description of your page, rebuilt as a read-only copy in their browser. There is no logged-in page underneath it, so there is nothing for anyone to click, type into or take over.
Your browser
Your real, logged-in page. Only you use it.
Their browser
A read-only copy with no session, no cookies of yours and no way to act as you.
Nobody drives your screen
The audience can scroll, zoom and read their own copy. None of that is sent back to your browser, and your page only changes when you change it. Audience suggestions are planned; if we add them, they will stay suggestions you choose to show.
Our relay passes your page along without reading it
Each update travels through our relay as packed data with a small label on the outside. The relay reads only the label, to put updates in order and send them on. It has no code for reading what is inside; only the Present Tense code in your browser and your audience's browsers unpacks it.
This is a design boundary, not end-to-end encryption. We will say so plainly until that changes.
What we keep
To let late joiners catch up, we keep recent snapshots of a live session while it is live. Session content is held in memory and discarded when the session ends. Recording is off. The retention and deletion policy is set out in our privacy policy and data-handling page.
What you should still check
Only the tab you present is shared. Unlike a screen share, your other tabs, apps and system notifications stay on your machine.
Everything on that tab is visible to the audience, the same as on the projector. Check it for private messages or personal details before you start.
Report a problem
Found a security issue? Email security@present-tense.io. We reply to every report.
Try it in a real room.
We're letting people in by email while we test in real venues.