The first post in this series answered the ethics question in general. This one answers its sharpest edge — the one a careful attorney feels before sending the first file: I'm about to put my client's medical records, litigation strategy, and case file in the hands of a contractor I've never met, who also works for other lawyers. How does that not become a problem?
The question deserves a specific answer, not reassurance. So here's exactly how confidentiality and conflicts work in my practice — the obligations, the conflicts system, and the security mechanics. Partly because you should know, and partly because how thoroughly a contract paralegal can answer this question is itself the credential. Vague answers here are disqualifying, and they should be.
The obligation: where my duty comes from
A common misconception is that confidentiality belongs only to lawyers, and a nonlawyer contractor floats outside it. The actual structure is tighter: your ethical duties extend through everyone who assists you — your obligation includes ensuring nonlawyer assistants handle client information consistently with your own duties. That's the supervision framework from the first post, applied to information.
On my side, the duty is layered three deep. Professionally: paralegal ethics codes (NALA, NFPA) impose confidentiality obligations directly on paralegals, and fifteen-plus years in litigation makes confidentiality reflexive rather than aspirational — it's the water the work swims in. Contractually: my engagement terms include confidentiality provisions, so the duty is enforceable, not just professional. Practically: a freelance paralegal's entire livelihood is attorney trust. A single loose-lips incident doesn't cost a client; it costs the practice. The incentive structure could not point harder in one direction.
What this means concretely: your case information is used for your engagement, period. Not in marketing (every example on this blog is fictional — house rule), not in conversation, not as war stories for other clients.
Conflicts: the system, since the question is really about systems
A freelance paralegal serving multiple attorneys raises a real structural question: what happens when two clients' matters touch? The answer can't be "I'd remember." It has to be a system.
Mine works like the conflicts checks you already run, scaled to a support practice. A conflicts log: every engagement records the parties, adverse parties, and matter — checked before any new engagement is accepted. The check happens before the file does: at intake I ask for party names first, run them against the log, and only then accept the matter and receive documents — so a conflict surfaces before any confidential information moves. A hit means disclosure and declination: if a new matter is adverse to a current or former engagement's parties, I flag it to both sides' attorneys and decline. No judgment calls in the gray — the gray is declined too, because no single engagement is worth the system's credibility. Side-switching is permanent: I don't work both sides of the same matter, ever, in any sequence.
Worth saying plainly: in practice, conflicts are rare — my clients are plaintiff-side PI attorneys spread across jurisdictions, and their adversaries are mostly insurers and defense firms I'll never work for. But "rare" isn't the answer to a conflicts question. The log is.
Security: the unglamorous mechanics
Remote work means files in transit and files at rest, and both have rules. In transit: encrypted transfer — secure links or encrypted email, never open attachments of sensitive material; my contact infrastructure runs on the same principle (this site's forms are spam-filtered and route to an encrypted inbox). At rest: case files live in access-controlled, encrypted storage, organized per engagement — not scattered across a desktop. At the end: when an engagement closes, files are returned or destroyed per your instruction, and I don't retain client records beyond what the engagement and my records obligations require. In writing: all of it documented in the engagement terms, so your file reflects that your duty of supervision over information handling was met — by documentation, not assumption.
None of this is exotic. That's rather the point: confidentiality at the support level isn't heroics, it's hygiene — the same boring, consistent mechanics your own office runs, extended through the engagement.
The remote paradox, one more time
Here's the reframe worth leaving with. Attorneys instinctively feel that remote support is less controllable than someone down the hall. Information-wise, it's usually the opposite. Remote work is structured work: defined files transferred through defined channels, written instructions, written questions, logged engagements, documented handling. The casual leak vector — the file left open, the hallway conversation, the assistant who hears everything about every case — barely exists. When everything moves in writing, everything is accountable in writing.
The answer should sound like a system. If it sounds like a promise, keep looking.The test to run on any contract paralegal — me included
So ask the sharp question of any contract paralegal you consider — me included.
Questions attorneys ask
Are freelance paralegals bound by confidentiality?
Yes, three layers deep: professional ethics codes (NALA, NFPA) bind paralegals directly, engagement terms make the duty contractually enforceable, and the attorney's own supervision duty extends through every assistant.
How does a contract paralegal check for conflicts?
With a logged system, not memory: every engagement's parties and adverse parties are recorded; new matters are checked against the log at intake, before any documents move; hits — and gray areas — are disclosed and declined.
How are case files transferred securely to a remote paralegal?
Encrypted transfer in transit (secure links or encrypted email — never open attachments), access-controlled encrypted storage at rest, organized per engagement.
What happens to case files when an engagement ends?
Returned or destroyed per the attorney's instruction, with nothing retained beyond what the engagement and records obligations require — and the handling documented in the engagement terms.
Ask about my conflicts and confidentiality process
The full intake order, the log, the security mechanics — happy to walk any attorney through the system before a single document moves.
Contact →Educational content for legal professionals — not legal advice. Rules vary by jurisdiction.