What to Ask Before Trusting a Service of Process Provider with Privileged Data
When a law firm or legal department hands off a matter to a process server, it isn't just assigning a task—it's sharing deeply sensitive information. Case strategy, witness identities, attorney work product, client contact details: all of it flows through the intake form, the instructions, and the confirmation emails.
For paralegals and legal administrators who manage process server relationships day to day, that transfer of data deserves the same scrutiny applied to any third-party vendor handling privileged material.
The problem is that vetting a service of process provider on data security rarely happens in a structured way. Price, turnaround time, and coverage area get evaluated. Data handling practices usually don't—until something goes wrong.
Here are the things every legal professional should know before trusting a process server company with their clients' information, including SOC II Type 2 compliance.
Does the Provider Have a Written Data Security Policy?
This is the baseline. Any reputable process server company should be able to produce a written policy that describes how client data is collected, stored, accessed, and destroyed. If the answer is "we haven't formalized that yet" or "we just use common sense," that's a meaningful signal.
Ask for the document. It may be part of their privacy policy published on their website. Read it. Look for specifics: data retention timelines, access controls, breach notification procedures. Vague language about "taking security seriously" is not a policy.
Read Proof’s commitment to integrity.
How Is Client Data Transmitted and Stored?
Service of process instructions often travel by email or web upload / download—each method carrying different levels of risk. The question to ask is: Do you have a reliable system in place to encrypt sensitive data?
Follow-up questions worth asking:
Is your client portal protected by two-factor authentication?
Are case documents stored on cloud infrastructure with SOC 2 compliance, or on local servers without formal oversight?
Do field servers (the individuals making attempts) have access to the full case file, or only what's necessary to complete service?
The principle of least privilege—limiting access to only the data each person needs—is a meaningful indicator of a mature security posture.
Who Has Access to Our Case Information, and Are They Vetted?
Process server companies often operate through networks of independent contractors. That's a normal business model, but it creates a question: when your confidential instructions reach a contractor in another city, what controls govern how they handle that information?
Ask whether the provider conducts background checks on its process servers. Ask whether contractors sign confidentiality agreements. Ask whether there's any training requirement around data handling.
A company that can answer these questions clearly is one that has thought through the risks. One that can't should raise concern—not because the individual servers are necessarily untrustworthy, but because the absence of controls means the company hasn't made security a priority.
What Happens to Our Data After an Assignment Is Completed?
Data that isn't needed anymore is data that can still be breached. Legal administrators should ask whether process server companies retain case files indefinitely, and if so, why.
A provider with sound practices will have a defined retention period tied to a legitimate business reason (dispute resolution, audit trails) and a documented destruction process when that period ends. Ask whether physical documents—affidavits, instructions, attempt logs—are shredded. Ask whether digital files are deleted or simply archived.
The absence of a clear retention and destruction policy is a liability for your firm and your clients.
The Right Legal Tech Vendor Answers These Questions Directly
Choosing a service of process provider is a business decision, but it’s also a security decision. The legal industry’s obligations around confidentiality don't pause when work is handed to a vendor. They extend through every partner in the chain.
Proof is built for legal professionals who understand that. Our platform is designed to handle privileged case information with the controls, transparency, and accountability that law firms and corporate legal departments require—because the integrity of your client relationships depends on it.
Have questions about Proof’s data security? Speak to a Proof specialist.
FAQ About What to Ask a Service of Process Provider: Data Security
Yes. Our data security practices are outlined in the privacy policy published on our website, covering how client data is collected, stored, accessed, and destroyed. Beyond our written policy, Proof's platform is SOC II Type 2 compliant. The certification provides independent assurance that its security controls are appropriately designed and are operating effectively. This includes ongoing security practices such as penetration testing, vulnerability management, access controls, and continuous monitoring.
Proof's full SOC 2 Type II report is a restricted-use document and is available to customers and prospective customers under NDA and upon request.
To request access, please contact your Proof sales representative or use our contact form to reach out.
Case information is transmitted and stored using encrypted, cloud-based infrastructure rather than local servers or unsecured email threads. Our client portal is protected by two-factor authentication, and we follow the principle of least privilege—field servers only see the information they need to complete service, not the full case file.
Proof takes privacy and data security very seriously. Your customer success specialist, your process server, and data and product teams handle customer and case data with great care, following internal best practices for data handling. Every independent process server in Proof's network goes through a rigorous vetting process before joining the platform, including background checks.
Proof retains sensitive and confidential data only for as long as necessary to fulfill its purposes, unless otherwise required by law or to meet legal and customer contractual obligations. To support compliance with these obligations, the Chief Technology Officer (CTO) or equivalent role reviews Proof's data retention practices on an annual basis.
Proof securely disposes of Sensitive and Confidential data following defined processes once it is no longer necessary for legal, regulatory, or business requirements or it has reached the end of its retention period.
The following methods are used for both hard copy and electronic data:
Purging and deleting data from all system components using a secure wipe program in accordance with industry-accepted standards for secure deletion (e.g., degaussing)
Destroying any cardholder data that is in a hard copy format (e.g., cross-shredding)
For electronic media stored on system components that are no longer in use, data is disposed of through one of the following methods:
Disintegration
Shredding by a disk grinding device
Incineration by a licensed incinerator
Pulverization
Instances of customer data disposal are tracked via a ticketing system to document the steps taken to complete the removal.
Confidentiality obligations don't end when a matter is handed off to a vendor—they extend through every partner in the chain. Choosing a provider with strong data security practices protects privileged case information, client relationships, and your firm's own obligations to safeguard sensitive material.


