Matchmaking plugin privacy
The intake form where membership itself is the secret
Matchmaking and introduction agencies on WordPress can host an intake that receives the most personally revealing form a small business ever collects — relationship status, divorce history, religion, income bracket, what you are looking for, and profile photos — filled in by someone who does not want anyone to know they filled it in. Membership in the service is the secret. A remarketing pixel on that intake page can fire before consent and treat matchmaking-intent traffic as an audience segment from the page URL alone. This sample reviews three plugins' documentation. Check which profile and preference fields you collect, who can open submissions, where temporary uploads and tags store or send that data, and how long intake rows, photos, and backups are kept after membership ends.
Documentation review only. This is not legal advice, not a dating-safety or background-check guide, not a compatibility or success-rate claim, not an outing claim, and not a GDPR or other compliance assessment. Consumer dating apps and platforms are outside this WordPress-hosted agency sample.
Scan your matchmaking intake page for third-party requestsThe scan checks browser requests on the pages it visits. It cannot inspect form entries, uploaded photos, email inboxes, staff permissions, vendor accounts, or backups.
Where profile photos, intake answers, and intake-page tags are stored
Files and form entries handled on your WordPress site
Check which relationship-status, divorce-history, religion, income, preference, photo-upload, or contact fields you enable, who can open entries, which uploads you accept, where temporary uploads live, which inboxes receive attachments, and how long records, photos, and backups are kept after membership ends. Notification emails can also copy intake answers off-site. Those answers next to a name and email in the contact-form database are a membership secret on a marketing site.
Marketing tags on the matchmaking intake page
Some tools load a marketing pixel or tag on the same page as the matchmaking intake form. A page request can fire before anyone submits a preference answer — and membership itself is the secret that page URL can reveal as a visit. A tag seeing a page request is evidence of a visit, not proof of orientation, religion, or membership tier. Review which tags you enable, which consent filters you use, and what those platforms retain. A browser scan cannot inspect stored form entries or uploaded photos.
Matchmaking intake 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 matchmaking SaaS tools without a WordPress.org listing are outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). The free-version listing states uploaded files move to a temporary folder under /wp-content/uploads/wp_dndcf7_uploads, attach to mail, then are removed from that temporary folder after submission — the same pattern Contact Form 7 documents for its default file field. That cleanup does not remove copies already sent as email attachments. Which profile photos, ID scans, or other intake files you accept depends on the fields you add; they are not fixed matchmaking defaults. Filenames chosen by visitors can include full legal names. Pro documents Media Library storage, custom upload folders, auto-delete timers, and remote storage options. Public form-page browser hosts are unverified. | Uploaded files attached to email; temporary copies under wp-content/uploads | Browser hosts not verified | Not assessed | Not tested |
| |
| Formidable Forms Documented self-hosted form builder (plugin version 6.35). The listing states every form submission is stored in the WordPress database, with back-end entry access, CSV export, and email notifications or autoresponders you configure. Relationship-status, divorce-history, religion, income-bracket, preference, or contact fields depend on the fields you add — they are not fixed matchmaking defaults. An intake form that stores those answers next to a name and email is a membership secret parked in the same contact-form database as ordinary lead capture. Optional payment, CRM, or spam-protection integrations send data only when enabled. Retention of entry rows after membership ends is not specified as a default purge. Public form browser hosts are unverified. | Matchmaking intake form entries stored in your WordPress database | 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, OpenAI Pixel, 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 relationship answer or photo was sent. A page request from this script on a matchmaking intake page is evidence of a visit — not proof of orientation, religion, membership tier, or that a profile was completed. A pre-consent tag on that page can still treat matchmaking-intent traffic as an audience segment. The listing describes consent-plugin filters; that is not a legal-compliance assessment. Consent timing has not been tested. Review which tags you enable on intake and photo-upload 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. Relationship-status, religion, income, preference, or photo-upload fields often depend on the fields you configure. An intake form is not a dating app, not a compatibility score, and not a background check. A marketing-tag page request is evidence of a visit — not proof of orientation, religion, membership tier, or that a photo was uploaded. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess dating-safety products, background-check services, compatibility outcomes, outing claims, GDPR, or other compliance status. Ask your web vendor where entries and uploads live, whether post-membership intake rows purge, whether portal links expire, whether marketing pixels stay off intake pages, whether profile photos stay off the first contact form, and whether “secure intake” badges match the storage path you can verify. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
Scan your matchmaking intake page for third-party requests/wp-matchmaking-plugin-privacy