Document shredding plugin privacy
The pickup form that catalogs what you're paying to destroy
The pickup form is the inverse of the service — a company paid to make records vanish starts by creating a fresh one. The quote asks what you're destroying (medical files, client records, financials), why, the pickup address, and the date the boxes sit unattended at the curb. The certificate-of-destruction request is itself a dated inventory of the most sensitive paper you own, stored in a WordPress database. Those fields are configured, not documented defaults. A shredding booking is a calendar row, not proof boxes were destroyed. A content-category or CoD answer is a form answer or uploaded file, not a verified destruction certificate. A page request is not proof anyone booked a pickup. The page URL can say document shredding even when no form is submitted. Ask what happens to the address, the content categories, the curb window, and the CoD inventory after a pickup closes — the stack that cataloged your paper outlives the shred. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking or quote page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a destruction-certificate-legality claim, a HIPAA-shredding-compliance claim, a chain-of-custody-validity 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 shredding bookings, destruction inventories, and page tags go
Bookings and inventories on your WordPress site
Check which address, content-category, destruction-reason, curb-window, certificate-of-destruction, inventory, or intake-upload fields you enable, who can open form entries and shredding bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a pickup closes — when the address-plus-inventory-plus-CoD row still holds a destruction catalog next to a curb-unattended window. Notification emails can also copy those fields off-site. One table can list every "12 Oak St · pickup Tue curb · boxes: medical files · client records · financials · why: office close · CoD requested · inventory: 14 bankers boxes" stack next to a customer name. Ask your web vendor not to keep destruction inventories and CoD requests next to home addresses and curb windows in one open submissions list longer than operations need, and to purge those fields when a pickup closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored shredding booking is not proof boxes were destroyed. A content-category or CoD answer is not a verified destruction certificate.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say document shredding even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "document shredding privacy" badge is not a verified storage path.
Document-shredding booking, destruction-inventory, 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 document-shredding 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 curb-pickup window or a certificate-of-destruction slot is a booking you create; a service name such as on-site shred or off-site destruction is a label you configure. Neither is a documented default. Address, content-category, destruction-reason, curb-window, certificate-of-destruction, or inventory questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof boxes were destroyed — and a CSV export of "12 Oak St · pickup Tue curb · boxes: medical files · client records · financials · why: office close · CoD requested · inventory: 14 bankers boxes" next to a customer name is still a calendar that pairs a destruction inventory with a curb-unattended window. 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. | Document-shredding 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. Address, content-category, destruction-reason, curb-window, certificate-of-destruction, or inventory fields are fields you add; they are not documented defaults. Completing the form can store an address-plus-inventory-plus-CoD stack ("12 Oak St · pickup Tue curb · boxes: medical files · client records · financials · why: office close · CoD requested · inventory: 14 bankers boxes") — typed once so a shredder can quote a destruction job, into the same tables as a "document shredding" label. A content-category or CoD answer is a form answer or uploaded file, not a verified destruction certificate. A shredding booking is a calendar row, not proof boxes were destroyed — and a staff login can open "Jordan, 12 Oak St, medical files, client records, CoD requested, 14 bankers boxes" 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. | Address, inventory, and CoD answers stored in WordPress; optional inventory lists 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 address, inventory, or CoD field was sent. A page request from this script is not proof anyone booked a pickup. The page URL can say document shredding even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote 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. Address, content-category, destruction-reason, curb-window, certificate-of-destruction, or inventory fields often depend on the fields you configure. A shredding booking is a calendar row, not proof boxes were destroyed. A content-category or CoD answer is a form answer or uploaded file, not a verified destruction certificate. A marketing-tag page request is not proof anyone booked a pickup. The page URL can say document shredding even when no form is submitted. The address-plus-inventory-plus-CoD row that cataloged your paper for a shredder — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that destruction-ledger stack, not a biohazard cleanup address event, a junk-removal shame photo, or an alarm-company vacancy window. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "document shredding privacy" or "certified destruction" 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 destruction-certificate legality, HIPAA shredding compliance, or chain-of-custody validity. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking and quote 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-document-shredding-plugin-privacy