Pottery studio plugin privacy

The keepsake booking that files a baby's handprint in the uploads folder

A pottery studio can sell keepsake sessions for baby handprint plates, infant footprint tiles, or memorial hand impressions. A booking form can collect the parent name, phone, child's name or age, session type, photos of the impressions, kiln-pickup date, and a card on file. Those photos can sit in the site uploads folder next to the parent name. Parent-name, phone, child-name, child-age, session-type, handprint-photo, kiln-pickup, and card-on-file fields are configured, not documented defaults. Optional impression photos go in the site uploads folder. A booking is not proof a plate was fired. A handprint photo is an upload, not a biometric identity. A kiln-pickup date is a stored date, not proof the family walks back in. A child's name or age is a stored note, not a party roster. A memorial-session label is a stored service name, not proof anyone died. A page request is not proof anyone booked. The page URL can say pottery studio 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 pickup pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a biometric claim, a medical claim, a HIPAA claim, an occupancy claim, a memorial claim, a kids-party 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 keepsake bookings, impression photos, and page tags go

Keepsake bookings and forms handled on your WordPress site

Check which parent-name, phone, child-name, child-age, session-type, handprint-photo, kiln-pickup, or card-on-file fields you enable, who can open form entries and bookings, where uploaded impression photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a session that never became a pickup. Notification emails can also copy the same parent names, child notes, and handprint photos off-site. One table can name the parent, photograph a baby's hand, and attach a kiln-pickup date next to a phone, even when the plate is never fired. Ask your web vendor not to collect a handprint photo next to a parent name and a child's age on the first public form, not to store that keepsake row next to a name in one open submissions list, and to purge unused sessions after the pickup date passes. A privacy-policy page does not by itself limit who can export a booking list or republish an upload. A stored booking is not proof a plate was fired.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the pottery-studio booking or pickup page. That page request can reach a vendor host before anyone submits. The page URL can say pottery studio even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and pickup pages if you do not want that page request. A browser scan cannot inspect stored parent names, child notes, or handprint photos. A "keepsake studio" badge is not a verified storage path.

Pottery-studio booking, keepsake, 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 kiln or studio POS 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 keepsake session is a booking you create; a service name such as baby handprint plate, infant footprint tile, memorial impression, or kiln pickup is a label you configure. Neither is a documented default. Parent-name, phone, child-name, child-age, session-type, handprint-photo, kiln-pickup, or card-on-file questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked session is not proof a plate was fired, and is not proof the family walks back in. Cancelling or missing the slot later does not erase the handprint photos, child notes, or parent name already stored next to a phone, and does not unsend a confirmation email already delivered. How long that row sits after a session that never became a pickup is not a documented default of the plugin. 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.

Keepsake bookings, custom intake 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. Parent-name, phone, child-name, child-age, session-type, handprint-photo, kiln-pickup, or card-on-file questions are fields you add; they are not documented defaults. A handprint photo is a file you accept; that file type is not a documented default. A booking is not proof a plate was fired. A handprint photo is an upload, not a biometric identity. A kiln-pickup date is a stored date, not proof the family walks back in. A child name or age is a stored note, not a party roster. A memorial-session label is a stored service name, not proof anyone died. 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 keepsake row sits after the session never became a pickup is not a documented default of the plugin.

Keepsake and handprint-photo 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 handprint-photo, child-name, or parent-name field was sent. A page request from this script is not proof anyone booked. The page URL can say pottery studio even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and pickup pages. Keep marketing tags off those pages if you do not want that page request. A tagged keepsake page can re-confirm pottery-studio interest next to a stored parent name and files; this row does not claim a pickup 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. Parent-name, phone, child-name, child-age, session-type, handprint-photo, kiln-pickup, or card-on-file fields often depend on the fields you configure. A booking is not proof a plate was fired. A handprint photo is an upload, not a biometric identity. A kiln-pickup date is a stored date, not proof the family walks back in. A child's name or age is a stored note, not a party roster. A memorial-session label is a stored service name, not proof anyone died. A marketing-tag page request is not proof anyone booked. The page URL can say pottery studio even when no form is submitted. The handprint photo, the parent name, and the kiln-pickup date can sit after the session never becomes a pickup. This page is about a keepsake booking that files a baby's handprint in the uploads folder, not a voiceover voiceprint, not a laser-tag kids-party roster, not a monument-engraving memorial proof, and not a gallery image portfolio. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or pickup page, and how long records and backups are kept. A portfolio 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 biometric identification, medical status, HIPAA, occupancy, memorial-proof, or kids-party claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and pickup 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-pottery-studio-plugin-privacy