Screen recording protection

Watch protected video in Ajar and keep it out of screen recordings

Ajar is a full web browser for everyday use. Open a DynTube-protected video in Ajar and it gets screen recording protection while it plays. Turn on Ajar-only playback for your account and your videos stop playing in Chrome, Safari and Firefox altogether.

Start free trialTalk to us
members.yourbrand.com/watch/module-2

Playback refused. The account allows only Ajar and approved apps, so the server sends no playable stream to this browser.

One members video, three different clients asking to play it

Illustration of designed behaviour, not a live test. Ajar is not yet publicly released.

  • Screen recording protection

    For DynTube-protected video in Ajar

  • Ajar-only playback

    A per-account setting

  • SDK for your apps

    Android, iOS and macOS

The basics

What does Ajar add to your DynTube videos?

Ajar is a complete web browser that people use for everything they do online. When it plays a video protected by DynTube, it keeps that video out of screen recordings and screenshots on supported devices, hides and pauses it when a recording starts, and proves to DynTube that the request really comes from a genuine Ajar installation.

That last part is what an ordinary browser cannot do. Chrome, Safari and Firefox will play any stream they are handed, so a copied embed code or link plays anywhere. When an account turns on Ajar-only playback, DynTube’s servers ask each playback request to prove which client sent it, and refuse the ones that cannot.

Everything else in Ajar works as people expect. The protection applies only to DynTube-protected video, so email, documents and every other website open normally.

The mechanism

How does Ajar-only playback decide who can watch?

The decision is made on DynTube’s servers and at the edge, never inside the player, so there is no script to switch off.

Each installation holds its own keyIdentity
On install, Ajar creates a device key and keeps the private half in the operating system’s secure storage. Official installations are admitted automatically; you do not approve viewers one by one.
Every playback request is signedProof
Requests for protected playback carry a short-lived proof made with that key and bound to the exact address being requested. A link copied out of the browser carries no valid proof, so it does not play elsewhere.
Refused before any video is sentEnforcement
With the setting on, a request without a valid proof gets no playable stream: embeds, private links, direct links, recorded video and live streams alike. Your viewer sign-in, domain and country rules still apply on top.
Revocation you controlControl
Revoke an installation from the dashboard and later playback from it is refused. A revoked installation is not quietly re-admitted. Changes reach the edge within a short, bounded cache window rather than instantly.

What the server checks, per request

  • The account’s playback setting and its current revision
  • A proof signed by an admitted installation key
  • The proof matches this exact request and is fresh
  • The installation has not been revoked
  • Your usual sign-in, domain and country rules

For your own apps

Can your own app play protected video too?

Yes. The DynTube protection SDK adds the same capture safeguards and request signing to apps you build, so Ajar-only accounts can still reach your app’s viewers.

  • Keeps your player

    The SDK adapts the native player your app already uses on Android, iOS and macOS. It does not replace it with a new one.

  • Embeds in a web view

    Apps that show DynTube embeds or private links in a web view are admitted through the SDK, while a plain web view without it is refused like an ordinary browser.

  • Registered, not assumed

    An app is admitted only after it is registered with DynTube. Mobile registrations can be backed by the platform’s own app-integrity checks.

Accepted limits

Where does Ajar-only playback stop?

These limits are part of the design, published so you can decide with them in view.

  • A camera pointed at a screen

    No software protection reaches a second device. A viewer watermark makes that copy traceable instead.

  • A compromised approved client

    An installation or app that has been modified after it was admitted can record what it plays.

  • Desktop identity is software-based

    Windows, macOS and Linux installations have no hardware attestation, so a skilled attacker can imitate one. Revocation is the remedy.

  • Revocation takes minutes, not milliseconds

    Caches bound how quickly a revoked installation or a new setting reaches every edge server.

The workflow

How do you move your audience to Ajar?

Plan it like any change your viewers will notice: test first, announce, then switch.

  1. 01

    Confirm entitlement

    Ajar-only playback is arranged per account rather than switched on by a plan tier. Talk to us and confirm entitlement before you set a date.

  2. 02

    Test with a small group

    Have a few viewers install the browser and watch a protected video on each platform your audience uses.

  3. 03

    Tell your viewers

    Explain why, and where to get the browser. Ordinary browsers will be refused once the setting is on, so give people time.

  4. 04

    Switch it on and watch the installations

    Turn on the setting, then use the installation list to see who is watching from where, and revoke anything you do not recognise.

Questions

Questions about watching in Ajar

Direct answers, each within what the product commits to.

Where can viewers get Ajar?

Ajar is not available for download yet. It is built for Windows, macOS, Linux, Android and iOS. Talk to us if you want to plan a rollout, and we will tell you when your viewers can get it.

What happens to viewers using Chrome, Safari or Firefox?

If your account has Ajar-only playback switched on, ordinary browsers are refused and the viewer sees an error instead of the video. If the setting is off, nothing changes: your videos play in any browser, and viewers using Ajar still get its capture safeguards.

Do links shared before the switch keep working?

No. Once the setting is on, links issued earlier stop playing in ordinary browsers after a short cache window. Plan the announcement before you switch, because viewers with old bookmarks will need Ajar.

Do I have to approve every viewer’s installation?

No. Ajar installations are admitted automatically. You can see installations and revoke one from the dashboard, and a revoked installation is not re-admitted on its own. Reinstalling creates a new installation, so revocation stops a key, not a person.

Does it cover live streams?

Yes. The setting applies to recorded video and to live streams on both of DynTube’s live systems. Viewer sign-in and your other access rules apply as they do today.

Can someone still copy a protected video?

Protection reduces unauthorised use and raises the effort of copying; it does not make copying impossible. A camera pointed at a screen, or an approved client that has been modified, can still capture what it plays. Pair the browser with a viewer watermark so any copy that is made can be traced.

Decide who gets to press play

Start a trial to set up your library, watermarking and encrypted delivery, and talk to us about Ajar-only playback for your account.

Start free trialTalk to us