Employment lawyer plugin privacy
That complaint about your boss — filed while the badge still works — who else can read it?
Employment-law firms on WordPress can collect a case-intake form that pairs a still-employed visitor with the employer's name, the names of people involved, and a narrative of harassment, discrimination, retaliation, or unpaid wages — through general-purpose form, upload, and marketing-tag plugins. Retained entries and public uploads can keep that accuser + accused pairing after the visitor expected confidentiality. This sample reviews three plugins' documentation. Check which employer and evidence fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, files, and backups are kept after the matter closes.
Documentation review only. This is not legal advice, not an attorney-client communication, and not a legal-practice, privilege, GDPR, or other compliance assessment.
Scan your employment-law intake page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded HR complaints or pay stubs, email inboxes, staff permissions, vendor accounts, or backups.
Where employer names and evidence uploads are stored
Files and form entries handled on your WordPress site
Check which employer-name, manager-name, narrative, HR-complaint, pay-stub, recording, 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, files, and backups are kept after a matter closes. Notification emails can also copy identity and case answers off-site. The pairing — "this employer, this manager, this allegation" — can leak before a claim is filed, which is exactly the adversarial timing visitors fear most.
Marketing tags on the case-intake page
Some tools load a marketing pixel or tag on the same page as the case-intake form. A page request can fire before anyone submits an employer name or evidence file — and can treat "considering suing employer" 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 HR complaints.
Employment-lawyer case-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 legal-intake SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 HR complaints, pay stubs, recordings, or other evidence files you accept depends on the fields you add; they are not fixed employment-firm defaults. Pro documents Media Library storage, custom upload directories, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Employer-name answers, manager or coworker name fields, free-text narratives about harassment, discrimination, retaliation, or unpaid wages, still-employed answers, or contact fields depend on the fields you add — they are not fixed employment-firm defaults. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after the matter closes is not specified as a default purge. Public form browser hosts are unverified. | Case-intake form entries stored in your WordPress database | Browser hosts not verified | Not assessed | Not tested |
| |
| 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 an HR complaint or employer narrative was sent. A page request from this script on a case-intake page is not proof that a named employer was collected — and a pre-consent tag on that page can still treat "considering suing employer" 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 case-intake and consultation pages. | Marketing tags handled through Meta, Google, or other configured platforms | connect.facebook.net | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Employer names, manager names, narratives, or evidence uploads often depend on the fields you configure. A case-intake form is not legal advice and is not an attorney-client communication. A marketing-tag page request is not proof a named employer was collected. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess legal-practice, privilege, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether evidence files stay off the public web, whether employer name is a structured field rather than free-text narrative, whether rows purge on matter close, and whether "confidential consultation" claims 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
- WordPress immigration plugin privacy
- Legal intake compliance
- WordPress file-upload plugin privacy
- All privacy guides
/wp-employment-lawyer-plugin-privacy