Tanning salon plugin privacy
The membership log that counts your sessions toward a dermatology chart
State rules make tanning salons record what other gyms don't: skin type, session timestamps, bed and intensity, parental consent where minors are allowed, and signed UV-risk acknowledgments. The membership log is a dose history — the exact exposure record a dermatologist or an insurer would want — kept in a WordPress membership or booking stack that was built to bill monthly, not to hold what is effectively radiation paperwork. Those fields are configured, not documented defaults. A session booking is a calendar row, not proof anyone used a bed. A skin-type answer is what a guest typed, not a dermatology chart. A UV acknowledgment is a form checkbox, not a clinical consent record. An intake upload is a client document in a site uploads folder. A page request is not proof anyone booked a session. The page URL can say tanning salon even when no form is submitted. Ask what happens to the skin-type answers and the session timestamps after a membership lapses — the membership log that counts your sessions toward a dermatology chart outlives the visit. 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 dermatology or UV-safety-law claim, a parental-consent-law claim, a tanning-efficacy claim, an insurer-underwriting claim, a clinical-fitness 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 bed sessions, UV intakes, and page tags go
Intakes and bookings on your WordPress site
Check which skin-type, bed-and-intensity, parental-consent, UV-acknowledgment, or intake-upload fields you enable, who can open form entries and bed-session bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a membership lapses — when the membership log counts sessions toward a dermatology chart. Notification emails can also copy those fields off-site. One table can list every skin-type answer a guest typed next to a Friday slot and a bed-intensity note. Ask your web vendor not to keep intake uploads next to UV-intake answers in one open submissions list longer than operations need, and to purge booking rows when a session is cancelled or a membership ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored session booking is not proof anyone used a bed. A skin-type answer is not a dermatology chart.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the tanning-salon booking or UV-intake page. That page request can reach a vendor host before anyone submits. The page URL can say tanning salon even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off bed-session booking and UV-intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "salon privacy" badge is not a verified storage path.
Bed-session booking, tanning UV-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 salon or EHR SaaS tools 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 Friday level-3 bed slot or a UV-session package is a booking you create; a service name such as tanning salon or bed session is a label you configure. Neither is a documented default. Skin-type, bed-and-intensity, parental-consent, or UV-risk acknowledgment 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 used a bed — and a CSV export of a Friday 3pm level-3 slot next to a skin-type answer and a parental-consent note is still a calendar that holds a dose history 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. | Bed-session 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. Skin-type, bed-and-intensity, parental-consent, or UV-risk acknowledgment fields are fields you add; they are not documented defaults. Completing the form can store a skin-type answer next to a bed-intensity note, a parental-consent row, a signed UV-risk acknowledgment, a session timestamp, and optional intake uploads — typed once as the membership log that counts your sessions toward a dermatology chart, into the same tables as a monthly membership bill. A skin-type answer is what a guest typed, not a dermatology chart. A UV acknowledgment is a form checkbox, not a clinical consent record — and a staff login can open "Alex, skin type III, bed level 3, parental consent on file, UV ack Friday 3pm, intake.pdf" next to everyone else's resume. A session booking is a calendar row, not proof anyone used a bed. 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. | Tanning UV-intake answers stored in WordPress; optional intake 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 a skin-type, bed-intensity, parental-consent, or UV-acknowledgment field was sent. A page request from this script is not proof anyone booked a session. The page URL can say tanning salon even when no form is submitted. Consent timing has not been tested. Review which tags you enable on bed-session booking and UV-intake 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. Skin-type, bed-and-intensity, parental-consent, UV-acknowledgment, or intake-upload fields often depend on the fields you configure. A session booking is a calendar row, not proof anyone used a bed. A skin-type answer is what a guest typed, not a dermatology chart. A UV acknowledgment is a form checkbox, not a clinical consent record. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone booked a session. The page URL can say tanning salon even when no form is submitted. The membership log that counts your sessions toward a dermatology chart — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that UV session exposure log, not a hair-salon patch-test book, a medspa aesthetics intake, or a gym body-measurement membership. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "salon privacy" or "HIPAA" 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 dermatology advice, UV safety law, parental-consent law, tanning efficacy, insurer underwriting, or clinical fitness. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and intake 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-tanning-salon-plugin-privacy