Skip to content
StreamSec

Forensic watermarking for on-demand video

Every stream is marked. Every leak is traceable.

StreamSec delivers your videos with an invisible watermark that's unique to every viewer. If a copy leaks, upload it and we'll tell you which viewer it came from.

We'll only email you about StreamSec's launch. See our privacy policy.

Example leak trace: three viewers each receive a different A/B watermark sequence. One records their screen, and StreamSec reads the sequence from the leaked copy and matches it to viewer usr_7Hq2Lm9 with 99.7% confidence.

The problem

Protection stops at the screen

Paid courses, internal all-hands and pre-release screeners all leak the same way: someone presses record.

  • DRM blocks downloads, not recordings

    Encryption stops ripping tools. A screen recorder, or a phone pointed at the monitor, still gets a clean copy.

  • Visible watermarks get cropped

    A name in the corner deters casual sharing, but it can be cropped, blurred or covered in seconds.

  • Without a name, leaks repeat

    If you can't tell who leaked a video, nobody faces a consequence, so it happens again.

How it works

One video, a different fingerprint for every viewer

StreamSec uses A/B forensic watermarking, the technique studios use to protect pre-release films, delivered as an API.

  1. 1

    Deliver

    Upload your video. When a viewer presses play, your backend asks our API for a playback token tied to their user ID, and your site embeds our player with it.

  2. 2

    Mark

    Every video is prepared in two invisibly different versions, A and B. Each playback session receives its own sequence of A and B segments, so no two viewers get the same stream.

  3. 3

    Trace

    Found a leaked copy? Upload it to the dashboard. We read the sequence back, match it to the playback session and give you the viewer ID, with an evidence report.

usr_7Hq2Lm9
usr_K2p9Xw1
usr_Q8v3Nd5
The same video, streamed to three viewers. Each gets its own sequence of A and B segments.

Leak tracing

From a leaked file to a viewer ID

Every trace ends in an evidence report you can hand to HR or legal.

The trace result

Viewer ID
The ID your platform gave the viewer, so you know exactly which account it was.
Playback session
Which video was streamed, and when the session started.
Confidence
How certain the match is. A weak match is never presented as certain.

The evidence report

  • A hash of the leaked file you submitted
  • The extraction method and its version
  • The matched playback session and viewer ID
  • The confidence level and timestamps

Features

Access control, watermarking and tracing in one API

  • Access control

    Short-lived playback tokens for one viewer and one video, with expiry and allowed domains.
  • Forensic A/B watermarking

    An invisible mark that's unique to every playback session. Quality stays the same.
  • Leak tracing

    Upload a leaked file or link in the dashboard and get the viewer it came from.
  • Evidence reports

    A downloadable record of every trace: file hash, method, result and confidence.
  • Embed and API

    Embed our player in your site or app. Everything the dashboard does, the API does too.
  • DRM

    Widevine, FairPlay and PlayReady on top of watermarking, to block download tools as well.
    Coming soon

Use cases

For video that can't afford to leak

  • Course creators and edtech

    Find the student who recorded and resold your course, and revoke their access.
  • Enterprise internal video

    Know which employee leaked the all-hands, with evidence HR and legal can act on.
  • Media and entertainment

    Trace a leaked screener or pre-release cut back to the recipient whose stream it came from.

FAQ

Questions, answered plainly

Early access

Find out who leaked it

StreamSec is in development. Join the waitlist and we'll email you when it opens.

We'll only email you about StreamSec's launch. See our privacy policy.