Courier plugin privacy

The dispatch form that pairs two addresses and proves who talks to whom

A courier WordPress stack is not only a dispatch calendar. It is often a relationship record. Every ticket can pair a pickup address with a drop-off address, timestamped, with a signature at each end. Recurring runs between a law office and a residence, or a pharmacy and a care home, narrate a connection people assume is private. Leave-at-side-door instructions and gate codes persist across jobs. A page request is not proof anyone booked. A paired address is stored text, not proof of a relationship. A gate code is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where signatures land, which inboxes receive copies, and how long past tickets, files, and backups are kept.

Documentation review only. This is not legal advice, a relationship claim, a delivery-network claim, a household-inventory claim, a GDPR or other compliance assessment, or a judgment about couriers.

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 paired addresses, signatures, and courier bookings go

Entries, bookings, and uploads on your WordPress site

Check which pickup-address, drop-off-address, signature, recurring-run, side-door, or gate-code fields you enable, who can open form entries and service bookings, where uploaded POD photos live in the uploads folder, which inboxes receive copies, and how long past tickets, files, and backups are kept after a run that never happened. Notification emails can also copy the same paired addresses, signatures, 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 dispatch calendar. A "bonded courier" badge is not a verified storage path.

Courier booking, paired-address, and gate-code 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 courier 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 same-day window or a "leave at side door — gate code 4412" access note is a booking you create; a service name such as courier or same-day run is a label you configure. Neither is a documented default. Pickup-address, drop-off-address, signature, recurring-run, side-door, or gate-code 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 a run — and a CSV export of "law office → residence + gate code 4412" next to a named sender is still a calendar that answers who talks to whom. 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.

Courier service 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. Pickup-address, drop-off-address, signature, recurring-run, side-door, gate-code, recipient-name, phone, or email questions are fields you add; they are not documented defaults. Optional POD-photo uploads are files you accept; that file type is not a documented default. A paired address is stored text, not proof of a relationship. A gate code is stored text, not proof anyone entered. A courier form is not proof anyone ran the route. 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 paired-address row sits after a run that never happened is not a documented default of the plugin.

Pickup and drop-off answers stored in WordPress; optional POD-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 POD photo or shipping label is a file you accept; that file type is not a documented default. An uploaded POD photo is a stored file, not proof of a relationship. 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 POD-photo file sits after a run that never happened is not a documented default of the plugin.

POD-photo and label 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. Pickup-address, drop-off-address, signature, recurring-run, side-door, or gate-code fields often depend on the fields you configure. A paired address is stored text, not proof of a relationship. A gate code is stored text, not proof anyone entered. A courier booking is not proof anyone ran the route. A page request is not proof anyone booked. The page URL can say courier even when no form is submitted. Ask your web vendor who can open entries and uploads, whether POD 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 firewood routes, propane schedules, meal-delivery sheets, or household moves. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-courier-plugin-privacy