Domestic violence shelter plugin privacy

Where does the contact form at the address that is not supposed to exist go?

A shelter's security model is that nobody can find it — then the outreach site's WordPress contact form stores survivor name, children's names and ages, the abuser's name, "is it safe to call this number", and a what-happened narrative in a local-first booking or form plugin behind one admin login. Retention here is a location risk, not an embarrassment risk: a leaked backup or a shared-computer autofill does not leak a secret, it leaks coordinates. The abuser is a second data subject who is also the one reader the row must never reach. A marketing tag on the same confidential-location page can send a page request to a vendor host before anyone submits — and that page request alone can treat shelter-seeking intent as an audience segment from the URL. A page request is not proof that anyone is in danger. A submitted form is not an intake or a bed assignment. This sample reviews three plugins' documentation. Check which survivor and abuser fields you collect, who can open entries, where uploaded files land, which tags load on the contact page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a VAWA claim, an address-confidentiality-program-law claim, a mandated-reporting assessment, a shelter-security-procedure claim, a custody 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 contact answers, abuser fields, and page tags go

Entries and bookings handled on your WordPress site

Check which survivor-name, children's-names, abuser-name, safe-to-call, or what-happened fields you enable, who can open form entries and intake-slot bookings, where uploaded protective orders or ID scans live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a contact that was answered or never followed up. Notification emails can also copy the same survivor identity and abuser name off-site. Ask your web vendor not to store an abuser name next to a survivor phone number in one open submissions list when a short contact ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the domestic-violence shelter contact page. That page request can reach a vendor host before anyone submits. On a confidential-location URL, that is the premise leak: the site existing in a vendor audience log is the location risk. Review which tags you enable, account access, and retention there. Keep marketing tags off contact pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. A "confidential" or "safe location" badge is not a verified storage path.

Domestic-violence shelter contact, intake-slot, 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. Case-management CRM platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A confidential intake-slot or advocate callback booking is a booking you create; a service name such as shelter intake or crisis callback is a label you configure. Neither is a documented default. Survivor-name, children's-names, abuser-name, safe-to-call, or what-happened questions are custom fields you add (textarea, select, or input); they are not documented defaults. A contact booking is not an intake or a bed assignment. Leaving the shelter later does not erase the abuser name already stored next to a survivor phone number. Emails can include those custom fields. 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.

Contact or intake-slot bookings and custom intake fields stored 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. Survivor-name, children's-names, abuser-name, safe-to-call, or what-happened questions are fields you add; they are not documented defaults. Protective-order, ID, or incident-photo uploads are files you accept; they are not documented defaults. One contact entry can store a survivor name and children's ages next to an abuser name and a safe-to-call flag. A submitted form is not an intake or a bed assignment. 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.

Form 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 survivor name, abuser name, or safe-to-call flag was sent. A page request from this script on a domestic-violence shelter contact page is not proof that anyone is in danger — and a pre-consent tag on that confidential-location page can still treat shelter-seeking intent as an audience segment from the URL alone. The page URL can say shelter or domestic violence even when no form is submitted. That is the premise leak for this vertical: the marketing tag records that someone visited the address that is not supposed to exist. Consent timing has not been tested. Review which tags you enable on contact pages.

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. Survivor names, children's names, abuser names, safe-to-call flags, or what-happened narratives often depend on the fields you configure. A submitted form is not an intake or a bed assignment. A marketing-tag page request is not proof that anyone is in danger. Leaving the shelter later does not erase the abuser name already stored next to a survivor phone number. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the contact page, and how long records and backups are kept. A "confidential" or "safe location" 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 VAWA, address-confidentiality-program law, mandated reporting, shelter security procedures, or custody outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on contact pages, and backups.

Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-domestic-violence-shelter-plugin-privacy