Psychic medium plugin privacy

The reading request that lists your dead and what you regret

A psychic or medium booking form can look like a date and a first name. It is also the reading. Before any session happens, the form asks who you lost and when, what you want to ask them, and what is still unresolved. Loss-details, question-list, deceased-photo, and relationship fields are configured, not documented defaults. Those answers are grief and guilt typed by the only person who will ever source them. Named dead people and living relatives never consented to the row. The question list is already the confession. It sits next to a name, an email, and a marketing pixel, and it can outlive the appointment. A booking is not proof a reading happened. An intake answer is a client's framing, not a fact about the living or the dead people it names. A page request is not proof anyone sought a reading. The page URL can say psychic or medium even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and uploads, which tags load on reading and intake pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a psychic-efficacy claim, a consumer-protection or fraud-law claim, a religious-exemption claim, a grief-counseling-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 reading bookings, question lists, and page tags go

Reading bookings and intakes handled on your WordPress site

Check which loss-details, question-list, deceased-photo, or relationship fields you enable, who can open form entries and bookings, where uploaded files live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a booking that never became a session. Notification emails can also copy the same question list off-site. One table can name the dead next to what the living still regret, even when only the client typed. Ask your web vendor not to collect a question list or a deceased photo on the first public form, not to store that grief next to a name in one open submissions list, and to purge unused bookings after the date passes. A privacy-policy page does not by itself limit who can export an intake list. A stored booking is not proof a reading happened.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the psychic-medium reading or intake page. That page request can reach a vendor host before anyone submits. The page URL can say psychic or medium even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off reading and intake pages if you do not want that page request. A browser scan cannot inspect stored question lists. A "private reading" badge is not a verified storage path.

Psychic-medium reading, 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 medium-practice or seance software without a WordPress.org listing is 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). The listing documents automatic email notifications: customers get instant booking confirmations; staff get notified; templates can include booking information and custom fields; customers can confirm or cancel via a link in the email. WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A reading session is a booking you create; a service name such as medium reading or grief-question intake is a label you configure. Neither is a documented default. Loss-details, question-list, or relationship questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked reading is not proof a session happened and is not a fact about anyone named in the intake. Cancelling or missing the session later does not erase the contact answers already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a session is not a documented default of the plugin. 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.

Reading-session bookings, custom intake fields, and automatic confirmation emails 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. Loss-details, question-list, deceased-photo, or relationship questions are fields you add; they are not documented defaults. A photo of the deceased, a handwritten letter, or a family snapshot is a file you accept; none of those file types is a documented default. A booking is not proof a reading happened. An intake answer is a client's framing, not a fact about the living or the dead people it names. 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. How long an intake sits after a request that never became a session is not a documented default of the plugin.

Intake and question-list 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 loss-details, question-list, deceased-photo, or relationship field was sent. A page request from this script is not proof anyone sought a reading. The page URL can say psychic or medium even when no form is submitted. Consent timing has not been tested. Review which tags you enable on reading and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged reading page can re-confirm interest next to a stored question list; this row does not claim a session outcome from that request.

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. Loss-details, question-list, deceased-photo, or relationship fields often depend on the fields you configure. A booking is not proof a reading happened. An intake answer is a client's framing, not a fact about the living or the dead people it names. A marketing-tag page request is not proof anyone sought a reading. The page URL can say psychic or medium even when no form is submitted. The question list can sit after the appointment ends. This page is about a reading request that stores grief as typed fields, not a funeral condolence book, a cemetery-plot pre-need lead, a genealogy research intake, or a crisis-line page visit. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the reading or intake page, and how long records and backups are kept. A "private" or "confidential reading" 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 psychic efficacy, consumer-protection or fraud law, religious exemption, or grief-counseling outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on reading and intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-psychic-medium-plugin-privacy