Secure Sessions
Board reviews, legal and M&A calls, product designs, question papers, paid courses. A secure meeting or a Secure class is app-only: every participant joins from an attested app, every view carries that person's invisible mark, and screen capture is blocked wherever the operating system lets us block it.
A secure meeting: the notice, the secure badge, external displays blacked out, the drifting visible name — and the invisible mark underneath.
Android 8 or later, iPhone and iPad with iOS 16 or later, and Macs with Apple silicon on macOS 27 or later; no browser join. The platform verifies the app before it hands out the session key, and Supermeet can require an app update before anyone joins.
Android blocks screenshots and screen recording. iPhone and iPad cannot, so the app blacks the session out and mutes it when recording or mirroring starts. Current macOS lets screen recorders capture a window, so on the Mac the mark does the work. A second display, casting or AirPlay blacks the session out.
Hosts included: each participant's screen carries a personal mark, so a leaked recording resolves to one account, not "someone in the meeting".
Host, presenter and attendee roles are minted into the join token by your console or your backend — never decided on the device.
A secure class's replay plays only in the app, with the viewer's own mark, and is erased when your retention policy says.
Secure meetings hold up to 100 participants; larger audiences run as Secure live classes, which carry the same protections on the broadcast path.