Car title loan plugin privacy
The application where being tracked is a condition of the money
A car-title-loan application can look like a VIN and a photo of the car. It is also a map of where you sleep, where you work, who will say where you are, and a checkbox that the car itself will report your location until the debt clears. VIN, plate, income, home-and-work-address, reference, and GPS-acknowledgment fields are configured, not documented defaults. The GPS-consent checkbox is the product: being tracked is a condition of the money. One WordPress row can hold the vehicle, both addresses, the people to call, and the disclosure that a tracker or starter-interrupt device is part of the loan. An application row is not proof of default or financial distress. A GPS acknowledgment field is a configured disclosure, not evidence a device was installed. A reference name is a contact the borrower typed, not a co-signer. A page request is not proof anyone borrowed. The page URL can say title loan or title pawn 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 application pages, and how long records, files, emails, and backups are kept.
Documentation review only. This is not legal advice, a lending-law claim, a usury-rate claim, a repossession-law claim, a GPS-tracking-legality claim, a consumer-protection-compliance 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 VIN lists, GPS checkboxes, appraisal bookings, and page tags go
Appraisal bookings and applications handled on your WordPress site
Check which VIN, plate, income, home-and-work-address, reference, or GPS-acknowledgment fields you enable, who can open form entries and bookings, where uploaded titles and vehicle 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 loan. Notification emails can also copy the same VIN, addresses, and GPS acknowledgment off-site. One table can name the car, both addresses, and the tracker checkbox next to a name, even when the loan never funds. Ask your web vendor not to collect a GPS-tracker acknowledgment or both home and work addresses on the first public form, not to store that disclosure next to a VIN in one open submissions list, and to purge unused appraisal bookings after the date passes. A privacy-policy page does not by itself limit who can export an application list. A stored booking is not proof an appraisal occurred.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the car-title-loan booking or application page. That page request can reach a vendor host before anyone submits. The page URL can say title loan or title pawn even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off booking and application pages if you do not want that page request. A browser scan cannot inspect stored VIN lists or GPS acknowledgments. A "secure application" badge is not a verified storage path.
Car-title-loan booking, application, 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 title-loan or lender 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. An appraisal or title-loan consult is a booking you create; a service name such as title loan, vehicle appraisal, or title pawn is a label you configure. Neither is a documented default. VIN, plate, income, home-and-work-address, reference, or GPS-and-interrupt-acknowledgment questions are custom fields you add (textarea, select, or input); they are not documented defaults. A booked appraisal is not proof a visit happened and is not proof of default or financial distress for anyone named in the application. Cancelling or missing the visit later does not erase the VIN, addresses, or GPS acknowledgment already stored next to a name, and does not unsend a confirmation email already delivered. How long that row sits after a booking that never became a loan 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. | Appraisal bookings, custom application 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. VIN, plate, income, home-and-work-address, reference, or GPS-and-interrupt-acknowledgment questions are fields you add; they are not documented defaults. A vehicle title, a vehicle photo, or a pay stub is a file you accept; none of those file types is a documented default. An application row is not proof of default or financial distress. A GPS acknowledgment field is a configured disclosure, not evidence a device was installed. A reference name is a contact the borrower typed, not a co-signer. An uploaded title is a client document, not a recorded lien. 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 application sits after a request that never became a loan is not a documented default of the plugin. | Application and document-upload 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 VIN, plate, income, address, reference, or GPS-acknowledgment field was sent. A page request from this script is not proof anyone borrowed. The page URL can say title loan or title pawn even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and application pages. Keep marketing tags off those pages if you do not want that page request. A tagged application page can re-confirm interest next to a stored VIN and GPS checkbox; this row does not claim a loan outcome 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. VIN, plate, income, home-and-work-address, reference, or GPS-acknowledgment fields often depend on the fields you configure. An application row is not proof of default or financial distress. A GPS acknowledgment field is a configured disclosure, not evidence a device was installed. A reference name is a contact the borrower typed, not a co-signer. An uploaded title is a client document, not a recorded lien. A marketing-tag page request is not proof anyone borrowed. The page URL can say title loan or title pawn even when no form is submitted. The GPS checkbox can sit after the loan never funds. This page is about an application where being tracked is a condition of the money, not a payday-loan contact list, a repossession-agency tow order, a pawn-shop ticket, a bankruptcy-attorney intake, a debt-collection file, or a bail-bonds collateral pledge. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the booking or application page, and how long records and backups are kept. A "secure" 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 lending law, usury rates, repossession law, GPS-tracking legality, or consumer-protection compliance. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking and application pages, and backups.
Documentation snapshot: Oct 14, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-car-title-loan-plugin-privacy