Knife sharpening plugin privacy

The drop-off ticket that inventories every blade in the house

A sharpening drop-off ticket can list every knife, cleaver, and edged tool in a household. Counts, types, sometimes photos, stapled to a name, address, and the pickup date when they are all out of the house. The only written inventory of the blades in a kitchen can sit in a form plugin entries table next to a marketing consent checkbox. Blade-count, blade-type, knife-list, cleaver, edged-tool, pickup-date, address, and blade-photo fields are configured, not documented defaults. Optional blade photos go in the site uploads folder. A drop-off ticket is not proof knives were sharpened. A blade count is a stored number, not an inventory of blades that exist. A blade photo is an upload, not proof of the knives in the house. A pickup date is a stored date, not proof the house is empty. A page request is not proof anyone dropped off. The page URL can say knife sharpening 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 drop-off and pickup pages, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a weapons claim, a blade-law claim, an occupancy claim, a theft claim, or a GDPR or other compliance assessment.

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 drop-off tickets, blade lists, and page tags go

Drop-off tickets and forms handled on your WordPress site

Check which blade-count, blade-type, knife-list, cleaver, edged-tool, pickup-date, address, or blade-photo fields you enable, who can open form entries and bookings, where uploaded blade photos live in the uploads folder, which inboxes receive copies, and how long records, files, emails, and backups are kept after a ticket that never became a pickup. Notification emails can also copy the same blade lists, photos, and addresses off-site. One table can name the house, how many knives left it, and the pickup date next to a name, even when the blades never come back. Ask your web vendor not to collect a blade list next to a pickup date and address on the first public form, not to store that inventory next to a name in one open submissions list, and to purge unused tickets after the date passes. A privacy-policy page does not by itself limit who can export a drop-off list or republish an upload. A stored ticket is not proof knives were sharpened.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the knife-sharpening drop-off or pickup page. That page request can reach a vendor host before anyone submits. The page URL can say knife sharpening even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off drop-off and pickup pages if you do not want that page request. A browser scan cannot inspect stored blade lists, photos, or addresses. A "blade inventory" badge is not a verified storage path.

Knife-sharpening drop-off, pickup, 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 sharpening or POS software without a WordPress.org listing is 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). 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 sharpening drop-off is a booking you create; a service name such as kitchen knives, cleaver, scissors, or pickup is a label you configure. Neither is a documented default. Blade-count, blade-type, knife-list, cleaver, edged-tool, pickup-date, address, or blade-photo questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked drop-off is not proof knives were sharpened, and is not an inventory of blades that exist. Cancelling or missing the slot later does not erase the blade list, photos, or address already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a ticket that never became a pickup is not a documented default of the plugin. 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.

Drop-off bookings, custom intake fields, and automatic confirmation emails 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. Blade-count, blade-type, knife-list, cleaver, edged-tool, pickup-date, address, or blade-photo questions are fields you add; they are not documented defaults. A blade photo is a file you accept; that file type is not a documented default. A drop-off ticket is not proof knives were sharpened. A blade count is a stored number, not an inventory of blades that exist. A blade photo is an upload, not proof of the knives in the house. A pickup date is a stored date, not proof the house is empty. 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 ticket sits after it never became a pickup is not a documented default of the plugin.

Drop-off and blade-photo entries stored in WordPress; file uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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 blade-count, knife-list, or address field was sent. A page request from this script is not proof anyone dropped off. The page URL can say knife sharpening even when no form is submitted. Consent timing has not been tested. Review which tags you enable on drop-off and pickup pages. Keep marketing tags off those pages if you do not want that page request. A tagged drop-off page can re-confirm knife-sharpening interest next to a stored address and files; this row does not claim a pickup from that request.

Marketing tags handled through Meta, Google, or other configured platformsconnect.facebook.netNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Blade-count, blade-type, knife-list, cleaver, edged-tool, pickup-date, address, or blade-photo fields often depend on the fields you configure. A drop-off ticket is not proof knives were sharpened. A blade count is a stored number, not an inventory of blades that exist. A blade photo is an upload, not proof of the knives in the house. A pickup date is a stored date, not proof the house is empty. A marketing-tag page request is not proof anyone dropped off. The page URL can say knife sharpening even when no form is submitted. The blade list, the photos, and the address can sit after the ticket never becomes a pickup. This page is about a drop-off ticket that inventories every blade in the house, not a jewelry-repair heirloom ticket, not a consignment-shop belongings intake, and not a metal-detecting buried-item pin. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the drop-off or pickup page, and how long records and backups are kept. A portfolio 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 weapons law, blade law, occupancy, or theft. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on drop-off and pickup pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-knife-sharpening-plugin-privacy