Biohazard cleanup plugin privacy
Where does the quote request that describes what happened in the house go?
Nobody fills this form speculatively. An address plus a what-happened field is itself a record that something terrible occurred there — typed by a family member on the worst day of their life, often with room photos attached. Those answers land in a local-first form or upload plugin before any crew arrives. Decline the quote and the photos can stay in the uploads folder, an inbox attachment, or a backup. The home may sell later; the WordPress database can still hold that sentence pinned to the address. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that anything happened at an address. A quote request is not a confirmed incident. This sample reviews three plugins' documentation. Check which address and what-happened fields you collect, who can open entries, where uploads land, which tags load on the quote page, and how long records, files, and backups are kept.
Documentation review only. This is not legal advice, an OSHA assessment, a bloodborne-pathogen-regulation claim, a stigmatized-property-disclosure 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, uploaded scene photos, email inboxes, staff permissions, vendor accounts, or backups.
Where addresses, what-happened text, scene photos, and page tags go
Entries and files handled on your WordPress site
Check which address, what-happened, service-type, or scene-photo fields you enable, who can open form entries, where uploaded room photos live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a quote that never became a job — including after the property sells. Notification emails can also copy the same address, narrative, and photos off-site. Ask your web vendor not to require graphic scene photos or detailed cause-of-death text on the first public quote when a short service category would do, and to delete declined-quote uploads on a documented schedule.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the biohazard quote page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off quote pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded scene photos. A "confidential quote" badge is not a verified storage path.
Biohazard quote, 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 remediation SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. Scene photos, room images, or property condition pictures are files you accept; they are not documented defaults. An uploaded scene photo is not a confirmed incident. Decline the quote and the inbox copy can still remain. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified. | Visitor files stored under wp-content/uploads/wp_dndcf7_uploads | 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, what-happened, service-type, or contact fields are fields you add; they are not documented defaults. Scene photos, room images, or property condition pictures are files you accept; they are not documented defaults. A submitted quote request is not a confirmed incident. Declining the quote does not by itself delete the entry or the file. Notification emails can copy field values and attachments off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in WordPress; file 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 an address, what-happened text, or scene photo was sent. A page request from this script on a biohazard quote page is not proof that anything happened at an address — and a pre-consent tag on that page can still treat biohazard-cleanup shopping intent as an audience segment from the URL alone. The page URL can say biohazard cleanup even when no form is submitted. Consent timing has not been tested. Review which tags you enable on 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. Addresses, what-happened free text, or scene-photo uploads often depend on the fields you configure. A quote request is not a confirmed incident. A marketing-tag page request is not proof that anything happened at an address. Decline the quote and the photos can still remain — including after the home sells. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the quote page, and how long records and backups are kept. A "confidential" or "discreet service" 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 OSHA, bloodborne-pathogen regulation, or stigmatized-property disclosure law. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on quote pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress funeral plugin privacy
- WordPress file upload plugin privacy
- WordPress real estate plugin privacy
- All privacy guides
/wp-biohazard-cleanup-plugin-privacy