Privacy
What Present Tense collects, why, how long it keeps it, and what you can ask us to do with it.
Who we are
Present Tense is a presentation tool made by Sentence Labs, based in India. We are the data controller for the personal data described in this policy, which covers present-tense.io, console.present-tense.io, and the Present Tense browser extension.
For anything privacy-related — a question, a request, or a complaint — write to hi@present-tense.io. A person reads it.
What we collect
Account: your display name, email address, and a password. We store the password only as a salted hash (argon2id) and never in plain text. Beta access is by invitation.
Sessions: when you present, the tab you choose is sent to our server as its structure and text — updates and periodic snapshots, with images, stylesheets, and fonts bundled in so your audience can render it. Large pages are uploaded over an encrypted HTTPS connection and held by our server in memory only (never on disk); the audience fetches them the same way. Input values are masked before anything leaves your browser: password and email fields are always masked, and any field you mark private is dropped. Our server does not read the content; it passes the bytes through and forwards them. The browser extension asks you to confirm what is captured the first time you present, and the toolbar badge reads REC while a tab is being captured.
Session history: the title, schedule, and start and end times, plus aggregate counts such as peak watching, so you can find past sessions.
Technical data: connection logs needed to run and secure the service — IP address, browser type, and timestamps — including the data required to keep a session working through a reconnect.
What you send us: the email you add to the waitlist, and any feedback or bug report you submit, together with the context a bug report includes.
Operational data
To support and improve the service we collect operational data about how sessions run: when people join, leave, or reconnect; 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 (for example video or an embedded frame).
This data is metrics, never content. It contains no page text, no attributes, no images, and no full addresses — only the site's hostname. A capture problem is recorded as a stage and an error name, never the error's payload.
Detailed per-session data is kept for 7 to 30 days, then reduced to small daily totals and deleted. Those totals are kept to see trends. You can ask us to delete your data at any time at hi@present-tense.io.
What we don't collect
Your screen or camera, your other tabs, other applications, or notifications. Keystrokes outside the presented page. Nothing an audience member does is sent to the presenter's browser beyond an aggregate reaction count.
We do not use advertising or cross-site tracking cookies, and our analytics are cookieless — no personal identifiers, no data sold or shared with ad networks. See the cookies page for detail.
How we use it
To provide the service: deliver your session to the audience, let people join, and bring late joiners up to date. To keep accounts secure: sign-in links, protection against cross-site request forgery, and abuse prevention. To support and improve the product: respond to bug reports and understand aggregate usage. To tell you about changes to the beta or these terms.
Where the law requires a lawful basis, we rely on performing our agreement with you, our legitimate interest in running and securing the service, and your consent for anything optional. You can withdraw consent at any time.
How long we keep it
Live session content: in memory, only while the session is live. It is not written to the database and is discarded when the session ends or the service restarts. Large page states (uploaded over HTTPS) are held in the same in-memory store, capped per session and across the host.
Leave-behind snapshot: in memory, for the life of the session; the final snapshot is kept so the shareable leave-behind link can render it.
Account (name, email, password hash): until you delete your account or the beta ends.
Session history: until you delete your account; deleting your account cascades your sessions.
Invites and sign-in tokens: until they expire; expired invites are pruned.
Waitlist leads, feedback, and bug reports: for the duration of the beta.
Database backups: encrypted, kept for a rolling window (14 days by default), then deleted automatically.
Connection logs: a short operational window.
Operational data: per-session detail for 7 to 30 days, then reduced to small daily totals and deleted; the totals are kept to see trends.
Recordings: disabled during the beta. If we enable them, we will set a retention period and tell you first.
Where it is stored
Our API and database run on Hetzner in Germany, within the European Union. Encrypted backups are held in Cloudflare R2. Email is delivered by Resend. The site and apps are served from Cloudflare's global edge.
Some of these providers may process data outside your country, including outside India. Where the law requires it, we rely on appropriate safeguards for those transfers.
Security
Passwords are stored as argon2id hashes, never in plain text. Traffic is encrypted in transit with TLS. Sign-in and security cookies are HttpOnly and Secure, and forms are protected against cross-site request forgery.
Staff access to our admin console is gated at the edge and authorized on the server, and is limited to account and session metadata for support — not session content. Backups are encrypted at rest.
No system is perfectly secure. If you believe you have found a problem, tell us at security@present-tense.io and we will look into it.
Your rights
You can ask us to access, correct, or delete your personal data, and you can ask us to restrict or object to certain processing or to withdraw consent where we rely on it. Write to hi@present-tense.io; deleting your account cascades your decks and sessions.
Under India's Digital Personal Data Protection Act you may also nominate another person to exercise your rights on your behalf, and you may raise a grievance with us first at hi@present-tense.io. We respond within a reasonable period.
Changes to this policy
We will update this page and the date above when this policy changes. For material changes we will tell account holders by email. If we change what the browser extension collects, we will also tell you in the product after you install it. Continuing to use Present Tense after a change means you accept the updated policy.
Contact
hi@present-tense.io
Try it in a real room.
We're letting people in by email while we test in real venues.