Sober living plugin privacy

Where does the application that stores your sobriety date next to the house address go?

A recovery residence runs on anonymity — residents tell neighbors nothing, and some houses deliberately keep the address unlisted. The WordPress application form undoes both at once: sobriety date, substance history, relapse count, probation status, and emergency contact, pinned to the house address in plugin tables. Often a parent types it while placing an adult child. Those answers land in a local-first form or upload plugin before anyone moves in. Decline the application and the referral letter can stay in the uploads folder, an inbox attachment, or a backup. The resident may move out clean; the WordPress database can still hold that row. 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 anyone is in recovery. An application is not an admission. This sample reviews three plugins' documentation. Check which sobriety-date and substance-history fields you collect, who can open entries, where uploads land, which tags load on the application page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a recovery-outcome claim, a licensing assessment, a fair-housing-law 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, uploaded referral letters, email inboxes, staff permissions, vendor accounts, or backups.

Where sobriety dates, substance history, referral letters, and page tags go

Entries and files handled on your WordPress site

Check which sobriety-date, substance-history, relapse-count, probation-status, emergency-contact, or house-address fields you enable, who can open form entries, where uploaded referral letters live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after an application that never became a move-in — including after the resident leaves clean. Notification emails can also copy the same answers and files off-site. Ask your web vendor not to require a full substance narrative or relapse count on the first public application when a short eligibility checklist would do, and not to store the house address next to sobriety details in one open submissions list.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the sober-living application 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 application pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded referral letters. An "anonymous house" badge is not a verified storage path.

Sober-living application, 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 recovery-residence SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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. Referral letters, court papers, or assessment PDFs are files you accept; they are not documented defaults. An uploaded referral letter is not an admission. Decline the application 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_uploadsBrowser 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. Sobriety-date, substance-history, relapse-count, probation-status, emergency-contact, house-address, or contact fields are fields you add; they are not documented defaults. Referral letters, court papers, or assessment PDFs are files you accept; they are not documented defaults. A submitted application is not an admission. Declining the application 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 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 sobriety date, substance history, relapse count, probation status, emergency contact, or house address was sent. A page request from this script on a sober-living application page is not proof that anyone is in recovery — and a pre-consent tag on that page can still treat sober-living shopping intent as an audience segment from the URL alone. The page URL can say sober living even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application 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. Sobriety dates, substance-history free text, relapse counts, probation status, emergency contacts, house addresses, or referral-letter uploads often depend on the fields you configure. An application is not an admission. A marketing-tag page request is not proof that anyone is in recovery. Decline the application and the referral letter can still remain — including after the resident moves out. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. An "anonymous" or "confidential placement" 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 recovery outcomes, licensing, or fair-housing law. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application 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-sober-living-plugin-privacy