Privacy policy

Last updated: September 24, 2026

This policy explains how the LecToCast website (lectocast.ayucode.com) and the LecToCast Chrome extension handle your data. In short: no account, no ads or tracking, and your screen is never stored.

Summary

  • No sign-up or sign-in. We do not collect personal information such as names or email addresses.
  • No ads and no third-party analytics or tracking.
  • Your screen and sound are encrypted and sent directly between the two devices whenever possible. They are never recorded or stored.
  • Your settings (cast ID, name, and so on) stay in your own browser.

Screen and sound

Casting uses the browser’s built-in WebRTC technology, and the screen and sound are encrypted (DTLS-SRTP). When a direct connection is possible, data travels only between your computer and the display PC. If the network does not allow a direct connection, it may be forwarded through an encrypted relay server. Either way, we never record, decrypt, or store what you cast.

Data used to set up connections

To let two devices find each other, our connection server temporarily relays the following, used only while connected:

  • The cast ID and the display name you optionally enter
  • Network information needed to connect (including IP addresses and connection parameters)
  • The version of the website or extension

The receiver’s connection mode, PIN, and failed-attempt count are stored on the server with the cast ID to enforce verification and prevent guessing; they contain no personal information. To prevent abuse, the server limits connection rates by IP address.

Data stored in your browser

The following stays in your own browser (localStorage and one language cookie) and is never uploaded. Clear your browser data at any time to delete it:

  • Receiver: cast ID, connection mode, whether to play sound
  • Presenter: display name, recent cast IDs and their labels, content type preference
  • lc_lang cookie: remembers the language you chose on the casting pages

Third-party services

ServicePurposeData it may receive
CloudflareWebsite hosting, connection server, encrypted relay (when enabled)IP address and request logs, handled under Cloudflare’s privacy policy
STUN servers (Cloudflare, Google)Help devices discover reachable network addressesIP address
PeerJS public server (0.peerjs.com)Connections compatible with the legacy extensionCast ID, IP address
Google FontsWeb fontsIP address, browser information

Chrome extension

The extension works the same way as the website: the cast ID is kept in the browser’s extension storage (chrome.storage), connections are set up through the PeerJS public server and STUN servers, and the screen is sent peer-to-peer. The extension does not read the pages you visit or collect browsing history.

Changes and contact

If this policy changes, the update will be posted on this page with a new date above.

For questions, contact us through the Chrome Web Store support page.