Workers' comp attorney plugin privacy

Where does the intake that names your employer while you still work there go?

A workers'-comp firm's WordPress intake often holds injury description, employer name, date of injury, whether you reported it, and an insurance carrier — filled out while the applicant is still on payroll, before any claim exists. That interval is the retaliation window, and the row documents it: free-text "how did it happen" assigns blame in writing to a company that still signs the paycheck. The most dangerous reader is the current employer during the gap between consult and filing. Those answers sit in a local-first booking or form plugin behind one admin login. A marketing tag on the same intake page can send a page request to a vendor host before anyone submits — and that page request alone can treat workplace-injury consult intent as an audience segment from the URL. A page request is not proof anyone was injured. A consultation request is not a filed claim. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the intake page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a workers-comp-statute claim, a retaliation-law claim, a benefit-eligibility claim, or a GDPR or other compliance assessment.

Scan your site for third-party requests

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

Where intake answers, visitor fields, and page tags go

Entries and bookings handled on your WordPress site

Check which name, phone, employer name, injury description, injury date, report-status, or insurance-carrier fields you enable, who can open form entries and consult bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a consult that was completed, abandoned, or never filed as a claim. Notification emails can also copy the same visitor identity and employer-injury answers off-site — including while the visitor is still on that employer's payroll. Ask your web vendor not to store an employer name next to free-text "how did it happen" in one open submissions list when a short matter ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the workers'-comp intake page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and consult-booking pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential consultation" badge is not a verified storage path.

Workers'-comp intake, consult booking, and marketing-tag 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. Case-management platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

Documented self-hosted appointment plugin marketed for service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A workers-comp consult is a booking you create; a service name such as injury consult or claim intake slot is a label you configure. Neither is a documented default. Name, phone, employer name, injury description, injury date, report-status, or insurance-carrier questions are custom fields you add (textarea, select, or input); they are not documented defaults. A submitted consult booking is not a filed claim. Cancelling or abandoning a consult later does not erase the employer and injury answers already stored next to a name — including while the visitor is still on that employer's payroll. Emails can include those custom fields. An optional GDPR setting can auto-remove customer data older than six months; that is not a default purge. Google Calendar, SMS, and payments are Pro. Google reCAPTCHA is optional. Public booking-form browser hosts are unverified.

Consult bookings and custom intake fields stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Forminator Forms – Contact Form, Payment Form & Custom Form Builder

Documented self-hosted form builder (plugin version 1.58.1). The listing states Forminator stores and organizes submissions so you can sort, analyze, and manage responses, and includes a free file-upload field with multi-file support. Version 1.58.1 helper-fields.php forminator_upload_root() writes under the WordPress uploads directory plus /forminator/, with per-form hashed subfolders from forminator_get_upload_path(). upload.php stores files through that path. Name, phone, employer name, injury description, injury date, report-status, or insurance-carrier questions are fields you add; they are not documented defaults. Incident photos, medical notes, or wage stubs are files you accept; they are not documented defaults. One intake entry can store an employer name next to free-text "how did it happen" while the applicant is still on that payroll and before any claim exists. A submitted form is not a filed claim. Filed or not, the row can stay. Notification emails can copy field values and file links off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Form entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser 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, 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 employer name, injury description, or carrier field was sent. A page request from this script on a workers-comp intake page is not proof anyone was injured — and a pre-consent tag on that page can still treat workplace-injury consult intent as an audience segment from the URL alone. The page URL can say workers comp even when no form was submitted. Consent timing has not been tested. Review which tags you enable on intake and consult-booking 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. Visitor names, phone numbers, employer names, injury descriptions, injury dates, report-status answers, or insurance-carrier fields often depend on the fields you configure. A consultation request is not a filed claim. A marketing-tag page request is not proof anyone was injured. Cancelling or abandoning a consult later does not erase the employer and injury answers already stored next to a name — including while the visitor is still on that employer's payroll and before any claim is filed. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "confidential consultation" badge is not a verified storage path. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess workers-comp statutes, retaliation law, or benefit eligibility. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-workers-comp-attorney-plugin-privacy