HR consulting plugin privacy

The help-me-fire-someone request that names the employee before they know

An HR consultant's site can look like a calendar and a short intake form. The same form often asks company size, the employee's name or role, what happened, how urgent it is, and whether prior warnings exist — and asks for a disciplinary file or a handbook — and stores those answers next to the owner's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a consultation booking next to an employee name, a describe-the-situation paragraph about performance or suspected theft, a how-urgent dropdown that says "this week," and a marketing pixel — the help-me-fire-someone request that names the employee before they know, typed once into a vendor table next to a newsletter signup. A consultation request is an inquiry, not an investigation or a finding. A describe-the-situation answer is the employer's account, not an adjudicated fact. The employee named never touched the form and may not know the row exists. An uploaded disciplinary file is a stored client document, not a legal record. A how-urgent answer is a preference, not a lawful-termination determination. A page request is not proof any workplace has a problem. The page URL can say hr-consulting even when no form is submitted. Ask what happens to the disciplinary files and employee-name rows after the engagement closes — the quietest field is the how-urgent dropdown that turns a consulting lead into a termination date before the meeting. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a claim about employment or wrongful-termination law, an EEOC or discrimination-procedure claim, an investigation-standards claim, a consultant licensure claim, a claim about the firm's data-security practices, a provider-quality 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 consultation bookings, disciplinary-file uploads, and page tags go

Bookings and notes on your WordPress site

Check which company-size, employee-name-or-role, describe-the-situation, how-urgent, or prior-warnings-question fields you enable, who can open form entries and consultation or investigation-scoping bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a consulting engagement closes — when the help-me-fire-someone request that names the employee before they know. Notification emails can also copy those fields off-site. One table can list every Tuesday consultation next to a disciplinary-file PDF and a handbook. Ask your web vendor not to keep disciplinary-file or handbook uploads next to plaintext employee-name and describe-the-situation rows in one open submissions list longer than operations need, and to purge intake rows when the engagement closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not an investigation. A describe-the-situation answer in a form table is not an adjudicated fact.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the HR-consulting consultation or intake page. That page request can reach a vendor host before anyone submits. The page URL can say hr-consulting even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off consultation, investigation-scoping, and HR-consulting intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted HR advisor" badge is not a verified storage path.

Consultation / investigation-scoping booking, HR-consulting intake, 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. Specialty HR-consulting SaaS 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 Tuesday consultation or an investigation-scoping slot is a booking you create; a service name such as HR consult or investigation scoping is a label you configure. Neither is a documented default. Company-size, employee-name-or-role, describe-the-situation, how-urgent, or prior-warnings questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry, not an investigation or a finding — and a CSV export of a consultation row next to an employee-name-or-role and a how-urgent note is still a calendar that holds a named personnel case beside a contact name. Emails can include those custom fields and copy the appointment off-site. 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.

Consultation and investigation-scoping bookings 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. Company-size, employee-name-or-role, describe-the-situation, how-urgent, or prior-warnings-question fields are fields you add; they are not documented defaults. Completing the form can store a company-size answer next to an employee name or role, a describe-the-situation note, a how-urgent dropdown, a prior-warnings answer, and optional disciplinary-file or handbook uploads — typed once as the help-me-fire-someone request that names the employee before they know, into the same tables as a newsletter signup. A consultation request is an inquiry, not an investigation or a finding. A describe-the-situation answer is the employer's account, not an adjudicated fact. The employee named never touched the form and may not know the row exists. An uploaded disciplinary file is a client document, not a legal record — and a staff login can open "Acme LLC, 18 employees, Jane D. — performance / suspected theft, this week, prior verbal warning, disciplinary-file.pdf, handbook.pdf" next to everyone else's resume. A how-urgent answer is a preference, not a lawful-termination determination. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

HR-consulting intake entries stored in WordPress; optional disciplinary-file and handbook 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 a company-size, employee-name-or-role, describe-the-situation, how-urgent, or prior-warnings field was sent. A page request from this script is not proof any workplace has a problem. The page URL can say hr-consulting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on consultation, investigation-scoping, and HR-consulting intake 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. Company-size, employee-name-or-role, describe-the-situation, how-urgent, or prior-warnings-question fields often depend on the fields you configure. A consultation request is an inquiry, not an investigation or a finding. A describe-the-situation answer is the employer's account, not an adjudicated fact. The employee named never touched the form and may not know the row exists. An uploaded disciplinary file is a stored client document, not a legal record. A how-urgent answer is a preference, not a lawful-termination determination. A marketing-tag page request is not proof any workplace has a problem. The page URL can say hr-consulting even when no form is submitted. The help-me-fire-someone request that names the employee before they know — that is a storage path next to a disciplinary-file PDF, not a feature these plugins claim. This page is about that HR-consulting intake, not a staffing-agency applicant folder, a payroll-service staff roster, a mystery-shopper review form, or the HR software category page. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long disciplinary-file rows and backups are kept after the engagement closes. A "trusted HR advisor" 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 employment or wrongful-termination law, EEOC/discrimination procedure, investigation standards, consultant licensure, the firm's data-security practices, or provider quality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-hr-consulting-plugin-privacy