Panic room plugin privacy
The quote form that diagrams the room no one is supposed to know exists
The entire value of a panic room is that nobody knows it exists. A quote form can collect the floor plan, the trigger locations, and who holds the combination. That spec sheet can sit in a form plugin entries table. Floor-plan, trigger-locations, combination-holders, homeowner-name, phone, address, install-date, and hidden-door fields are configured, not documented defaults. Optional floor-plan files go in the site uploads folder. A quote request is not proof a room was installed. A floor plan is an upload, not proof a hidden room exists. Trigger locations are stored notes, not a live security system. A combination-holders list is stored names, not proof who can open the door. A hidden-door label is a stored service name, not proof a door is there. A page request is not proof anyone booked. The page URL can say panic room 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 quote pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a security-system claim, a safe-room rating claim, an occupancy claim, a valuables-vault claim, a staffed-protection claim, a weather-shelter 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 panic-room quotes, floor plans, and page tags go
Install quotes and forms handled on your WordPress site
Check which floor-plan, trigger-locations, combination-holders, homeowner-name, phone, address, install-date, or hidden-door fields you enable, who can open form entries and bookings, where uploaded floor plans live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became an install. Notification emails can also copy the same floor plans, trigger notes, combination-holder names, and addresses off-site. One table can name the house, who holds the combination, and the floor plan next to a phone, even when the install never happens. Ask your web vendor not to collect a floor plan next to combination-holder names and trigger locations on the first public form, not to store that spec sheet next to an address in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list or republish an upload. A stored quote is not proof a room was installed.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the panic-room booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say panic room 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 floor plans, trigger locations, or combination-holder names. A "hidden room" badge is not a verified storage path.
Panic-room booking, quote, 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 safe-room or CAD software without a WordPress.org listing is 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). 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 panic-room quote is a booking you create; a service name such as panic room, safe room, hidden door, combination intake, or site visit is a label you configure. Neither is a documented default. Floor-plan, trigger-locations, combination-holders, homeowner-name, phone, address, install-date, or hidden-door questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked quote is not proof a room was installed, and is not a floor plan. Cancelling or missing the slot later does not erase the floor plan, trigger locations, combination-holder names, or address already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became an install 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. | Install bookings, custom intake fields, and automatic confirmation emails 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. Floor-plan, trigger-locations, combination-holders, homeowner-name, phone, address, install-date, or hidden-door questions are fields you add; they are not documented defaults. A floor-plan file is a file you accept; that file type is not a documented default. A quote request is not proof a room was installed. A floor plan is an upload, not proof a hidden room exists. Trigger locations are stored notes, not a live security system. A combination-holders list is stored names, not proof who can open the door. A hidden-door label is a stored service name, not proof a door is there. 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 quote sits after a request that never became an install is not a documented default of the plugin. | Quote and floor-plan 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 a floor-plan, trigger-locations, or combination-holders field was sent. A page request from this script is not proof anyone booked. The page URL can say panic room even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm panic-room interest next to a stored address and files; this row does not claim an install from that request. | 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. Floor-plan, trigger-locations, combination-holders, homeowner-name, phone, address, install-date, or hidden-door fields often depend on the fields you configure. A quote request is not proof a room was installed. A floor plan is an upload, not proof a hidden room exists. Trigger locations are stored notes, not a live security system. A combination-holders list is stored names, not proof who can open the door. A hidden-door label is a stored service name, not proof a door is there. A marketing-tag page request is not proof anyone booked. The page URL can say panic room even when no form is submitted. The floor plan, the trigger locations, and the combination-holder names can sit after the quote never becomes an install. This page is about a quote form that diagrams the room no one is supposed to know exists, not a storm-shelter weather hiding place, not a valuables-vault delivery booking, and not a staffed-protection quote. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote 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 security-system, safe-room-rating, occupancy, valuables-vault, staffed-protection, or weather-shelter claims. Review stored records, uploaded files, 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-panic-room-plugin-privacy