Controlled delivery
Content opens in a controlled viewer, never as a loose file you lose track of.
The problem it solves: A downloaded copy is one you can no longer reach.
Features
The controls that keep shared content yours.
Watermarking, expiry, device limits, access records and controlled delivery — set the policy once, and it's enforced every time the file is opened. Here's what each control does, and the problem it solves.
What each one does
Eight capabilities that keep content yours.
Recipient watermarking
Every view is stamped with the reader — name and email tied to the copy on screen.
The problem it solves: A leaked screenshot is anonymous, so no one is accountable.
Time-based access
Access expires on the date you set, or after a set number of opens.
The problem it solves: Training and licensed material stays open long after it should.
Device authorization
Cap how many devices a reader can use, and revoke any one of them.
The problem it solves: One shared login quietly becomes unlimited access.
Print & copy controls
Allow or block printing and copying per policy — the protected viewer enforces the rule when the document is opened.
The problem it solves: A file that can be freely printed or copied is a file that can be redistributed.
Offline-access policies
Give each policy a time-boxed offline window, so a document stays readable without a connection for as long as you allow.
The problem it solves: Offline access without a time limit is permanent access.
Access records
Every open is recorded — who, when, and on which device.
The problem it solves: Once a file is sent, you can't see who actually has it.
Send for signature
Send a document for signature with a secure link — recipients sign from their email, without creating an account or re-entering their address. Signed documents stay under the same controls.
The problem it solves: Chasing signatures over email scatters versions and identity across inboxes.
Try it: watermark a document to a reader
Set the reader and the policy — the preview updates the watermark and controls in real time.
DRM protected
Print blocked
Copy blocked
Up to 3 devices
Expires in 7 days
Watermarked to reader
Interactive illustration with sample content — not the production viewer. Watermark fields and placement are configured per deployment; the screenshots elsewhere on this page show the actual product interface.
Connect your systems
Run it standalone, or wire it into your stack.
Connect by API
Protect content and grant access straight from your own platform, which stays the source of record — the public REST API reference covers each endpoint. See which formats can be protected, and check plan allowances before you integrate.
Native to MyPass LMS
MyPass DRM is the native DRM layer for MyPass LMS, and connects to another LMS, an AMS, a portal or an ecommerce platform by API.
By consultation
Additional controls, available on request.
These are available on request and confirmed for your setup during solution design, rather than switched on by default. Ask us what applies to your content and platform.
User & group authorization
Branded recipient portal
Single sign-on (SSO)
Content fingerprinting
Protected video & audio
Features FAQ
Common questions about the controls.
MyPass DRM includes controlled delivery, recipient watermarking, time-based access (expiry and open limits), device authorization, print and copy controls, offline-access windows, access records, and send-for-signature. Each is set once as policy and enforced every time the content is opened.
You keep control of it. MyPass DRM opens content in a controlled viewer instead of releasing a loose file, so you can watermark each copy to its reader, expire access, limit devices, and revoke access after delivery.
No DRM stops a photo of a screen, and we do not claim to. MyPass DRM makes a leak traceable — every copy is watermarked to a person — and lets you expire and revoke access, rather than promising to prevent every capture.
Supported formats and viewers are confirmed for your content types during setup.
Yes. MyPass DRM runs standalone or connects to your platform by REST API, and it is the native DRM layer for MyPass LMS.
Yes. You can send a document for signature with a secure link; the recipient signs from their email without an account, and the signed document stays under the same controls.
See the controls on your own content.
Create a free account and apply watermarking, expiry, device limits and access records to your first document.