Process server plugin privacy

The request form that names the person being sued before they are served

Process-server sites on WordPress can collect a full locate package in one intake form — the defendant's name, home address, workplace, photo, daily routine, and a court case number — through general-purpose form, upload, and marketing-tag plugins. The person filling the form is the customer. The person named in the fields never consented and may not know the form exists. It lands in a WordPress contact-form database because that is how small process-serving shops take jobs. A remarketing pixel on that request page can fire before consent and treat legal-service intent as an audience segment. This sample reviews three plugins' documentation. Check which defendant and case fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, photos, case PDFs, and backups are kept after the job ends.

Documentation review only. This is not legal advice, not a service-of-process or court-procedure guide, not a service-validity or court-outcome claim, and not a GDPR or other compliance assessment.

Scan your process-server intake page for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded photos, case PDFs, email inboxes, staff permissions, vendor accounts, or backups.

Where defendant details, case numbers, and request-page tags are stored

Files and form entries handled on your WordPress site

Check which defendant-name, home-address, workplace, daily-routine, case-number, photo-upload, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, photos, case PDFs, and backups are kept after the job ends. Notification emails can also copy intake answers off-site. A defendant address next to a court case number in the contact-form database names someone who never consented — before they are served.

Marketing tags on the process-server request page

Some tools load a marketing pixel or tag on the same page as the process-server intake form. A page request can fire before anyone submits a defendant address — and can treat legal-service intent as an audience segment. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded photos.

Process server intake setups

No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.

Three plugins reviewed from public documentation. Specialty process-server SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Drag and Drop Multiple File Upload for Contact Form 7

Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which defendant photos, case PDFs, skip-trace notes, or other intake files you accept depends on the fields you add; they are not fixed process-server defaults. Filenames chosen by visitors can include full legal names or case-number fragments. An uploaded photo is not a served document. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified.

Uploaded files attached to email; temporary copies under wp-content/uploadsBrowser hosts not verifiedNot assessedNot tested
  • None
Formidable Forms

Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. Defendant name, home address, workplace, daily-routine, case-number, or photo fields depend on the fields you add — they are not fixed process-server defaults. An intake form that stores a defendant address next to a court case number names the person being sued before they are served, and that person never consented. An intake entry is not a served document or a court record. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the job ends is not specified as a default purge. Public form browser hosts are unverified.

Process-server intake form entries stored in your WordPress databaseBrowser hosts not verifiedNot assessedNot tested
  • None
PixelYourSite – Your smart PIXEL (TAG) & API Manager

Documented pixel and tag manager (plugin version 11.4.2.1). When a Meta Pixel ID is saved, version 11.4.2.1 dist/scripts/public.js loads https://connect.facebook.net/en_US/fbevents.js. A noscript image uses https://www.facebook.com/tr. Google Analytics 4, Google Tag Manager, OpenAI Pixel, and Head and Footer scripts load only when you enable them. Automated events include form submissions; those events do not by themselves prove that a defendant address was sent. A page request from this script on a process-server request page is not proof that an address or case number was collected — and a pre-consent tag on that page can still treat legal-service intent as an audience segment. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on intake and document-upload pages.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Defendant-detail, case-number, photo-upload, or surveillance-adjacent fields often depend on the fields you configure. An intake entry is not a served document, not a court record, and not proof of valid service. A marketing-tag page request is not proof an address or case number was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess service of process, court procedure, legal advice, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether post-job intake rows purge, whether portal links expire, whether marketing pixels stay off intake pages, whether defendant photos and case numbers stay off the first contact form, and whether “secure intake” badges match the storage path you can verify. Review stored records, uploaded files, connected services, exports, notification emails, and backups.

Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.

Related pages

Scan your process-server intake page for third-party requests

/wp-process-server-plugin-privacy