Payroll service plugin privacy
The client onboarding that uploads the whole staff, typed by the one person it isn't about
A payroll bureau's site can look like a calendar and a short new-client form. The same form often asks for an employee count, a pay schedule, a prior provider, and a direct-deposit question — and asks for a staff roster, a W-4 batch, a voided check, or a garnishment order — 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 new-client booking next to a staff roster with every SSN and pay rate, a garnishment PDF, and a marketing pixel — the client onboarding that uploads the whole staff, typed by the one person it isn't about, typed once into a vendor table next to a newsletter signup. A roster upload is a client document, not a verified employment record. A pay rate in a spreadsheet is what the employer typed, not a contract. An employee named in the roster never touched the form and may not know the row exists. A garnishment order is a stored document about a third party's legal matter, not the processor's finding. A consultation booking is an inquiry, not an engagement. A page request is not proof any business runs payroll. The page URL can say payroll-service even when no form is submitted. Ask what happens to the roster and garnishment files after the engagement closes — the quietest fields are the pay-rate column coworkers hide for a career and the garnishment order that tells the processor about legal trouble a desk neighbor will never learn. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the onboarding page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a claim about payroll-tax or IRS/941 compliance, a wage-and-hour claim, a garnishment-law claim, a claim about the bureau's data-security practices, a provider-quality claim, or a GDPR or other compliance assessment.
Scan your site for third-party requestsThe 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 new-client bookings, staff-roster uploads, and page tags go
Bookings and notes on your WordPress site
Check which employee-count, pay-schedule, prior-provider, or direct-deposit-question fields you enable, who can open form entries and new-client or quarterly-review bookings, which inboxes receive copies, and how long records, emails, and backups are kept after an onboarding closes — when the client onboarding uploads the whole staff, typed by the one person it isn't about. Notification emails can also copy those fields off-site. One table can list every Tuesday consultation next to a staff roster and a garnishment PDF. Ask your web vendor not to keep staff-roster, W-4 batch, voided-check, or garnishment-order uploads next to plaintext pay-rate 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 engagement. A roster in a form table is not a verified employment record.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the payroll-service new-client or quarterly-review page. That page request can reach a vendor host before anyone submits. The page URL can say payroll-service even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off new-client, quarterly-review, and onboarding pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted payroll" badge is not a verified storage path.
New-client / quarterly-review booking, payroll onboarding, 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 payroll SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 new-client consultation or a quarterly-review slot is a booking you create; a service name such as payroll onboarding or quarterly review is a label you configure. Neither is a documented default. Employee-count, pay-schedule, prior-provider, or direct-deposit questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry, not an engagement — and a CSV export of a new-client row next to an employee-count and a prior-provider note is still a calendar that holds a company's payroll shape 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. | New-client consultation and quarterly-review bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Employee-count, pay-schedule, prior-provider, or direct-deposit-question fields are fields you add; they are not documented defaults. Completing the form can store an employee count next to a pay schedule, a prior-provider answer, a direct-deposit question, and optional staff-roster, W-4 batch, voided-check, or garnishment-order uploads — typed once as the client onboarding that uploads the whole staff, typed by the one person it isn't about, into the same tables as a newsletter signup. A roster upload is a client document, not a verified employment record. A pay rate in a spreadsheet is what the employer typed, not a contract. An employee named in the roster never touched the form and may not know the row exists. A garnishment order is a stored document about a third party's legal matter, not the processor's finding — and a staff login can open "Acme LLC, 42 employees, biweekly, prior ADP, roster.xlsx with SSNs and routing numbers, W-4 zip, voided-check PDF, garnishment for Jane D." next to everyone else's resume. 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. | Payroll onboarding entries stored in WordPress; optional staff-roster, W-4 batch, voided-check, and garnishment-order uploads in the site uploads/forminator folder | 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, 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 employee-count, pay-schedule, prior-provider, or direct-deposit field was sent. A page request from this script is not proof any business runs payroll. The page URL can say payroll-service even when no form is submitted. Consent timing has not been tested. Review which tags you enable on new-client, quarterly-review, and onboarding 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. Employee-count, pay-schedule, prior-provider, or direct-deposit-question fields often depend on the fields you configure. A roster upload is a client document, not a verified employment record. A pay rate in a spreadsheet is what the employer typed, not a contract. An employee named in the roster never touched the form and may not know the row exists. A garnishment order is a stored document about a third party's legal matter, not the processor's finding. A consultation booking is an inquiry, not an engagement. A marketing-tag page request is not proof any business runs payroll. The page URL can say payroll-service even when no form is submitted. The client onboarding that uploads the whole staff, typed by the one person it isn't about — that is a storage path next to a garnishment PDF, not a feature these plugins claim. This page is about that payroll onboarding, not a staffing-agency applicant packet, a tax-preparer SSN folder, or a debt-collection spreadsheet of strangers. Ask your web vendor who can open entries, whether a marketing tag loads on the onboarding page, and how long roster rows and backups are kept after the engagement closes. A "trusted payroll" 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 payroll-tax or IRS/941 compliance, wage-and-hour law, garnishment law, the bureau's data-security practices, or provider quality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on onboarding pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-payroll-service-plugin-privacy