Cuddle therapy plugin privacy

The intake that writes down why nobody touches you

A cuddle-therapy screening intake can store touch boundaries, what is off-limits and why, and a bereavement or divorce reason next to a name before any professional relationship exists. The answers themselves, stored in plain text in a form plugin, can say why the client wants to be held. Recurring bookings with timestamps can sit in an appointments list any staffer can open, a loneliness ledger of who keeps coming back. Unlike clinical notes locked in a therapy practice, those rows sit in the same WordPress database as newsletter signups. A no-show or cancellation can stay on the calendar after the client could not face another person. Touch-boundaries, off-limits-and-why, bereavement-or-divorce-reason, client-name, session-type, and phone fields are configured, not documented defaults. A touch-boundaries answer is a stored preference, not proof of trauma. A bereavement or divorce reason is a stored booking reason, not proof anyone died or divorced. A session type labeled cuddle therapy is a stored service name, not proof anyone was held. A missed slot is not proof anyone could not face another person. A cuddle-therapy booking is not proof anyone is lonely. A page request is not proof anyone booked a session. The page URL can say cuddle therapy even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on booking and intake pages, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a clinical-therapy claim, a massage claim, a matchmaking claim, a crisis-line claim, a HIPAA 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 cuddle-therapy bookings, screening answers, and page tags go

Cuddle-therapy bookings and forms handled on your WordPress site

Check which touch-boundaries, off-limits-and-why, bereavement-or-divorce-reason, client-name, session-type, or phone fields you enable, who can open form entries and bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a slot is missed. Notification emails can also copy the same touch boundaries, off-limits answers, bereavement or divorce reasons, names, session types, and phone numbers off-site. One table can name a touch-boundaries answer, a bereavement or divorce reason, and a client name next to a session type, even when no session is held. The appointments list can show who is booked this week and how often they return. Ask your web vendor not to collect a bereavement or divorce reason next to a name and a touch-boundaries answer on the first public form, not to store those answers next to a session type in one open submissions list, and to purge unused pairings after the slot passes. A privacy-policy page does not by itself limit who can export an intake list. A stored bereavement or divorce reason is not proof anyone died or divorced.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the cuddle-therapy booking or intake page. That page request can reach a vendor host before anyone submits. The page URL can say cuddle therapy even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and intake pages if you do not want that page request. A browser scan cannot inspect stored touch-boundaries answers or bereavement or divorce reasons. A "certified professional cuddler" badge is not a verified storage path.

Cuddle-therapy booking, 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 professional-cuddling or platonic-touch SaaS tools 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). 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 cuddle-therapy appointment is a booking you create; a service name such as professional cuddle, platonic touch, or intake session is a label you configure. Neither is a documented default. The stored service name can say cuddle therapy in plain text before anyone is held. Touch-boundaries, off-limits-and-why, bereavement-or-divorce-reason, client-name, session-type, or phone questions are custom fields you add (textarea, select, or input); they are not documented defaults. A touch-boundaries answer is a stored preference, not proof of trauma. A bereavement or divorce reason is a stored booking reason, not proof anyone died or divorced. A session type labeled cuddle therapy is a stored service name, not proof anyone was held. A booked slot is not proof anyone is lonely, and is not proof a session was held. Cancelling or missing the slot later does not erase the touch-boundaries answer, bereavement or divorce reason, or name already stored next to a session type, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never produced a session is not a documented default of the plugin. The appointments list can show who is booked this week and how often they return. 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.

Cuddle-therapy bookings, custom screening 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. Touch-boundaries, off-limits-and-why, bereavement-or-divorce-reason, client-name, session-type, or phone questions are fields you add; they are not documented defaults. Waiver PDFs and ID photos are files you accept; those file types are not documented defaults. A touch-boundaries answer is a stored preference, not proof of trauma. A bereavement or divorce reason is a stored booking reason, not proof anyone died or divorced. A session type labeled cuddle therapy is a stored service name, not proof anyone was held. A cuddle-therapy booking is not proof anyone is lonely. 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 a pairing sits after a slot is missed is not a documented default of the plugin.

Cuddle-therapy screening 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 touch-boundaries, bereavement-or-divorce-reason, or client-name field was sent. A page request from this script on a cuddle-therapy intake page is not proof anyone booked a session, and a pre-consent tag on that page can still treat cuddle-therapy interest as an audience segment from the URL alone. The page URL can say cuddle therapy even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake pages. Keep marketing tags off those pages if you do not want that page request. A tagged intake page can re-confirm cuddle-therapy interest next to a stored screening answer; this row does not claim a session was held 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. Touch-boundaries, off-limits-and-why, bereavement-or-divorce-reason, client-name, session-type, or phone fields often depend on the fields you configure. A touch-boundaries answer is a stored preference, not proof of trauma. A bereavement or divorce reason is a stored booking reason, not proof anyone died or divorced. A session type labeled cuddle therapy is a stored service name, not proof anyone was held. A missed slot is not proof anyone could not face another person. A cuddle-therapy booking is not proof anyone is lonely. A marketing-tag page request is not proof anyone booked a session. The page URL can say cuddle therapy even when no form is submitted. The touch-boundaries answer, the bereavement or divorce reason, and the name can sit after a slot is missed. This page is about a screening intake that writes down why someone wants to be held, not a massage health intake, not clinical talk-therapy notes, not a matchmaking membership, not a sober-companion hours-alone calendar, and not a crisis-line page visit. Ask your web vendor who can open entries, whether a marketing tag loads on the booking or intake page, and how long records and backups are kept. A "certified professional cuddler" 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 clinical, HIPAA, massage, matchmaking, or crisis claims. Review stored records, connected services, exports, notification emails, marketing tags on booking and intake pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-cuddle-therapy-plugin-privacy