Fingerprinting plugin privacy

The live-scan booking that logs why you must prove who you are

A fingerprinting appointment can store a reason code next to a name, a date of birth, and a callback number. Nobody books a live scan for fun. The reason itself, stored in plain text in a booking plugin, can say employment, immigration, adoption, firearm permit, or expungement before anyone is printed. ID photos and authorization PDFs can sit in the site uploads folder. That pairing can sit in a form plugin entries table any staffer can open after a slot is missed. The appointments list is a running feed of who in town is being vetted, and for what, this week. Reason-code, full-name, dob, callback-number, appointment-type, id-photo, requesting-agency, ori-number, and phone fields are configured, not documented defaults. Optional ID photos go in the site uploads folder. A reason code labeled employment or expungement is a stored service reason, not proof anyone is being vetted. A date of birth is a stored date, not proof of identity. An appointment type labeled live scan is a stored service name, not proof anyone was printed. An ID photo is an upload, not proof of identity. A fingerprinting booking is not proof anyone must prove who they are. A page request is not proof anyone booked a live scan. The page URL can say fingerprinting even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on booking and intake pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, an identity claim, a background-check claim, an immigration claim, an adoption claim, a firearm-permit claim, an expungement claim, a HIPAA 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 live-scan bookings, uploaded files, and page tags go

Fingerprinting bookings and forms handled on your WordPress site

Check which reason-code, full-name, dob, callback-number, appointment-type, id-photo, requesting-agency, ori-number, or phone fields you enable, who can open form entries and bookings, where uploaded ID photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a slot is missed. Notification emails can also copy the same reason codes, names, dates of birth, callback numbers, appointment types, ID photos, requesting-agency names, and ORI numbers off-site. One table can name a reason code, a date of birth, and a callback number next to an appointment type, even when no print is taken. The appointments list can show who is booked this week and for what reason. Ask your web vendor not to collect a reason code next to a name and a date of birth on the first public form, not to store those files next to an appointment type in one open submissions list, and to purge unused pairings after the slot passes. A privacy-policy page does not by itself limit who can export an intake list or republish an upload. A stored reason code is not proof anyone is being vetted.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the fingerprinting booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say fingerprinting even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored reason codes, dates of birth, or ID photos. A "FBI channeler" badge is not a verified storage path.

Fingerprinting booking, 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 live-scan or FBI-channeler software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A fingerprinting appointment is a booking you create; a service name such as live scan, ink card, FBI channeler, or mobile print is a label you configure. Neither is a documented default. The stored service name can say fingerprinting in plain text before anyone is printed. Reason-code, full-name, dob, callback-number, appointment-type, requesting-agency, ori-number, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. A reason code labeled employment, immigration, adoption, firearm permit, or expungement is a stored service reason, not proof anyone is being vetted. A date of birth is a stored date, not proof of identity. An appointment type labeled live scan is a stored service name, not proof anyone was printed. A booked slot is not proof anyone must prove who they are, and is not proof a print was taken. Cancelling or missing the slot later does not erase the reason code, name, date of birth, or callback number already stored next to an appointment type, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a print is not a documented default of the plugin. The appointments list can show who is booked this week and for what reason. 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.

Live-scan bookings, custom reason-code fields, and automatic confirmation emails 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. Reason-code, full-name, dob, callback-number, appointment-type, requesting-agency, ori-number, or phone questions are fields you add; they are not documented defaults. ID photos and authorization PDFs are files you accept; those file types are not documented defaults. A reason code labeled employment, immigration, adoption, firearm permit, or expungement is a stored service reason, not proof anyone is being vetted. A date of birth is a stored date, not proof of identity. An appointment type labeled live scan is a stored service name, not proof anyone was printed. An ID photo is an upload, not proof of identity. A fingerprinting booking is not proof anyone must prove who they are. 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. How long a pairing sits after a slot is missed is not a documented default of the plugin.

Live-scan intake 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 a reason-code, dob, or callback-number field was sent. A page request from this script on a fingerprinting intake page is not proof anyone booked a live scan, and a pre-consent tag on that page can still treat fingerprinting interest as an audience segment from the URL alone. The page URL can say fingerprinting even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged intake page can re-confirm fingerprinting interest next to a stored reason code; this row does not claim a print was taken from that request.

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. Reason-code, full-name, dob, callback-number, appointment-type, id-photo, requesting-agency, ori-number, or phone fields often depend on the fields you configure. A reason code labeled employment, immigration, adoption, firearm permit, or expungement is a stored service reason, not proof anyone is being vetted. A date of birth is a stored date, not proof of identity. An appointment type labeled live scan is a stored service name, not proof anyone was printed. An ID photo is an upload, not proof of identity. A fingerprinting booking is not proof anyone must prove who they are. A marketing-tag page request is not proof anyone booked a live scan. The page URL can say fingerprinting even when no form is submitted. The reason code, the name, the date of birth, and the callback number can sit after a slot is missed. This page is about a live-scan booking that logs why someone must prove who they are, not a notary attestation file, not an expungement petition, and not a bail-bonds co-signer form. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. A "FBI channeler" 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 identity, background-check, immigration, adoption, firearm-permit, or expungement claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-fingerprinting-plugin-privacy