Mystery shopper plugin privacy
The performance review written by a stranger the employee never saw
A mystery-shopping WordPress stack is not only a contact form — it is a covert evaluation file the named employee never opens. The shopper application holds payment-adjacent identity and which stores they can visit unrecognized. The evaluation submission names or describes an employee, scores friendliness, upsell attempts, and policy compliance, and sometimes attaches receipts or covert photos. The employee is scored by a paid stranger, read by their manager, and never consented or knew — and the same plugin table that hides the shopper from the stores scores the worker who never saw the row. No breach required: a CSV export of last quarter's evaluations is still a performance review written by a stranger. Ask how long evaluations are kept and who can export them — retention length is who still holds the score sheet, not housekeeping. A marketing tag on the same evaluation page can send a page request to a vendor host before anyone submits — and that page request alone can treat mystery-shopper evaluation intent as an audience segment from the URL. A page request is not proof any store was shopped. An evaluation row is one visit's impression, not an employment record or a performance verdict. Employee-identifier and score fields are fields you configure, not defaults. 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 evaluation page, and how long past evaluations, files, and backups are kept.
Documentation review only. This is not legal advice, an employment-law claim, a workplace-surveillance or consent-requirement assessment, an evaluation-fairness claim, a GDPR or other compliance assessment, or a judgment about employers, shoppers, or employees.
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 evaluations, shopper applications, and page tags go
Entries, uploads, and bookings on your WordPress site
Check which employee-identifier, score, narrative, receipt, photo, or shopper-identity fields you enable, who can open form entries and assignment bookings, where uploaded receipts or covert photos live in the uploads folder, which inboxes receive copies, who can export CSV evaluations next to named employees — and who can export the shopper burn list the stores must not see — and how long past evaluations, files, and backups are kept after the visit ends. Notification emails can also copy the same employee description and score answers off-site. Ask your web vendor not to put every score next to a named employee on one open table when a short visit ID would do — and ask how long last quarter's evaluation rows are kept.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the mystery-shopper evaluation 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 evaluation and application pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or who exported the evaluations. A "confidential audit records" badge is not a verified storage or visibility path.
Mystery-shopper evaluation, shopper-application, 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 mystery-shopping 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 store-visit assignment or shopper-application slot is a booking you create; a service name such as retail audit or dining evaluation is a label you configure. Neither is a documented default. Shopper-identity, payment-adjacent, burn-list store, availability, or unrecognized-visit questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof any store was shopped — and a CSV export of shopper identities next to store assignments is the burn list that must not reach the stores being audited. 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. | Shopper applications and assignment visit 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-name, employee-description, register-number, visit-time, friendliness-score, upsell-score, policy-compliance, narrative, shopper-identity, or payment-adjacent questions are fields you add; they are not documented defaults. A receipt, covert-photo, or supporting upload is a file you accept; it is not a documented default. One evaluation entry can store a named or described employee next to scored answers and a photo the employee never saw — and the same plugin table that holds that score sheet also holds shopper identities the stores must not see. An evaluation row is one visit's impression, not an employment record or a performance verdict. Ask how long evaluations are kept and who can export them: retention length is who still holds last quarter's scores, not housekeeping. 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 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 name, score sheet, or covert photo was sent. A page request from this script on a mystery-shopper evaluation page is not proof any store was shopped — and a pre-consent tag on that page can still treat mystery-shopper evaluation intent as an audience segment from the URL alone. The page URL can say mystery shopper even when no form is submitted. Consent timing has not been tested. Review which tags you enable on evaluation and application 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 identifiers, score scales, narratives, receipt uploads, or shopper-identity fields often depend on the fields you configure. An evaluation row is one visit's impression, not an employment record or a performance verdict. A marketing-tag page request is not proof any store was shopped. Ending the assignment later does not erase the named employee already stored next to a score — and last quarter's evaluation may still be the review the worker never saw. Ask your web vendor who can open entries, who can export evaluations, who can export the shopper burn list, where uploaded files live, whether a marketing tag loads on the evaluation page, and how long past evaluations and backups are kept. A "confidential audit records" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and evaluation-export paths only and does not assess employment law, workplace-surveillance law, consent requirements, or evaluation fairness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on evaluation 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-mystery-shopper-plugin-privacy