Safe external sharing checklist
Goal
Send a PDF outside your organisation without leaking more than you intended: hidden pages, author names, attachments, history, or open access.
You are sending a proposal to a prospect. It has a draft appendix you forgot to remove, the author field shows an ex-colleague's name, and an Excel file is embedded in the PDF. You want a clean copy and a lock.
What this does not cover
No Documentize app redacts text inside a page (PDF Redactor is not available). Pages can be removed; words on a page you keep stay in the file. If that is your situation, use an outside tool that deletes the text, then follow this checklist. Never believe a black box.
Starting state
- A PDF that opens, not password-protected. Keep the original; send only the new copy.
Chain
Extract Metadata (inspect) → Delete Page → Recovery (sanitize) → verify (Extract Metadata, Search, Parser) → Protector
what is in there? drop pages strip hidden data does it hold up? lock
Step by step
1. Extract Metadata (inspect)
Upload the file and press Extract. Read the author, title, subject, keywords, producer and Custom: entries. Note what you do not want out. The app only reads; it cannot change them. See Extract Metadata.
2. Delete Page
Type the pages to remove (for example 12-14). This is real removal. See Delete Page. Rebuild the table of contents with Add TOC if the old one is now wrong.
3. Recovery with sanitization
Upload the result (one file per run). Choose a Sanitization policy:
- Full (default): history, metadata, attachments, active content, hidden content.
- Public release: Full plus image EXIF metadata. Best choice for external sharing.
- Court filing: strict; the run fails if anything is still detected.
- Internal share keeps annotations, so avoid it here.
Leave Expected page count at the real count if you want a safety net. Download repaired.pdf and read the report: it names what was removed and what it could not prove gone. Do not rely on it for legal use without reading that section. See Recovery.
4. Verify
Check the file, not your memory.
- Extract Metadata: author and keywords gone or acceptable.
- Search for a few sensitive words: no results.
- Parser: the ZIP should have no unexpected attachments, annotations or bookmark titles.
5. Protector
Strong password, Full Document Lock, press Protect. Send the password through another channel. See Protector.
Why this order
Look first so you know what to remove. Remove content (pages) before sanitising, so the cleaner sees the final content. Verify while the file is still unencrypted, because the checking apps cannot read a locked file. Lock last, since Recovery refuses an encrypted file.
Expected result
A clean copy with only the intended pages, no leftover metadata or attachments, opened by a password.
Check it worked
- Page count is original minus removed pages.
- Re-run of Extract Metadata and Parser shows nothing you did not intend.
- Search finds no sensitive words.
- The password prompt appears in your viewer.
- The original is stored separately, and the filename says "external".
Variations
- Need a signature too: sign instead of locking (Sign), as a signed file is readable by anyone. The two do not combine well (see combos).
- Files with form answers: Flatten before Recovery.
- Only some pages to share: Share only part of a document.
- Smaller: Compressor after Recovery, before Protector.
What can go wrong
- Recovery's default Full removes attachments you meant to keep; choose another policy.
- If the cleaner cannot run, you get the repaired file unsanitized and no certificate: check the report.
- The password in the same email.
- Visible secrets on kept pages remain.
- Protector restricts opening only, not printing or copying.