Timeshare exit plugin privacy

Where does the list of everyone who already fell for it once go?

Everyone in a timeshare-exit WordPress intake has already been sold something they regret once. The form asks which resort, what they paid, the monthly maintenance fee, and how it was pitched — so the exit vendor's form table holds a verified registry of persuadable people with documented assets and a documented wound. The service sells getting out; the intake certifies who already bought in. A marketing tag on the same page can send a page request to a vendor host before anyone submits — and that page request alone can treat timeshare-exit intent as an audience segment from the URL. A page request is not proof anyone booked a strategy call. An exit-consultation intake is not proof an exit closed. 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 intake page, and how long records, files, and backups are kept.

Documentation review only. This is not legal advice, an exit-industry-legitimacy claim, a scam accusation, an FTC or consumer-protection-law claim, a contract-rescission claim, an exit-success or refund-outcome claim, a contract-law 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 intake answers, visitor fields, and page tags go

Entries and bookings handled on your WordPress site

Check which resort-name, purchase-amount, maintenance-fee, or pressure-tactics 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, and backups are kept after a consultation that was cancelled, declined, or never completed. Notification emails can also copy the same client identity and purchase details off-site. Ask your web vendor not to store every regretted purchase next to a client name in one open submissions list when a short case ID would do.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the timeshare-exit intake 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 intake pages if you do not want that page request. A browser scan cannot inspect stored form entries or bookings. A "confidential consultation" badge is not a verified storage path.

Timeshare-exit intake, booking, 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 timeshare SaaS 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 timeshare-exit strategy call is a booking you create; a service name such as exit consultation or strategy call is a label you configure. Neither is a documented default. Resort name, purchase amount, maintenance fee, or pressure-tactics questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. An exit-strategy booking is not proof an exit closed. Cancelling later does not erase the purchase amount or resort name already stored next to a client identity. 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.

Exit-strategy call bookings and custom consultation 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. Resort-name, purchase-amount, maintenance-fee, or pressure-tactics checkbox questions are fields you add; they are not documented defaults. A contract scan or payment-history file is a file you accept; it is not a documented default. One intake entry can store every regretted purchase detail next to a client identity — the post-sale registry is the story. A submitted form is not proof an exit closed. 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 resort name, purchase amount, or maintenance fee was sent. A page request from this script on a timeshare-exit intake page is not proof anyone booked a strategy call — and a pre-consent tag on that page can still treat timeshare-exit intent as an audience segment from the URL alone. The page URL can say timeshare exit even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake 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. Resort names, purchase amounts, maintenance fees, or pressure-tactics answers often depend on the fields you configure. An exit-consultation intake is not proof an exit closed. A marketing-tag page request is not proof anyone booked a strategy call. Abandoning later does not erase the purchase amount already stored next to a resort name. Everyone who appears already bought once. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the intake page, and how long records and backups are kept. A "confidential consultation" 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 exit-industry legitimacy, scam accusations, FTC rules, contract rescission, exit success, or refund outcomes. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake 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-timeshare-exit-plugin-privacy