Go kart plugin privacy

The kiosk that scans your driver's license and posts your lap times under your real name

The track's kiosk scans your actual driver's license — the one document that carries your legal name, DOB, address, and license number in a single swipe — just to prove you're allowed to drive a 40cc kart. Then the timing system publishes your name and best lap on a public leaderboard that never expires. The DMV guards that card; the speed park stores it in a form plugin. Minors ride too, so height, weight, and a parent's signature sit in the same row. Those fields are configured, not documented defaults. A track booking is a calendar row, not proof anyone raced. A license answer is what a guest typed or a kiosk stored, not a DMV file. An intake upload is a client document in a site uploads folder. A page request is not proof anyone entered a kart. The page URL can say go kart even when no form is submitted. Ask what happens to the license number, DOB, address, height, weight, parent signature, and published lap name after the heat ends — the kiosk that scans your driver's license and posts your lap times under your real name outlives the race. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the check-in page, and how long records, emails, and backups are kept.

Documentation review only. This is not legal advice, a driver's-license-law claim, a DMV claim, a minor-age-rule claim, a venue-liability-law claim, a leaderboard-publicity-law 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 license answers, heat bookings, and page tags go

Intakes and bookings on your WordPress site

Check which license-number, DOB, address, height, weight, parent-signature, or leaderboard-name fields you enable, who can open form entries and heat bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the heat ends — when the kiosk that scans your driver's license and posts your lap times under your real name still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to a license number, a minor's height and weight, a parent signature, and a best lap that never left the board. Ask your web vendor not to keep license numbers next to DOBs, addresses, and published lap names in one open submissions list longer than operations need, and to purge license-grade fields when a heat closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored track booking is not proof anyone raced. A license answer is not a DMV file.

Page tags handled by a vendor

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

License-intake, booking, and marketing-tag setups

Three plugins reviewed from public documentation. Specialty go-kart / timing SaaS tools without a WordPress.org listing are outside this sample.

No paid placement. Site-hosted tools appear first, followed by vendor-hosted tools. Names are alphabetical within each group.

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 Saturday heat slot or a track block is a booking you create; a service name such as go kart or junior session is a label you configure. Neither is a documented default. License-number, DOB, address, height, weight, parent-signature, or leaderboard-name questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a calendar row, not proof anyone raced — and a CSV export of "Jordan Lee, DOB 03/14/1991, Lic #D1234567, best lap 42.1" next to a contact name is still a calendar that holds a license-grade identity next to a published lap. 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.

Track and heat 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. Legal-name, DOB, address, license-number, height, weight, parent-signature, or leaderboard-name fields are fields you add; they are not documented defaults. Completing the form can store a kiosk-scanned license number next to a legal name, DOB, home address, a minor's height and weight, a parent's signature, a contact name, and optional license-photo or waiver uploads — typed once so the front desk does not have to re-key the heat, into the same tables as a go-kart-session label. A license answer is what a guest typed or a kiosk stored, not a DMV file. A track booking is a calendar row, not proof anyone raced — and a staff login can open "Jordan Lee, DOB 03/14/1991, Lic #D1234567, ht 4 ft 10 in, parent sig, waiver PDF" 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.

License, DOB, and address answers stored in WordPress; optional license or waiver 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 license-number, DOB, address, height, weight, parent-signature, or leaderboard-name field was sent. A page request from this script is not proof anyone entered a kart. The page URL can say go kart even when no form is submitted. Consent timing has not been tested. Review which tags you enable on check-in and 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. License-number, DOB, address, height, weight, parent-signature, or leaderboard-name fields often depend on the fields you configure. A track booking is a calendar row, not proof anyone raced. A license answer is what a guest typed or a kiosk stored, not a DMV file. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone entered a kart. The page URL can say go kart even when no form is submitted. The kiosk that scans your driver's license and posts your lap times under your real name — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that license-kiosk and never-expiring-leaderboard stack, not a driving-school instructional permit intake, a foot-race registration leaderboard, a trampoline-park kiosk waiver, or a court-ordered DUI-school driving context. Ask your web vendor who can open entries, whether a marketing tag loads on the check-in page, and how long records and backups are kept. A "go kart privacy" or "track-compliant" 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 driver's-license law, DMV rules, age rules for minors at tracks, venue liability law, or leaderboard publicity law. Review stored records, bookings, connected services, exports, notification emails, marketing tags on check-in and booking 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-go-kart-plugin-privacy