Privacy

Plain-language explanation, not a legal document. Last updated August 2026.

The short version

TelePrompter doesn't have a server, a database, or a login. There's no account to create and nothing about you to store on our end, because there is no "our end" in the usual sense: this is a static site, and everything it does happens inside your own browser.

What's stored, and where

Your scripts, and settings like speed, theme, and font, are saved in your browser's local storage on your own device. That data never leaves your device unless you explicitly export it (as a .txt or .json file you choose to save) or import a file yourself. Clearing your browser's site data for this page removes it completely, since nothing exists anywhere else to restore from.

What isn't collected

No account, no email address, no sign-up of any kind
No analytics or tracking scripts
No advertising, and no ad networks with access to your usage
No cookies used for tracking (a service worker caches files for offline use, which is not the same thing and doesn't identify you)

Third-party services this app talks to

A handful of features load small libraries or make requests to services we don't operate, only when you actually use the feature that needs them:

Google Fonts, for the typefaces used throughout the interface
mammoth.js and pdf.js (via cdnjs), loaded only if you import a .docx or .pdf file, to read the file's text in your browser
PeerJS (via unpkg), loaded only if you turn on remote control, to help your phone and computer find each other over WebRTC. After that initial handshake, control messages travel directly between your two devices, not through PeerJS's servers or ours
QR Server (api.qrserver.com), used only to render the pairing QR code as an image when remote control is on

None of these services receive your script content. Remote control only ever sends short commands like play, pause, or a speed change, never the text you're reading.

Microphone, camera, other permissions

TelePrompter doesn't request camera or microphone access. If a feature is ever added that would need one, it'll be opt-in and asked for at the moment it's actually used, the same way remote control's network access is today.

This page describes how the app is built and what it does, in plain terms, so you can decide for yourself whether that works for you. It isn't a substitute for legal advice and isn't a formal privacy policy or terms of service document.