Axe throwing plugin privacy
The waiver that timestamps your drinks next to your throws
Axe throwing is the one venue where the booking plugin knowingly pairs two records that were never meant to meet: the liability waiver you signed to hurl a hatchet, and the bar tab that says what you drank while doing it. League nights add a standing roster with your throwing scores and attendance pattern — which weeknight you are reliably not at home. If anything ever goes wrong, that form data is the first thing subpoenaed, and it lives in a WordPress table the venue forgot about. Those fields are configured, not documented defaults. A lane booking is a calendar row, not proof anyone threw. A waiver answer is what a guest typed or uploaded, not a court finding. A bar-tab line is an order note, not a breathalyzer. A league score is a self-reported or staff-entered number, not a certified ranking. A page request is not proof anyone stepped onto a lane. The page URL can say axe throwing even when no form is submitted. Ask what happens to the waiver, the drink order, the league score, and the attendance stamp after the night ends — the waiver that timestamps your drinks next to your throws outlives the last round. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the booking page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a venue-liability-law claim, an alcohol-service-law claim, an age-verification-law claim, a workers-comp or injury-claim assessment, 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 waiver answers, bar tabs, league bookings, and page tags go
Intakes and bookings on your WordPress site
Check which liability-waiver, bar-tab, league-score, or attendance fields you enable, who can open form entries and lane bookings, which inboxes receive copies, and how long records, emails, and backups are kept after the night ends — when the waiver that timestamps your drinks next to your throws still holds that row. Notification emails can also copy those fields off-site. One table can list a legal name next to a signed waiver, a drink order, a Tuesday league score, and an attendance stamp that maps which weeknight that person is reliably not at home. Ask your web vendor not to keep waivers next to bar tabs and league attendance in one open submissions list longer than operations need, and to purge those fields when a league season closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored lane booking is not proof anyone threw. A bar-tab line is not a breathalyzer.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the axe-throwing booking page. That page request can reach a vendor host before anyone submits. The page URL can say axe throwing 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 entries or bookings. A "axe throwing privacy" badge is not a verified storage path.
Waiver-plus-tab, booking, and marketing-tag setups
Three plugins reviewed from public documentation. Specialty axe-throwing / venue 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.
| 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A Saturday lane slot or a Tuesday league block is a booking you create; a service name such as axe throwing or league night is a label you configure. Neither is a documented default. Liability-waiver, bar-tab, league-score, or attendance 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 threw — and a CSV export of "Sam Rivera, waiver: signed, tab: 2 IPAs, league score: 42, attendance: Tue 7pm" next to a contact name is still a calendar that holds a drink order next to a hatchet waiver. 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. | Lane and league bookings stored 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. Liability-waiver, bar-tab, league-score, or attendance fields are fields you add; they are not documented defaults. Completing the form can store a signed waiver next to a drink order, a Tuesday league score, an attendance stamp that maps which weeknight a guest is reliably not at home, a contact name, and optional waiver PDF uploads — typed once so the front desk does not have to re-key the booking, into the same tables as an axe-throwing label. A waiver answer is what a guest typed or uploaded, not a court finding. A lane booking is a calendar row, not proof anyone threw — and a staff login can open "Sam Rivera, waiver PDF, tab: 2 IPAs, league score: 42, attendance: Tue 7pm" 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. | Waiver and bar-tab answers stored in WordPress; optional waiver 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 liability-waiver, bar-tab, league-score, or attendance field was sent. A page request from this script is not proof anyone stepped onto a lane. The page URL can say axe throwing even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking pages. | 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. Liability-waiver, bar-tab, league-score, or attendance fields often depend on the fields you configure. A lane booking is a calendar row, not proof anyone threw. A waiver answer is what a guest typed or uploaded, not a court finding. A bar-tab line is an order note, not a breathalyzer. A league score is a self-reported or staff-entered number, not a certified ranking. An intake upload is a client document in a site uploads folder. A marketing-tag page request is not proof anyone stepped onto a lane. The page URL can say axe throwing even when no form is submitted. The waiver that timestamps your drinks next to your throws — that is a storage path next to names and contacts, not a feature these plugins claim. This page is about that waiver-plus-bar-tab and league-attendance stack, not a laser-tag kids party roster, a go-kart kiosk leaderboard, a shooting-range firearm sign-in log, or an escape-room adult group booking. Ask your web vendor who can open entries, whether a marketing tag loads on the booking page, and how long records and backups are kept. A "axe throwing privacy" or "venue-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 venue liability law, alcohol-service law, age-verification law, workers-comp, or injury claims. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.
Documentation snapshot: Oct 15, 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-axe-throwing-plugin-privacy