Screenshot protection

Block the capture. Trace the leak.

Block copy, save, and print shortcuts, wipe the clipboard on Print Screen, and burn the viewer's identity into every page so leaks trace back.

Brand refresh proposal

Page 3 of 4

ProtectedAAdham Alaa

4. Fees and payment

Adham's keyboard

CtrlAltPrtSc
  1. Adham reads the proposal, his name on every page
  2. He presses Print Screen
  3. The page frosts and the capture is blocked
  4. The attempt is logged
  5. He is back to reading
  6. Asim sees the attempt in Adham's session

Four ways every page defends itself

Keep scrolling. Each card settles on the last, the way each layer settles on the page.

01

Capture shortcuts blocked

Copy, Save, Print, and View Source shortcuts are blocked inside the viewer, so the casual keyboard grab stops working.

4. Fees and payment

CtrlCCopyBlocked
CtrlSSaveBlocked
CtrlPPrintBlocked
CtrlUView sourceBlocked
  1. The page is protected
  2. Copy is blocked
  3. Save is blocked
  4. Print is pressed, and blocked
  5. Nothing leaves by keyboard

02

Print Screen wiped

When Print Screen fires, we catch it and wipe the clipboard, so the grab comes back blank.

4. Fees and payment

PrtSc

Clipboard

Blank image

Screenshot logged · document is watermarked

  1. The page is on screen
  2. Print Screen is pressed
  3. The grab reaches the clipboard
  4. The clipboard comes back blank

03

Burned into every page

The reader's name and a live timestamp are stamped into the file itself on the server, so they survive screenshots, prints, and downloads.

Watermark

OffOverlayBurned in

4. Fees and payment

sealed

Brand refresh proposal.pdf

4. Fees and payment

  1. Overlay draws the mark in the viewer
  2. Burned in is picked
  3. The mark is stamped into the page
  4. The file carries it everywhere

04

Every attempt logged

A screenshot-attempt event lands in the audit trail the moment a real capture signal fires, with IP, region, and device hash.

A

Adham Alaa

adham.alaa@doc-shark.com · ID K4P9-2M7Q

  • Opened the document10:38
  • Verified email10:38
  • Read page 310:41
  • Attempted a screenshot10:42
  1. Adham's session is recorded
  2. A capture signal fires
  3. It lands in the trail
  4. The attempt is opened
  5. Where, on what, and when

Inside the shield

The page knows when it is being watched

Four quiet layers you can add to any protected link, each one a reason a capture comes back with nothing useful.

01

Reading spotlight

Only the pointer area is sharp

Read one line at a time.

With the reading spotlight on, only the area around the pointer is sharp. A screenshot catches a few lines, never the page.

02

Blur when away

Leaving the window, screen or app

Look away, and the page frosts.

The moment the reader leaves the window, switches apps, or reaches for a capture tool, the page blurs itself. It clears the instant they are back.

03

1m

Blur when idle

After a quiet minute

A quiet minute, and it pauses.

Leave a page untouched for a minute and it frosts over, so an open screen on an empty desk shows nothing.

04

Brand refresh proposalPrint

A blank sheet

Print it, and the sheet comes out blank.

Printing a protected page sends a blank sheet to the printer, so there is nothing to carry out of the room.

How it works

Arm it once. Every page defends itself.

  1. Arm the protection

    01

    Toggle screenshot protection on any share link, dataroom link, or signature envelope.

  2. The viewer opens the link

    02

    Their name and a live timestamp are burned into every page. The copy, save, and print shortcuts stop working in their browser.

  3. Attempts are traced

    03

    A Print Screen wipes the clipboard. Every capture attempt is recorded in the audit trail, and the burned watermark still names the reader.

Try it

Watch the page push back.

Toggle screenshot protection on, then try to print or copy. The shortcut is blocked, and the attempt is logged.

Capture shield

4. Fees and payment

Move your pointer across the page, then take it off the page.

Questions

Before you share something sensitive.

What if someone photographs the screen?

The photo carries the proof. Every page shows the viewer's identity and a timestamp, so a picture of the screen points straight back to the person who took it.

Does this work on mobile browsers?

Yes. The watermark rides on every page in any modern browser, on a phone or a desktop, and the page frosts the moment the viewer switches away.

Where do capture attempts show up?

In the audit trail for the link, dataroom, or envelope. For signatures, the attempt is added to the certificate of completion itself.

Still deciding, or have a question we did not answer? Talk to us

Ready for the next document.

Send it with control. Follow the read. Finish with the signature.

Free plan. No card required.