Coworking space plugin privacy
The day-pass signup whose door log knows your hours better than your landlord
A coworking space's membership page can look like a contact form and a desk booking. The same form often asks name and phone, home address, guest names, optional virtual-office mail-forwarding lines that map a business address back to an apartment, an emergency contact, and a desk or door sign-in time, and stores those answers next to a name for the life of the form table. Those fields are configured, not documented defaults. Before anyone takes a hot desk, the day-pass signup asks where you live. The door and desk sign-in log timestamps when you arrive and leave. A guest name sits in the same row as your address. A mail-forwarding line for a virtual office can map a business suite back to someone's apartment. A desk booking is a calendar row, not proof someone works there full-time. A day-pass answer is the applicant's disclosure, not a verified employment record. A mail-forwarding address is what the applicant typed, not proof of residency. A sign-in timestamp is a visit log, not proof of absence from home. A page request is not proof anyone coworks anywhere. The page URL can say coworking space even when no form is submitted. Ask what happens to the home-address answer and the door log after the day pass ends — the day-pass signup whose door log knows your hours better than your landlord outlives the first visit. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the day-pass page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an employment or tenancy or residency or identity 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 desk bookings, day-pass intakes, and page tags go
Day passes and sign-ins on your WordPress site
Check which day-pass, membership, guest-sign-in, desk-booking, door-access, mail-forwarding, home-address, or emergency-contact fields you enable, who can open form entries and desk bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a booking closes — when the day-pass signup is a door log that knows your hours better than your landlord. Notification emails can also copy those fields off-site. One table can list every home address a member typed next to a desk slot and a guest name. Ask your web vendor not to keep sign-in timestamps next to home addresses and mail-forwarding apartment lines in one open submissions list longer than operations need, and to purge booking rows when the day pass is declined or closed. A privacy-policy page does not by itself limit who can open a submissions list. A stored desk booking is not proof someone works there full-time. A sign-in timestamp is not proof of absence from home.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the coworking day-pass page. That page request can reach a vendor host before anyone submits. The page URL can say coworking space even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off day-pass and membership pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "verified member" badge is not a verified storage path.
Desk booking, day-pass 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 coworking CRM SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A desk or day-pass sign-in booking is a booking you create; a service name such as hot desk, day pass, meeting room, or virtual-office mail pickup is a label you configure. Neither is a documented default. Home-address, mail-forwarding, guest-name, door-access, or membership questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof someone works there full-time — and a CSV export of desk slots next to a home address, a guest name, and a dated sign-in is still a booking row after someone asked for a day pass. Emails can include those custom fields and copy the appointment off-site. 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. | Desk and day-pass sign-in bookings stored 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. Home-address, mail-forwarding, guest-name, door-access, or membership questions are fields you add; they are not documented defaults. Completing the form can store a day-pass answer next to a home address, a guest name, a virtual-office mail-forwarding apartment line, an emergency contact, and optional ID or agreement-file uploads — typed once by a member into the same tables as a newsletter signup. A desk booking is a calendar row, not proof someone works there full-time. A day-pass answer is the applicant's disclosure, not a verified employment record. A mail-forwarding address is what the applicant typed, not proof of residency. A sign-in timestamp is a visit log, not proof of absence from home. An uploaded agreement is a client document in uploads/forminator, not a lease. A staff login can open the home-address answer next to Tuesday's 10am hot-desk slot. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified. | Day-pass and membership entries stored in WordPress; optional ID or agreement 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 day-pass, membership, guest-sign-in, mail-forwarding, home-address, or door-access field was sent. A page request from this script is not proof anyone coworks anywhere. The page URL can say coworking space even when no form is submitted. Consent timing has not been tested. Review which tags you enable on day-pass and membership 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. Day-pass, membership, guest-sign-in, desk-booking, door-access, mail-forwarding, home-address, or emergency-contact fields often depend on the fields you configure. A desk booking is a calendar row, not proof someone works there full-time. A day-pass answer is the applicant's disclosure, not a verified employment record. A mail-forwarding address is what the applicant typed, not proof of residency. A sign-in timestamp is a visit log, not proof of absence from home. A marketing-tag page request is not proof anyone coworks anywhere. The page URL can say coworking space even when no form is submitted. The day-pass signup whose door log knows your hours better than your landlord — that is a storage path next to names and phones, not a feature these plugins claim. This page is about that recurring day-pass and visit-log intake, not a security-guard license form or an alarm-company site brief. Ask your web vendor who can open entries, whether a marketing tag loads on the day-pass page, and how long records and backups are kept. A "verified member" 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 employment, tenancy, residency, or identity. Review stored records, bookings, connected services, exports, notification emails, marketing tags on day-pass pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress membership plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-coworking-space-plugin-privacy