Data handling
What a captured session contains, who can access it, and how long it is kept.
In short
A captured session is the page you choose to present, sent as its structure and text — not a video and not your screen. It lives only while the session is live, and it is gone when the session ends. Recordings are off during the beta.
What a captured session contains
The page's structure and text — the tab you're presenting, sent as updates and periodic snapshots. Images, stylesheets, and fonts from that page are bundled in, so the audience can render it.
Large pages travel over an encrypted HTTPS connection, held by our server in memory only — never on disk — and fetched by the audience the same way. The upload is authenticated with your presenter key.
Input values are masked before anything leaves your browser: passwords and email fields are never sent, and any field you mark private is dropped. Our server never reads the content — it passes the bytes through and forwards them.
What it does not contain
Your screen or camera, other tabs, other applications, notifications, or keystrokes outside the presented page. Audience members see a script-free replica, and nothing an audience does is sent back to your browser beyond a reaction count.
Who can access it
The presenter, who owns the session. The audience, while the session is live, using the join code or link. Sentence Labs staff, through the internal admin console, only for support and only for account and session metadata.
Session content itself is not stored: it is held in memory by our server for the duration of the session and discarded when the session ends or the service restarts.
How long we keep it
Session content: in memory, only for the life of the session. It is not written to the database and is not kept after the session ends. Large page states are held the same way (in memory, capped), and the final snapshot is kept so the shareable leave-behind link can render it.
Account data (name, email, password hash): until you delete your account or the beta ends.
Session history (title, schedule, end time): kept so you can find past sessions; you can delete it with your account.
Nightly database backups: encrypted and retained for a rolling window, then deleted automatically.
Recordings: disabled during the beta. If we enable them, we will set a retention period and tell you first.
Operational data
Alongside a session we collect operational data about how it runs: joins, leaves, and reconnects; connection quality, summarized per minute; traffic sizes by message type; and counts of events, such as a viewer catching up after a drop or a page feature that couldn't be captured.
This data is metrics, never content. It contains no page text, no attributes, no images, and no full addresses — only the site's hostname.
Per-session detail is kept for 7 to 30 days, then reduced to small daily totals and deleted. Staff see it through the internal admin console, for support, under the same limits as session metadata.
Questions and requests
Ask us to access, correct, or delete your data any time at hi@present-tense.io. See our privacy policy for the full picture.
Try it in a real room.
We're letting people in by email while we test in real venues.