How watermarking works
Nothing leaves CoverQueue unstamped. Every script and coverage PDF that reaches someone (a download, an in-app view, a share-link open) is watermarked, so a leaked file always points back to who received it.
Stamped per recipient, at delivery
Watermarking happens server-side, per recipient, at the moment of delivery. Each page carries who received it, which org sent it, and when. Because it's applied when a specific person needs the file, two people downloading the same script get two differently stamped copies.
Every page footer:
Jane Smith / Acme · Meridian Pictures · 2026-07-14 10:22
You choose the style in Settings → Organization: footer-only, or footer plus a diagonal watermark across the page.
One clean original, never served
CoverQueue keeps exactly one clean original per submission, and never serves it directly. Watermarked copies are derived artifacts: generated when needed and cached, never the source of truth. The cache is always safe to purge; the worst case is a re-stamp.
For share links, the included items are pre-stamped in the background when the link is created, so the recipient's first click is instant even for a large script.
Tied to the audit trail
Watermarking and the access log work together: the stamp identifies the copy, and the log records every open and download. Together they mean a Friday hand-off never becomes an untracked leak.
Revoking a share link deletes that link's cached watermarked copies immediately, and replacing a submission's file orphans all prior stamped copies (swept automatically).
Common questions
Is watermarking on every plan? Yes. Watermarked downloads are included on Free, Solo, and Team.
Does it slow downloads down? Not perceptibly: direct downloads stamp on the fly, and share-link items are pre-stamped ahead of the first click.
Can I turn it off? No. Confidentiality is the point; you choose the style, not whether it's applied.