Medical marijuana card plugin privacy
The qualifying-condition form that is legal in one table and disqualifying on the federal one
A medical-marijuana-card intake can look like a booking and a contact form. The same form often asks qualifying condition, current medications, prior cannabis use, and a physician-recommendation or state-ID upload — and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. One row can be legal in a state patient table while the same fact is disqualifying on a federal firearms form, a CDL screen, or an employer drug test — and it can sit in WordPress before any doctor signs anything. An appointment request is not a certification. A qualifying-condition answer is the client's account, not a medical record. An uploaded recommendation letter is a client document, not a signed physician order. A page request is not proof anyone applied for a card. The page URL can say medical marijuana card even when no form is submitted. Ask what happens to the condition field and the ID upload after the visit — the card changes what you may buy, drive, and carry, and the row outlives the appointment. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a cannabis-law claim, a federal-controlled-substance claim, a firearms-eligibility claim, an employment-law claim, a DOT or CDL-regulation claim, a medical-efficacy claim, or a 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where certifications, qualifying-condition intakes, and page tags go
Intakes and bookings on your WordPress site
Check which qualifying-condition, medication, prior-use, physician-recommendation, or state-ID fields you enable, who can open form entries and certification bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the same row is legal in one jurisdiction table and disqualifying in another. Notification emails can also copy those fields off-site. One table can list every person who typed a qualifying condition. Ask your web vendor not to keep ID scans next to condition answers in one open submissions list longer than operations need, and to purge intake rows when the visit is closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored appointment is not a certification. An uploaded recommendation letter is not a signed physician order.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the medical-marijuana-card intake page. That page request can reach a vendor host before anyone submits. The page URL can say medical marijuana card even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and booking pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "confidential patient intake" badge is not a verified storage path.
Certification, qualifying-condition 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. Specialty cannabis-card or telehealth SaaS platforms without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| 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 certification or evaluation booking is a booking you create; a service name such as medical marijuana card evaluation is a label you configure. Neither is a documented default. Qualifying-condition, current-medication, or prior-use questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not a certification — and a CSV export of visits next to qualifying-condition answers is still a name-keyed legal-status-split row. Emails can include those custom fields and copy the appointment off-site. 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. | Medical-marijuana-card certification bookings stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| 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. Qualifying-condition, current-medication, prior-use, physician-recommendation, or state-ID questions are fields you add; they are not documented defaults. Completing the form can store a condition that earns a state card next to an ID scan and a recommendation letter — and the same row can be disqualifying on a federal form. A submitted appointment request is not a certification. A qualifying-condition answer is the client's account, not a medical record. An uploaded recommendation letter is a client document, not a signed physician order — and a state ID next to a condition field can sit in the same row as a name and address. A staff login can open the ID next to the condition answer. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Qualifying-condition intake entries stored in WordPress; optional state-ID and physician-recommendation uploads in the site uploads/forminator folder | 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, 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 qualifying-condition, medication, prior-use, or ID field was sent. A page request from this script is not proof anyone applied for a card. The page URL can say medical marijuana card even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake and booking 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. Qualifying-condition, medication, prior-use, physician-recommendation, or state-ID fields often depend on the fields you configure. An appointment request is not a certification. A qualifying-condition answer is the client's account, not a medical record. An uploaded recommendation letter is a client document, not a signed physician order. A marketing-tag page request is not proof anyone applied for a card. The page URL can say medical marijuana card even when no form is submitted. The same row can be legal in one table and disqualifying on another — that is a storage path next to a name, not a feature these plugins claim. This page is about that legal-status-split intake, not a ketamine eligibility form, an addiction-treatment intake, a sleep-clinic form, a weight-loss intake, an age-verification gate, or a sexual-health clinic form. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "confidential patient intake" 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 cannabis law, federal controlled-substance rules, firearms eligibility, employment law, DOT or CDL regulation, or medical efficacy. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-medical-marijuana-card-plugin-privacy