Real estate agents, mortgage brokers and insurance brokers have something in common with accountants: they spend their days moving other people's most sensitive paperwork from one inbox to another. A closing packet can hold a driver's license scan, bank statements, pay stubs and a signed purchase agreement. A policy document can list beneficiaries, dates of birth and premium details. Most of it travels as plain email attachments. This article walks through a practical way to protect those files, one client at a time or a hundred at once, without uploading them to a website first.
What's actually in the files you send
It helps to look at a typical week's outbox with fresh eyes.
- Real estate: listing agreements, disclosure packets, offers and counteroffers, closing statements, copies of IDs collected for verification, proof-of-funds letters.
- Mortgage brokerage: loan applications, pay stubs, tax returns, bank statements, credit authorizations, pre-approval letters, closing disclosures.
- Insurance: quotes, policy schedules, renewal notices, endorsements, certificates of insurance, claim files with photos and medical or repair reports.
Any one of these files is enough to start an identity theft. Put several together in a single packet, and it's a complete profile of a household. Yet the usual way to send them is the same as for a lunch invitation: attach and click send.
Why "just email it" is riskier than it looks
Email wasn't designed as a vault. A message sits in your sent folder, in the client's inbox, possibly in their spouse's inbox if they share an account, and on every phone where either mailbox is set up. If any of those is compromised months later, the attachments are still there, readable. Real estate transactions in particular attract scammers who watch inboxes for closing dates and wiring instructions.
A password on the PDF itself doesn't fix everything, but it changes what a leaked email exposes. Without the password, the attachment is an encrypted file that shows nothing. That's a meaningful difference for documents that will sit in mailboxes for years.
One fixed password per client
The most workable setup for a brokerage or agency is to give each client one strong password at the start of the relationship and keep it for every document you send them. A buyer working with you over a three-month transaction, or a policyholder who renews every year, learns it once.
Practically, that means a short conversation at onboarding ("all documents from us will be protected; your password is this, we'll text it to you now") and a line in your client list. Make each password at least 12 characters. A few unrelated words with a separator and a number, like Cedar-Lantern-Pier-64, are easy to read over the phone and hard to guess.
Single files: a closing packet for one buyer
For a one-off packet, the simplest path is to assemble the documents into one PDF in the order the client will read them, then protect that file. PDF Protect Plus does both on your computer: merging and reordering pages, then encrypting the result with AES-256. The protected copy is saved as a new file; the original stays as it was. Our guide on password-protecting a PDF covers the single-file steps, and merging PDFs without uploading them covers the assembly.
Batches: renewals, annual notices, pre-approval letters
The real time sink is volume. Take an insurance agency sending renewal documents to around 150 policyholders at the start of the month, each file named after the client. Or a mortgage broker sending updated pre-approval letters to a few dozen active buyers after a rate change. Protecting each file by hand, with the right password every time, is where mistakes creep in.
The Batch protection tab is built for that. It has three steps: Add the PDFs, Import the password spreadsheet and Check, then protect.
- Add the PDFs. Drag the files in, up to 200 per batch. Files that are already protected are set aside.
- Choose "My clients' passwords" and import your spreadsheet. It's a CSV with a
clientcolumn and apasswordcolumn, plus an optionalfilecolumn. Semicolons, commas or tabs all work, as do UTF-8 and Windows-1252 encodings and English or French headers. The Download the template button gives you a blank one. You can also drop the CSV in with the PDFs and the app switches to client mode by itself. - Check the table. Each file is matched to a client: an exact name in the
filecolumn wins; otherwise the client's full name must appear in the file name, ignoring capitals, accents and punctuation. Rows that need you turn orange: To confirm for a partial match (two clients named Garcia, say), Client not found when nothing matches, Too weak when a password is under 12 characters, with a Generate button to replace it. You pick the right client from a list. - Protect. Choose a destination folder. The protected copies go into a new subfolder, named
001_…_protected.pdf,002_…and so on. The batch is all-or-nothing, and your originals are not touched. A window confirms how many files were protected and offers Open the folder.
Two options are worth ticking. Save these passwords in the vault keeps one entry per client in the app's encrypted local vault, so next month you won't need the spreadsheet at all. Create the sending summary (client, file) writes a recapitulatif-envoi.csv file listing which file goes to which client, with no passwords in it. It doubles as a checklist while you send the emails.
If you don't keep per-client passwords, there are two other modes: The same password for all, and A generated password per file, which creates a random 20-character password for each file and saves them in a plain-text batch_passwords.txt file. Keep that file somewhere safe and never attach it to an email.
Documents clients send back protected
Traffic goes both ways. Buyers forward bank statements; policyholders send back signed forms; and some of those arrive password-protected. When you know the passwords, the Unlock a batch tab removes the protection from a whole set at once, using your client spreadsheet or the vault. Each password is tested before anything is written, a wrong one shows ✕ Password refused, and the batch is only created if every password is correct. It doesn't crack passwords: it's for files you're entitled to open. The article on protecting and unlocking PDFs in bulk goes into more detail.
Black out what the recipient doesn't need
Sometimes the issue isn't who can open the file but what's in it. A lender may need a bank statement but not the full account number; a co-broker may need a page of an ID but not the date of birth. Drawing a black box in an ordinary editor often leaves the text underneath intact and copyable. Our guide on redacting a PDF properly explains why, and how to do it so the information is really gone.
Send the password by a different route
A protected PDF and its password in the same email protect nothing. Email the file; text the password, or give it once by phone at onboarding. Since each client keeps the same password, you only do this once per client. Our guide to sending a PDF password separately includes email and SMS templates you can adapt.
Nothing leaves your computer
All of this, from reading the spreadsheet to encrypting the files, happens on your own machine. Your PDFs and your password list are never sent to our servers. Your account and license need an internet connection; the documents don't. That matters when the documents are other people's IDs and bank records. The batch protection tutorial shows each screen in order, and you can download the app to try it on a test folder during the trial.