Ignition interlock plugin privacy

The service appointment for the device the court put in your car

An ignition-interlock installer booking form can collect a name, a phone number, a vehicle, a license plate, a monitoring-authority reference, an install date, and a monthly recalibration date. Recalibration is a repeating visit. Each booking can add another row, so the number of rows can grow for as long as those visits continue. That count is not a court sentence, a conviction record, or a compliance report. A missed appointment can remain in the list. Reminder emails can put the word interlock in a subject line that lands in a shared family inbox. Those answers can sit in a local-first form or booking plugin behind one admin login. A marketing tag on the same page can send a page request to a vendor host before anyone submits. A page request is not proof that anyone has a device in their car. An appointment is not a conviction record. The page URL can say ignition interlock even when no form is submitted. This sample reviews three plugins' documentation. Check which fields you collect, who can open bookings and entries, where uploaded files land, which tags load on the booking page, and how long records, files, emails, and backups are kept.

Documentation review only. This is not legal advice, a DMV-process claim, a sentencing-law claim, a device-regulation claim, a compliance-reporting 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 bookings, form entries, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.

Where bookings, uploads, and page tags go

Bookings and files handled on your WordPress site

Check which name, phone, vehicle, license-plate, monitoring-authority, install-date, or recalibration-date fields you enable, who can open bookings and form entries, where uploaded license or registration files live in the uploads folder, which inboxes receive copies, and how long records, files, and backups are kept after a booking that never became a completed service visit. Recalibration is a repeating visit; each booking can add another row. A missed appointment can remain in the list. Notification emails can also copy the same answers off-site and can put the word interlock in a subject line. Ask your web vendor not to collect a license plate or monitoring-authority reference on the first public form, and not to store a vehicle next to an install date in one open appointments list.

Page tags handled by a vendor

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

Ignition-interlock booking, form, 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 ignition-interlock hardware or monitoring 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 clinics and service businesses (plugin version 4.0.3). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, CSV export, and email notifications that can include custom fields. Version 3.12.13 added a repeat appointment feature. An ignition-interlock install or monthly recalibration slot is a booking you create; a service name such as ignition interlock or device calibration is a label you configure. Neither is a documented default. Name, phone, vehicle, license-plate, monitoring-authority, install-date, or recalibration-date questions are custom fields you add (textarea, select, or input); they are not documented defaults. Recalibration is a repeating visit you schedule; each booking can add another row. The number of rows can grow for as long as those visits continue. That count is not a court sentence, a conviction record, or a compliance report. A missed appointment can remain in the appointments list. Reminder emails can put the word interlock in a subject line. An appointment is not a conviction record. 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.

Install and recalibration bookings and custom fields 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. Name, phone, vehicle, license-plate, monitoring-authority, install-date, or recalibration-date questions are fields you add; they are not documented defaults. License, registration, or ID scans are files you accept; they are not documented defaults. One entry can store a license plate next to a monitoring-authority reference. Repeat submissions can add more rows over time. An appointment form entry is not a conviction record. Notification emails can copy field values off-site and can put the word interlock in a subject line that lands in a shared family inbox. Optional Stripe, PayPal, HubSpot, Mailchimp, and webhook integrations send data only when you enable them. Public form-page browser hosts are unverified.

Form 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 name, vehicle, license plate, monitoring-authority reference, install date, or recalibration date was sent. A page request from this script is not proof anyone has a device in their car. The page URL can say ignition interlock even when no form is submitted. Consent timing has not been tested. Review which tags you enable on install and recalibration booking 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. Name, phone, vehicle, license-plate, monitoring-authority, install-date, or recalibration-date answers often depend on the fields you configure. An appointment is not a conviction record. Recurring recalibration bookings that add rows over time are not a court sentence or a compliance report. A marketing-tag page request is not proof that anyone has a device in their car. The page URL can say ignition interlock even when no form is submitted. This page is about the service appointment after a class, not a classroom enrollment, a tow, or an anger-management class. Ask your web vendor who can open bookings and entries, where uploaded files live, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "secure" or "confidential interlock records" 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 DMV processes, sentencing law, device regulation, or compliance reporting. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on booking pages, and backups.

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

Related pages

Scan your site for third-party requests

/wp-ignition-interlock-plugin-privacy