Needle exchange plugin privacy

Where does the signup form at the program that promised anonymity go?

A syringe-service program's founding premise is that nobody writes your name down — then the outreach site's WordPress appointment or signup form stores name, phone, ZIP, what-do-you-use, and how-often in plugin tables. In places where paraphernalia possession is criminalized, the row sits next to a confession; a naloxone-training signup names the person expected to witness an overdose; a parent books for an adult child and becomes a second data subject; no-show and declined rows persist like everything else. Those answers sit in a local-first booking or form plugin behind one admin login. A marketing tag on the same signup page can send a page request to a vendor host before anyone submits — and that page request alone can treat harm-reduction intent as an audience segment from the URL. A page request is not proof anyone uses drugs. A signup is not program enrollment. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the signup page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, a paraphernalia-law claim, a Good-Samaritan-law claim, a program-legality-by-state claim, a public-health-outcome 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 signup answers, visitor fields, and page tags go

Entries and bookings handled on your WordPress site

Check which name, phone, ZIP, what-do-you-use, how-often, or naloxone-training fields you enable, who can open form entries and exchange-slot bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a visit that was completed, declined, or never attended. Notification emails can also copy the same visitor identity and substance answers off-site. Ask your web vendor not to store a what-do-you-use confession next to a name in one open submissions list when a short visit ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the needle-exchange signup 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 signup pages if you do not want that page request. A browser scan cannot inspect stored form entries or uploaded files. An "anonymous" or "no ID required" badge is not a verified storage path.

Needle-exchange signup, intake, 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 needle-exchange or naloxone-training booking is a booking you create; a service name such as syringe exchange or overdose-prevention training is a label you configure. Neither is a documented default. Name, phone, ZIP, what-do-you-use, how-often, or naloxone-training questions are custom fields you add (textarea, select, or input); they are not documented defaults. A signup booking is not program enrollment. Declining or missing a visit later does not erase the what-do-you-use answer already stored next to a name. 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.

Exchange-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. Name, phone, ZIP, what-do-you-use, how-often, or naloxone-training questions are fields you add; they are not documented defaults. ID or referral uploads are files you accept; they are not documented defaults. One signup entry can store a visitor name next to a what-do-you-use confession, or a parent name next to an adult child they booked for. A submitted form is not program enrollment. 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 visitor name, what-do-you-use answer, or naloxone-training signup was sent. A page request from this script on a needle-exchange signup page is not proof anyone uses drugs — and a pre-consent tag on that page can still treat harm-reduction intent as an audience segment from the URL alone. The page URL can say needle exchange even when no form is submitted. Consent timing has not been tested. Review which tags you enable on signup 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. Visitor names, phone numbers, ZIP codes, what-do-you-use answers, how-often answers, or naloxone-training signups often depend on the fields you configure. A signup is not program enrollment. A marketing-tag page request is not proof anyone uses drugs. Declining or missing a visit later does not erase the what-do-you-use answer already stored next to a name. Writing the name down at all breaks the anonymity premise the program advertised. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the signup page, and how long records and backups are kept. An "anonymous" or "no ID required" 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 paraphernalia law, Good-Samaritan law, program legality by state, or public-health outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on signup 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-needle-exchange-plugin-privacy