Elevator service plugin privacy
The maintenance log that records every entrapment
An elevator-service WordPress stack is not only a job calendar. It is often a maintenance log in disguise. Service tickets can name who got stuck, when, and for how long. The contract portal can hold the building's violation history and traffic patterns: which floors, what hours. A repair request is a diary of a building's worst days with tenants' names attached. A page request is not proof anyone booked. An entrapment note is stored text, not proof anyone was trapped. A violation PDF is a stored file, not a citation. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where logs land, which inboxes receive copies, and how long past tickets, files, and backups are kept.
Documentation review only. This is not legal advice, a safety claim, an inspection claim, an ADA claim, a GDPR or other compliance assessment, or a judgment about elevator mechanics.
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 entrapment names, violation files, and elevator bookings go
Entries, bookings, and uploads on your WordPress site
Check which entrapment-name, duration, floor, traffic-hours, violation-history, tenant-name, building-address, owner-name, phone, email, or appointment-date fields you enable, who can open form entries and service bookings, where uploaded cab photos and violation files live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a call that never happened. Notification emails can also copy the same tenant names, floors, and file links off-site.
Uploads or connected destinations off your WordPress site
Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who opened the service calendar. A licensed-elevator badge is not a verified storage path.
Elevator booking, entrapment-log, and violation-file 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 elevator-service 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 window such as "car 2, 14th floor, 7:40am, 18 minutes" is a booking you create; a service name such as elevator service is a label you configure. Neither is a documented default. Entrapment-name, duration, floor, traffic-hours, violation-history, or tenant-name questions are custom fields you add (textarea, select, input, checkbox, or file); they are not documented defaults. A booking is a calendar row, not proof of work - and a CSV export of "tenant name + 14th floor + 18 minutes stuck" next to a named owner is still a calendar that answers when the crew is expected. 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. | Elevator service 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. Entrapment-name, duration, floor, traffic-hours, violation-history, tenant-name, building-address, owner-name, phone, email, or appointment-date questions are fields you add; they are not documented defaults. Optional cab photo uploads are files you accept; that file type is not a documented default. An entrapment note is stored text, not proof anyone was trapped. A violation PDF is a stored file, not a citation. An elevator form is not proof anyone serviced the car. 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 cab photo sits after a call that never happened is not a documented default of the plugin. | Maintenance-log answers stored in WordPress; optional cab-photo and violation-file uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A cab photo or violation PDF is a file you accept; that file type is not a documented default. An uploaded cab photo is a stored file, not proof of the work. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long a cab photo file sits after a call that never happened is not a documented default of the plugin. | Cab-photo and violation-file uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Entrapment-name, duration, floor, traffic-hours, violation-history, or tenant-name fields often depend on the fields you configure. An entrapment note is stored text, not proof anyone was trapped. A violation PDF is a stored file, not a citation. An elevator booking is not proof anyone serviced the car. A page request is not proof anyone booked. The page URL can say elevator even when no form is submitted. Ask your web vendor who can open entries and uploads, whether logs remain reachable by direct URL, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess stairlifts or safe deliveries. Review stored records, uploaded files, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 20, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-elevator-service-plugin-privacy