Garage door repair plugin privacy
The service ticket that announces your house will not lock tonight
A broken garage door is a house that cannot fully lock, and the repair request timestamps exactly how long it has been that way. A form can collect a stuck-open-since note, a property address, a when-home window, a door photo that shows the opener and the garage inventory, and a gate or keypad code so the tech can get in if you leave. That row can sit in a form plugin entries table any staffer can open. Stuck-open-since, property-address, when-home, door-photo, opener-model, garage-inventory, gate-code, keypad-code, owner-name, phone, and service-date fields are configured, not documented defaults. Optional door photos go in the site uploads folder. A stuck-open note is a stored note, not proof the door will not lock. A property address is a stored location, not a verified residence. A when-home window is a stored booking, not proof anyone will be home. A door photo is an upload, not proof of a broken door, an opener model, or garage inventory. An opener model is a stored label, not a verified serial. A gate or keypad code is a stored secret, not proof of access. A garage-door booking is not proof anyone booked a repair. A page request is not proof anyone booked. The page URL can say garage door repair 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 booking and quote pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a lock-security claim, an appliance-repair claim, an EV-charger claim, a handyman claim, an insurance 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 garage-door quotes, door photos, and page tags go
Repair bookings and forms handled on your WordPress site
Check which stuck-open-since, property-address, when-home, door-photo, opener-model, garage-inventory, gate-code, keypad-code, owner-name, phone, or service-date fields you enable, who can open form entries and bookings, where uploaded door photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a request that never became a repair job. Notification emails can also copy the same stuck-open notes, addresses, when-home windows, door photos, opener models, gate codes, keypad codes, and owner names off-site. One table can name the house, the stuck-open note, and the keypad code next to a phone, even when the repair is never sold. Ask your web vendor not to collect a keypad code next to a stuck-open note and a property address on the first public form, not to store those door photos next to a when-home window in one open submissions list, and to purge unused quotes after the date passes. A privacy-policy page does not by itself limit who can export a quote list or republish an upload. A stored quote is not proof the door will not lock.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the garage-door-repair booking or quote page. That page request can reach a vendor host before anyone submits. The page URL can say garage door repair even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and quote pages if you do not want that page request. A browser scan cannot inspect stored stuck-open notes, door photos, or keypad codes. A "same-day service" badge is not a verified storage path.
Garage-door-repair booking, quote, 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 garage-door dealer 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 garage-door repair is a booking you create; a service name such as garage door repair, opener service, spring replacement, or emergency same-day is a label you configure. Neither is a documented default. The stored service name can say garage door repair in plain text before anyone arrives. Stuck-open-since, property-address, when-home, opener-model, gate-code, keypad-code, owner-name, phone, or service-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. A stuck-open note is a stored note, not proof the door will not lock. A property address is a stored location, not a verified residence. A when-home window is a stored booking, not proof anyone will be home. An opener model is a stored label, not a verified serial. A gate or keypad code is a stored secret, not proof of access. A booked slot is not proof anyone booked a repair, and is not proof a door was fixed. Cancelling or missing the slot later does not erase the stuck-open note, address, when-home window, or keypad code already stored next to a name, and does not unsend a confirmation email already delivered. How long that pairing sits after a booking that never became a repair job is not a documented default of the plugin. The appointments list can show who is booked this week and at which address. 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. | Garage-door-repair 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. Stuck-open-since, property-address, when-home, opener-model, gate-code, keypad-code, owner-name, phone, or service-date questions are fields you add; they are not documented defaults. Door photos and opener-label photos are files you accept; those file types are not documented defaults. A stuck-open note is a stored note, not proof the door will not lock. A property address is a stored location, not a verified residence. A when-home window is a stored booking, not proof anyone will be home. A door photo is an upload, not proof of a broken door, an opener model, or garage inventory. An opener model is a stored label, not a verified serial. A gate or keypad code is a stored secret, not proof of access. A garage-door booking is not proof anyone booked a repair. 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 pairing sits after a request that never became a repair job is not a documented default of the plugin. | Quote and door-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 stuck-open-since, property-address, or keypad-code field was sent. A page request from this script on a garage-door-repair quote page is not proof anyone booked, and a pre-consent tag on that page can still treat garage-door-repair interest as an audience segment from the URL alone. The page URL can say garage door repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and quote pages. Keep marketing tags off those pages if you do not want that page request. A tagged quote page can re-confirm garage-door-repair interest next to a stored address; this row does not claim a repair job 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. Stuck-open-since, property-address, when-home, door-photo, opener-model, garage-inventory, gate-code, keypad-code, owner-name, phone, or service-date fields often depend on the fields you configure. A stuck-open note is a stored note, not proof the door will not lock. A property address is a stored location, not a verified residence. A when-home window is a stored booking, not proof anyone will be home. A door photo is an upload, not proof of a broken door, an opener model, or garage inventory. An opener model is a stored label, not a verified serial. A gate or keypad code is a stored secret, not proof of access. A garage-door booking is not proof anyone booked a repair. A marketing-tag page request is not proof anyone booked. The page URL can say garage door repair even when no form is submitted. The stuck-open note, the address, the door photo, and the keypad code can sit after a request that never became a repair job. This page is about the service ticket that announces your house will not lock tonight, not an appliance-repair garage-code booking, not a locksmith lock record, not an EV-charger panel map, and not a general handyman visit. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or quote page, and how long records and backups are kept. A "same-day service" 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 lock-security, appliance-repair, EV-charger, handyman, or insurance claims. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and quote pages, and backups.
Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress file upload plugin privacy
- All privacy guides
/wp-garage-door-repair-plugin-privacy