Roommate matching plugin privacy
The profile that tells a stranger which nights you sleep alone
A roommate profile can record your sleep schedule, lease dates, gender preferences, and which nights you are home alone, then show that row to strangers until one of them gets a key. The deliverable is cohabitation, so the stored data is occupancy, not romance. Sleep-schedule, lease-date, gender-preference, nights-home-alone, occupancy, neighborhood, and address fields are configured, not documented defaults. Optional room photos go in the site uploads folder. A profile is not proof someone lives there. A sleep-schedule field is a stored note, not proof they sleep alone. A nights-home-alone answer is a stored note, not proof the house is empty. A viewing booking is not a lease. A gender-preference field is a stored choice, not a housing decision. A page request is not proof anyone applied. The page URL can say roommate matching 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 profile, search, and viewing pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a fair-housing claim, an occupancy claim, a lease claim, a roommate claim, a dating claim, a background-check 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 roommate profiles, occupancy notes, and page tags go
Profiles and viewing bookings handled on your WordPress site
Check which sleep-schedule, lease-date, gender-preference, nights-home-alone, occupancy, neighborhood, or address fields you enable, who can open form entries and bookings, where uploaded room photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a profile that never became a roommate. Notification emails can also copy the same sleep schedules, nights-home-alone notes, and addresses off-site. One table can name the renter, which nights they are home alone, and the photo of the room next to a name, even when no one moves in. Ask your web vendor not to collect a nights-home-alone answer next to a sleep schedule and address on the first public profile, not to store that occupancy map next to a name in one open submissions list, and to purge unused profiles after the date passes. A privacy-policy page does not by itself limit who can export a profile list or republish an upload. A stored profile is not proof someone lives there.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the roommate-matching profile, search, or viewing page. That page request can reach a vendor host before anyone submits. The page URL can say roommate matching even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off profile, search, and viewing pages if you do not want that page request. A browser scan cannot inspect stored sleep schedules, nights-home-alone notes, or addresses. A "home alone" badge is not a verified storage path.
Roommate-matching profile, viewing, 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 roommate or listing software without a WordPress.org listing is 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). 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 roommate viewing is a booking you create; a service name such as room tour, meet-and-greet, or move-in walkthrough is a label you configure. Neither is a documented default. Sleep-schedule, lease-date, gender-preference, nights-home-alone, occupancy, neighborhood, or address questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked viewing is not proof someone lives there, and is not a lease. Cancelling or missing the slot later does not erase the sleep schedule, nights-home-alone note, or address already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a viewing that never became a roommate 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. | Viewing bookings, custom intake fields, and automatic confirmation emails 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. Sleep-schedule, lease-date, gender-preference, nights-home-alone, occupancy, neighborhood, or address questions are fields you add; they are not documented defaults. A room photo is a file you accept; that file type is not a documented default. A profile is not proof someone lives there. A sleep-schedule field is a stored note, not proof they sleep alone. A nights-home-alone answer is a stored note, not proof the house is empty. A gender-preference field is a stored choice, not a housing decision. 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 profile sits after it never became a roommate is not a documented default of the plugin. | Profile and room-photo entries stored in WordPress; file 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 sleep-schedule, nights-home-alone, or address field was sent. A page request from this script is not proof anyone applied. The page URL can say roommate matching even when no form is submitted. Consent timing has not been tested. Review which tags you enable on profile, search, and viewing pages. Keep marketing tags off those pages if you do not want that page request. A tagged profile page can re-confirm roommate-matching interest next to a stored address and files; this row does not claim a roommate from that request. | 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. Sleep-schedule, lease-date, gender-preference, nights-home-alone, occupancy, neighborhood, or address fields often depend on the fields you configure. A profile is not proof someone lives there. A sleep-schedule field is a stored note, not proof they sleep alone. A nights-home-alone answer is a stored note, not proof the house is empty. A viewing booking is not a lease. A gender-preference field is a stored choice, not a housing decision. A marketing-tag page request is not proof anyone applied. The page URL can say roommate matching even when no form is submitted. The sleep schedule, the nights-home-alone note, and the address can sit after the profile never becomes a roommate. This page is about a roommate profile that stores occupancy, not a matchmaking romance intake, not a tenant-screening landlord application, and not a house-sitting empty-house calendar. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the profile, search, or viewing page, and how long records and backups are kept. A portfolio 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 fair-housing, occupancy, lease, roommate, dating, or background-check claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on profile, search, and viewing pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress membership plugin privacy
- WordPress forms privacy
- WordPress search plugin privacy
- All privacy guides
/wp-roommate-matching-plugin-privacy