Addiction-treatment plugin privacy
Where are addiction-treatment inquiry answers and insurance files stored?
Admissions and verify-insurance forms can collect a substance name, insurance identifiers, and file uploads before anyone is admitted. Marketing tags on those pages can also send a page request to a vendor host. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where uploaded files land, which tags load on the inquiry page, and how long entries, files, and backups are kept.
Documentation review only. This is not legal or clinical advice, or a HIPAA, 42 CFR Part 2, 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 files, email inboxes, staff permissions, vendor accounts, or backups.
Where inquiry answers, files, and page tags go
Answers and files handled on your WordPress site
Check which inquiry or file fields you enable, who can open entries, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept. Notification emails can also copy the same answers off-site.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the admissions or verify-insurance page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. A browser scan cannot inspect stored form entries.
Addiction-treatment inquiry, file-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 EHR tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Everest Forms – Contact Form, Payment Form, Quiz, Survey & Custom Form Builder with AI Documented self-hosted form builder (plugin version 3.6.2). The listing states unlimited entry storage in the WordPress database, with admin view, search, export, and delete. File uploads and image uploads are included in the free version. Version 3.6.2 class-evf-form-fields-upload.php stores files under wp-content/uploads/everest_forms_uploads, with a temporary folder at everest_forms_uploads/tmp. Substance, insurance, or verify-insurance questions are fields you add; they are not documented defaults. Notification emails can copy field values to any recipients you set. Optional Stripe, PayPal, reCAPTCHA, and CRM add-ons send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in your WordPress database; file uploads in the site uploads folder | Browser hosts not verified | Not assessed | Not tested |
| |
| weForms – Easy Drag & Drop Contact Form Builder For WordPress Documented self-hosted form builder (plugin version 1.6.28). Submissions are stored in WordPress (weforms_entries and weforms_entrymeta) and can be viewed, exported as CSV, and deleted from the dashboard. The free Image Upload field uses wp_handle_upload and wp_insert_attachment in class-ajax-upload.php, so files land in the default site uploads directory and the Media Library. A general file-upload field is listed as a Pro module. Substance, insurance, or verify-insurance questions are fields you add; they are not documented defaults. Email notifications can copy field values off-site. Optional reCAPTCHA, Slack, and Pro CRM or email-marketing integrations send data only when you enable them. Public form-page browser hosts are unverified. | Form entries stored in your WordPress database; image uploads added to the Media Library | 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, OpenAI Pixel, 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 named substance was sent. A page request from this script is not proof that an admissions answer was collected. The listing describes consent-plugin filters and a Meta setting to disable event parameters that can track protected health information; neither is a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on admissions and verify-insurance 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. Substance names, insurance identifiers, or verify-insurance notes often depend on the fields you configure. An inquiry form is not a medical record. A marketing-tag page request is not proof that a named substance was collected. Camera metadata and unlisted media URLs are described only when a plugin documents them. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess HIPAA, 42 CFR Part 2, or other legal status. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on admissions pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress rehab plugin privacy
- WordPress therapy plugin privacy
- WordPress file-upload plugin privacy
- All privacy guides
/wp-addiction-treatment-plugin-privacy