Awning plugin privacy

The measurement visit that books itself for when the storefront is empty

An awning WordPress stack is not only a quote calendar — it is often a schedule of when the storefront stands empty. Every confirmed measurement can store opening hours, which mornings are slow, and the alley door the installer should use, next to a name and address in a forms table. A storefront photo can sit beside that schedule in the uploads folder. A page request is not proof anyone booked. An opening-hours answer is a stored schedule, not proof the store stood empty. An alley-door note is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where storefront photos land, which inboxes receive copies, and how long past quotes, files, and backups are kept.

Documentation review only. This is not legal advice, a burglary-risk claim, an insurance claim, a permit-outcome claim, a GDPR or other compliance assessment, or a judgment about awning installers.

Scan your site for third-party requests

The 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 opening hours, alley-door notes, and measurement bookings go

Entries, bookings, and uploads on your WordPress site

Check which opening-hours, slow-day, alley-door, rear-access, storefront-photo, or measurement-notes fields you enable, who can open form entries and measurement bookings, where uploaded storefront photos live in the uploads folder, which inboxes receive copies, and how long past quotes, files, and backups are kept after a measurement that never happened. Notification emails can also copy the same address, empty-hour notes, and photo 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 measurement calendar. A "commercial awning installer" badge is not a verified storage path.

Awning measurement, quote-form, and storefront-photo 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 awning SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
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 "measure when closed Tue mornings" window or an "alley door by the dumpster — code 2219" access note is a booking you create; a service name such as awning measurement or canopy install is a label you configure. Neither is a documented default. Opening-hours, slow-day, alley-door, rear-access, or storefront-photo 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 entry — and a CSV export of "Tue closed + alley door 2219 + storefront photo" next to a named retailer is still a calendar that answers when someone will find the storefront empty for a measurement visit. 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.

Awning measurement bookings stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
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. Opening-hours, slow-day, alley-door, rear-access, measurement-notes, property-address, contact-name, phone, or email questions are fields you add; they are not documented defaults. Optional storefront-photo uploads are files you accept; that file type is not a documented default. An opening-hours answer is a stored schedule, not proof the store stood empty. An alley-door note is stored text, not proof anyone entered. An awning form is not proof anyone measured or installed. 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 an opening-hours row sits after a quote that never happened is not a documented default of the plugin.

Opening-hours and alley-door answers stored in WordPress; optional storefront-photo uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 storefront photo or measurement sketch is a file you accept; that file type is not a documented default. An uploaded storefront photo is a stored file, not a burglary map claim. 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 storefront-photo file sits after a quote that never happened is not a documented default of the plugin.

Storefront-photo and document uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Opening-hours, slow-day, alley-door, rear-access, storefront-photo, or measurement-notes fields often depend on the fields you configure. An opening-hours answer is a stored schedule, not proof the store stood empty. An alley-door note is stored text, not proof anyone entered. An awning booking is not proof anyone measured or installed. A page request is not proof anyone booked. The page URL can say awning even when no form is submitted. Ask your web vendor who can open entries and uploads, whether storefront photos 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 burglary risk, insurance coverage, or permit outcomes. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

Documentation snapshot: Oct 21, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-awning-plugin-privacy