Piercing studio plugin privacy

The consent file that keeps a parent's license next to a child's birth certificate

A piercing studio is where ID verification meets minors: shops often collect a parent's license and a child's birth certificate with the under-18 consent, then keep both on file. The booking plugin ends up holding a family's identity documents and a photo of a minor's healing piercing from the aftercare follow-up — collected for verification, retained because nobody wrote the delete step. Those fields are configured, not documented defaults. A booking is a calendar row, not proof anyone was pierced or that a scanned ID was valid. An aftercare upload is a file a parent or shop attached, not a verified medical record. A page request is not proof anyone booked a piercing. The page URL can say piercing studio even when no form is submitted. Ask what happens to the license scans, the birth certificates, the signed consents, and the aftercare photos after a visit ends — the stack that verified a minor outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the consent page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a state piercing-law claim, a minor-consent statute claim, an ID-custody claim, a COPPA or safeguarding 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 consent files, ID uploads, and page tags go

Intakes and bookings on your WordPress site

Check which parent-license, birth-certificate, consent, minor-age, guardian-contact, or aftercare-photo fields you enable, who can open form entries and piercing bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit ends — when the license-plus-birth-cert-plus-consent-plus-aftercare row still holds a family's identity documents. Notification emails can also copy those fields off-site. One table can list every "parent-license.jpg, birth-cert.pdf, under-18 earlobe consent, aftercare-healing.jpg" stack next to a guardian name. Ask your web vendor not to keep parent licenses next to birth certificates and aftercare photos of minors in one open submissions list longer than operations need, and to purge those fields when a visit closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not proof anyone was pierced or that a scanned ID was valid. An aftercare upload is not a verified medical record.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the consent or aftercare-upload page. That page request can reach a vendor host before anyone submits. The page URL can say piercing studio even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off under-18 consent pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "piercing privacy" badge is not a verified storage path.

Consent booking, ID-upload, 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 studio SaaS tools 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 Saturday under-18 earlobe slot or a piercing package is a booking you create; a service name such as piercing studio or minor consent piercing is a label you configure. Neither is a documented default. Parent-license, birth-certificate, consent, minor-age, or guardian-contact questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone was pierced or that a scanned ID was valid — and a CSV export of "Sat 2pm, under-18 earlobe, guardian Casey, age 16" next to a parent name is still a calendar that pairs a minor with a guardian contact. 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.

Piercing appointments 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. Parent-license, birth-certificate, consent, minor-age, or guardian-contact fields are fields you add; they are not documented defaults. Completing the form can store a license-plus-birth-cert-plus-consent-plus-aftercare stack ("parent-license.jpg, birth-cert.pdf, under-18 earlobe consent, aftercare-healing.jpg") — uploaded once so a shop can verify an under-18 piercing, into the same tables as a "piercing studio" label. An aftercare upload is a file a parent or shop attached, not a verified medical record. A booking is a calendar row, not proof anyone was pierced — and a staff login can open "Casey, parent-license.jpg, birth-cert.pdf, aftercare-healing.jpg" 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.

Consent, license, birth-certificate, and aftercare answers stored in WordPress; optional ID and photo 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 parent-license, birth-certificate, consent, or aftercare field was sent. A page request from this script is not proof anyone booked a piercing. The page URL can say piercing studio even when no form is submitted. Consent timing has not been tested. Review which tags you enable on under-18 consent and aftercare-upload 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. Parent-license, birth-certificate, consent, minor-age, guardian-contact, or aftercare-photo fields often depend on the fields you configure. A booking is a calendar row, not proof anyone was pierced or that a scanned ID was valid. An aftercare upload is a file a parent or shop attached, not a verified medical record. A marketing-tag page request is not proof anyone booked a piercing. The page URL can say piercing studio even when no form is submitted. The license-plus-birth-cert-plus-consent-plus-aftercare row that keeps a parent's license next to a child's birth certificate — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that under-18 piercing consent file, not an adult tattoo consent form, a tattoo-removal consult photo, a go-kart license-scan kiosk, a flight-school federal ID file, or an orthodontist child-photo upload. Ask your web vendor who can open entries, whether a marketing tag loads on the consent page, and how long records and backups are kept. A "piercing privacy" or "ID compliant" 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 state piercing laws, minor-consent statutes, ID-custody duties, COPPA, or safeguarding practice. Review stored records, bookings, connected services, exports, notification emails, marketing tags on consent 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-piercing-studio-plugin-privacy