Consignment shop plugin privacy
The intake that dates each thing you decided to let go
A consignment intake is a timeline of letting go: the wedding dress, the crib, the golf clubs, the designer bags — listed with photos, asking prices, and a payout account, dated. Read in order, one seller's rows tell a story no one typed deliberately: downsizing, divorce, a baby that didn't come home, money getting tight. Pawn captures a desperate Tuesday; consignment captures the slow version, item by item, in a boutique's WordPress database. Those fields are configured, not documented defaults. A consignment booking is a calendar row, not proof anyone sold or that an item changed hands. An item or photo answer is a form answer or uploaded file, not a verified life event. A page request is not proof anyone consigned goods. The page URL can say consignment shop even when no form is submitted. Ask what happens to the item list, the photos, the asking prices, the payout account, and the intake dates after a consignment closes — the stack that dated each thing someone decided to let go outlives the season. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake or drop-off page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a consignment-contract-law claim, a divorce-discovery claim, a child-welfare-inference claim, an insurer-underwriting claim, a tax-reporting claim, a resale-regulation 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 consignment intakes, drop-offs, and page tags go
Intakes and bookings on your WordPress site
Check which item-description, photo-upload, asking-price, payout-account, intake-date, or drop-off fields you enable, who can open form entries and consignment bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a consignment closes — when the item-plus-photo-plus-asking-price-plus-payout row still holds the letting-go timeline. Notification emails can also copy those fields off-site. One table can list every "wedding dress, crib, golf clubs — photos, $180/$40/$60, payout acct ••••9912, intake 3/12–4/02" stack next to a seller name. Ask your web vendor not to keep item and photo rows next to payout accounts and dated intakes in one open submissions list longer than operations need, and to purge those fields when a consignment closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored consignment booking is not proof anyone sold or that an item changed hands. An item or photo answer is not a verified life event.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the intake or drop-off page. That page request can reach a vendor host before anyone submits. The page URL can say consignment shop even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and drop-off pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "consignment privacy" badge is not a verified storage path.
Consignment intake, drop-off booking, 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 consignment 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 Tuesday 2pm drop-off window or a payout-pickup slot is a booking you create; a service name such as consignment intake or designer bags is a label you configure. Neither is a documented default. Item-description, photo-upload, asking-price, payout-account, or intake-date 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 sold or that an item changed hands — and a CSV export of "wedding dress, crib, golf clubs — photos, $180/$40/$60, payout acct ••••9912, intake 3/12–4/02" next to a seller name is still a calendar that pairs a letting-go timeline with a payout account. 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. | Consignment drop-off 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. Item-description, photo-upload, asking-price, payout-account, or intake-date fields are fields you add; they are not documented defaults. Completing the form can store an item-plus-photo-plus-asking-price-plus-payout stack ("wedding dress, crib, golf clubs — photos, $180/$40/$60, payout acct ••••9912, intake 3/12–4/02") — typed once so a boutique can list and pay out, into the same tables as a "consignment" label. An item or photo answer is a form answer or uploaded file, not a verified life event. A consignment booking is a calendar row, not proof anyone sold — and a staff login can open "Jordan, wedding dress.jpg, crib.jpg, payout ••••9912, intake 3/12–4/02" 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. | Item, photo, asking-price, and payout answers stored in WordPress; optional photos 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 item-description, photo, asking-price, or payout-account field was sent. A page request from this script is not proof anyone consigned goods. The page URL can say consignment shop even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and drop-off 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. Item-description, photo-upload, asking-price, payout-account, intake-date, or drop-off fields often depend on the fields you configure. A consignment booking is a calendar row, not proof anyone sold or that an item changed hands. An item or photo answer is a form answer or uploaded file, not a verified life event. A marketing-tag page request is not proof anyone consigned goods. The page URL can say consignment shop even when no form is submitted. The item-plus-photo-plus-asking-price-plus-payout row that dates each thing someone decided to let go — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that consignment letting-go timeline, not a pawn collateral ticket, an estate-sale whole-household list, a gold-buyer appraisal photo set, a junk-removal disposal haul, or a timeshare-exit asset inference. Ask your web vendor who can open entries, whether a marketing tag loads on the intake or drop-off page, and how long records and backups are kept. A "consignment privacy" or "boutique 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 consignment contract law, divorce discovery, child-welfare inference, insurer underwriting, tax reporting, or resale regulation. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake and drop-off pages, and backups.
Documentation snapshot: Oct 15, 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-consignment-shop-plugin-privacy