Computer repair plugin privacy

The drop-off form where typing your real password is the intended use

A repair-shop site can look like a calendar and a short drop-off form. The same form often asks for a device password, a lock-screen PIN, a description of the problem, what to recover, and a pickup contact — and asks for a photo of the damage or a proof-of-purchase scan — and stores those answers next to the customer's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a drop-off booking next to a device password, a what-to-recover note, and a marketing pixel — the drop-off form where typing your real password is the intended use, typed once into a vendor table next to a newsletter signup. A password typed into an intake is a credential the shop asked for, not consent to read everything on the device. A describe-the-problem answer is the customer's words, not an inventory of the drive. A what-to-recover request names what matters most, not what exists. A drop-off booking is custody logistics, not authorization beyond the ticket. An uploaded proof-of-purchase is a stored file in a site uploads folder, not a verified ownership record. A page request is not proof anyone's device holds anything. The page URL can say computer-repair even when no form is submitted. Ask what happens to the device password after the ticket closes — people reuse passwords, so the quietest detail is that the same string that opens the laptop in the back room can still open the customer's email and banking apps long after the machine leaves the bench. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the drop-off page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a claim about the shop's data-security or encryption practices, a claim about technician conduct, a right-to-repair or computer-fraud (CFAA) claim, a warranty 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 bookings, password notes, and page tags go

Bookings and notes on your WordPress site

Check which device-password, lock-screen-PIN, describe-the-problem, what-to-recover, or pickup-contact fields you enable, who can open form entries and drop-off or diagnostic bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a visit closes — when the drop-off form asks you to type your real password so a stranger can get in. Notification emails can also copy those fields off-site. One table can list every Friday drop-off next to a device password and a what-to-recover note. Ask your web vendor not to keep proof-of-purchase uploads next to plaintext password rows in one open submissions list longer than operations need, and to purge intake rows when the ticket closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not authorization beyond the ticket. A password in a form table is not consent to read everything on the device.

Page tags handled by a vendor

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

Drop-off / diagnostic booking, repair intake, 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 repair-shop POS and RMA 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 Friday drop-off or a Monday diagnostic slot is a booking you create; a service name such as laptop drop-off or diagnostics is a label you configure. Neither is a documented default. Device-password, lock-screen-PIN, describe-the-problem, or what-to-recover questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is custody logistics, not authorization beyond the ticket — and a CSV export of a drop-off row next to a device password and a what-to-recover note is still a calendar that holds a credential beside a customer name. 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.

Drop-off and diagnostic 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. Device-password, lock-screen-PIN, describe-the-problem, what-to-recover, or pickup-contact questions are fields you add; they are not documented defaults. Completing the form can store a device password next to a lock-screen PIN, a describe-the-problem answer, a what-to-recover request, a pickup-contact note, and optional photo-of-damage or proof-of-purchase uploads — typed once as the drop-off form where typing your real password is the intended use, into the same tables as a newsletter signup. A password typed into an intake is a credential the shop asked for, not consent to read everything on the device. A describe-the-problem answer is the customer's words, not an inventory of the drive. A what-to-recover request names what matters most, not what exists. An uploaded proof-of-purchase is a stored document in a site uploads folder, not a verified ownership record — and a staff login can open "MacBook, PIN 4829, won't boot — late wife's photos, recover Photos library, receipt JPEG" next to everyone else's resume. Notification emails can copy field values and files off-site. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Repair intake entries stored in WordPress; optional photo-of-damage and proof-of-purchase 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 device-password, lock-screen-PIN, describe-the-problem, or what-to-recover field was sent. A page request from this script is not proof anyone's device holds anything. The page URL can say computer-repair even when no form is submitted. Consent timing has not been tested. Review which tags you enable on drop-off, diagnostic, and intake pages.

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. Device-password, lock-screen-PIN, describe-the-problem, what-to-recover, or pickup-contact fields often depend on the fields you configure. A password typed into an intake is a credential the shop asked for, not consent to read everything on the device. A describe-the-problem answer is the customer's words, not an inventory of the drive. A what-to-recover request names what matters most, not what exists. A drop-off booking is custody logistics, not authorization beyond the ticket. An uploaded proof-of-purchase is a stored file in a site uploads folder, not a verified ownership record. A marketing-tag page request is not proof anyone's device holds anything. The page URL can say computer-repair even when no form is submitted. The drop-off form where typing your real password is the intended use — that is a storage path next to a what-to-recover note, not a feature these plugins claim. This page is about that repair intake, not a physical-key locksmith job sheet or a self-storage gate-code roster. Ask your web vendor who can open entries, whether a marketing tag loads on the drop-off page, and how long password rows and backups are kept after the ticket closes. A "trusted repair" 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 the shop's data-security or encryption practices, technician conduct, right-to-repair or computer-fraud (CFAA) law, or warranty status. Review stored records, bookings, connected services, exports, notification emails, marketing tags on drop-off pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-computer-repair-plugin-privacy