Storm shelter plugin privacy

The install quote that maps where your family hides and how many of you fit

A shelter quote can be a map of the hiding place. GPS pin of the install spot. Occupancy count. Whether it sits below the garage slab or in the master closet. Photos of the access route through the house. The one document that should never leave the household, where everyone goes when something is wrong, can sit in a form plugin entries table next to a marketing consent checkbox. GPS-pin, install-spot, occupancy-count, location-type, below-slab, master-closet, access-route-photo, and address fields are configured, not documented defaults. Optional access-route photos go in the site uploads folder. A quote request is not proof a shelter was installed. A GPS pin is a stored location, not proof a shelter is there. An occupancy count is a stored number, not proof how many people live there. An access-route photo is an upload, not a floor plan of a hiding place that exists. A location-type answer is a stored note, not proof the room is a rated safe room. A page request is not proof anyone booked. The page URL can say storm shelter 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 FEMA claim, an ICC-500 claim, a safe-room claim, a tornado claim, a building-code claim, an occupancy claim, a survival claim, a shelter-rating 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 shelter quotes, occupancy notes, and page tags go

Install quotes and forms handled on your WordPress site

Check which GPS-pin, install-spot, occupancy-count, location-type, below-slab, master-closet, access-route-photo, or address fields you enable, who can open form entries and bookings, where uploaded access-route photos 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 occupancy counts, GPS pins, photos, and addresses off-site. One table can name the house, how many people fit, and the photo of the hallway next to a name, even when the install never happens. Ask your web vendor not to collect an occupancy count next to a GPS pin and access-route photo on the first public form, not to store that hiding-place map 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 shelter was installed.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the storm-shelter booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say storm shelter 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 occupancy counts, GPS pins, or access-route photos. A "hiding place" badge is not a verified storage path.

Storm-shelter 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 shelter or CAD 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 shelter quote is a booking you create; a service name such as tornado shelter, safe room, below-slab, in-closet, or site visit is a label you configure. Neither is a documented default. GPS-pin, install-spot, occupancy-count, location-type, below-slab, master-closet, access-route-photo, or address questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked quote is not proof a shelter was installed, and is not a floor plan. Cancelling or missing the slot later does not erase the occupancy count, GPS pin, access-route photo, 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 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. GPS-pin, install-spot, occupancy-count, location-type, below-slab, master-closet, access-route-photo, or address questions are fields you add; they are not documented defaults. An access-route photo is a file you accept; that file type is not a documented default. A quote request is not proof a shelter was installed. A GPS pin is a stored location, not proof a shelter is there. An occupancy count is a stored number, not proof how many people live there. An access-route photo is an upload, not a floor plan of a hiding place that exists. A location-type answer is a stored note, not proof the room is a rated safe room. 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 access-route 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 GPS-pin, occupancy-count, or access-route-photo field was sent. A page request from this script is not proof anyone booked. The page URL can say storm shelter 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 storm-shelter 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 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. GPS-pin, install-spot, occupancy-count, location-type, below-slab, master-closet, access-route-photo, or address fields often depend on the fields you configure. A quote request is not proof a shelter was installed. A GPS pin is a stored location, not proof a shelter is there. An occupancy count is a stored number, not proof how many people live there. An access-route photo is an upload, not a floor plan of a hiding place that exists. A location-type answer is a stored note, not proof the room is a rated safe room. A marketing-tag page request is not proof anyone booked. The page URL can say storm shelter even when no form is submitted. The occupancy count, the pin, and the access-route photo can sit after the quote never becomes an install. This page is about an install quote that maps where the family hides and how many of them fit, not a generator-installation outage register, not a foundation-repair crack photo, and not a security-guard 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 FEMA, ICC-500, safe-room, tornado, building-code, occupancy, survival, or shelter-rating 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

Scan your site for third-party requests

/wp-storm-shelter-plugin-privacy