A practical checklist for sharing PDFs more privately

“Make it private” usually means several jobs

People ask for privacy when they mean different things: hide who authored the file, mark a draft so it is not treated as final, require a password to open, or avoid leaving the document on a random vendor’s servers for months.

Those are related, but they are not the same control. A watermark does not encrypt. A password does not remove author metadata. Auto-deletion on our side does not stop a recipient from forwarding a file they already opened.

Filemynt keeps these tools separate on purpose. Honest controls beat a single “privacy” button that overclaims. This guide is a checklist you can run in Studio on one upload when the risk warrants more than “attach and hope.”

Start by naming the threat you care about. Wrong recipient? Metadata leak? Draft treated as final? Interception in transit? Casual forwarding? Each threat maps to different controls — and some threats are mostly process, not PDF settings.

Step 1 — Clean document metadata

Office and design exports often embed author names, titles, and producer fields you never meant to share. Those fields can reveal internal usernames, software stacks, or draft titles that do not match the filename you carefully chose.

Strip Metadata clears common info fields. Privacy Pack combines strip and compress when you also want a smaller share copy. Metadata cleanup is hygiene. It does not redact text on the page, blur faces in images, or password-protect the file.

Run metadata cleanup on the version you will actually send — after you finish editing structure. Cleaning an early draft and then re-exporting from Word can put the fields right back.

Step 2 — Mark drafts and sensitive copies

Watermark text such as DRAFT, CONFIDENTIAL, or INTERNAL across every page. Recipients see the intent immediately. Accidental forwards still carry the stamp, which often prevents a draft from being treated as a signed final.

Choose wording that matches your culture. “DRAFT — NOT FOR DISTRIBUTION” is clearer than a cryptic project code. Place and opacity should keep the document readable; a watermark that hides the contract text has failed.

A watermark is a social and visual signal. Pair it with Protect when the content must not open without a password. Use watermark alone when the main risk is confusion about status, not interception.

Step 3 — Require a password when the risk warrants it

Protect PDF for contracts, offers, financial statements, and HR packs. Share the password through a different channel than the file itself when you can — a call, a separate messenger, or a password manager share your team already trusts.

Remember the limit: anyone who knows the password can still save and forward the unlocked contents. Passwords raise the bar; they do not replace judgment about who should receive the document. They also do not stop screenshots.

If you need an open copy later for merge or compress steps that reject locked files, Unlock with the password you already know. Filemynt does not crack forgotten passwords — and that is intentional.

Step 4 — Know retention on both sides

Filemynt deletes files within one hour. We cannot recover a document after that window. Keep your own archive of anything important before you close the tab.

Your recipient’s inbox, downloads folder, and backup tools have their own retention rules. Private sharing is a chain; every link matters. A password-protected PDF sitting forever in a shared team drive is a different risk profile than a short-lived email attachment.

Ask where the file will live after open. If the answer is “forwarded to four people and synced to personal phones,” watermarking and least-privilege distribution matter as much as encryption.

A suggested order in Studio

For many external sends: finish structure → strip or Privacy Pack → watermark if needed → protect → download → store your master. For internal drafts: watermark early so every intermediate share carries the draft mark, then protect only if the draft itself is sensitive.

Do not skip the human step: confirm the recipient list. The most expensive privacy failures are still “sent to the wrong person,” not missing metadata fields.

For a deeper look at what passwords actually guarantee, read Understanding PDF passwords. For workflow shape, see Upload once. Finish everything. Privacy questions: hello@filemynt.com.

Common mistakes that look like privacy

Encrypting a file and then posting the password in the same email thread is theater. Anyone who intercepts the message gets both pieces. Use a second channel for the password whenever the content is sensitive enough to protect in the first place.

Stripping metadata while leaving an old draft title on the first page is another false win. Readers see the page; metadata tools only clean fields. Read what you are sending, not only what the inspector reports.

Relying on Filemynt’s one-hour deletion as if it protected the recipient’s copy misunderstands retention. Our deletion ends our custody. It does not erase inboxes, downloads folders, or backups on the other side.

Finally, over-watermarking until the contract is unreadable helps nobody. A clear DRAFT stamp at readable opacity beats a wall of diagonal text that forces recipients to squint through legal language.

Build a team habit, not a one-off ritual

Privacy checklists fail when only one careful person on the team knows them. Write a short internal note: when we watermark, when we protect, when Privacy Pack is mandatory, and where masters live after send.

For recurring packet types — offers, invoices, diligence folders — save the order of operations. Studio makes consecutive tools easy; a shared habit makes sure people actually use them in the right order.

If something goes wrong, treat it as a process bug: wrong recipient, missing watermark, password in the same email. Fix the checklist. Tools amplify good habits; they do not invent them.

When you are ready to run the sequence, start in Studio with the final structured PDF, or open Privacy Pack, Strip Metadata, Watermark, and Protect as individual steps. Questions: hello@filemynt.com.