Dog behaviorist plugin privacy

The bite-history intake that timestamps what you knew

A dog-behaviorist WordPress stack is not only a booking calendar — it is a liability log the owner wrote voluntarily. Before the first session, the intake often asks for incident dates, who was bitten, severity, "has bitten before", muzzle history, quarantine notes, vet records, and incident photos. The owner authors a timestamped admission log that sits in a form table behind one admin login — and the bitten person often appears in a form they never saw. No breach required: the intake that was supposed to fix the dog is the exhibit that proves you knew. Ask how long intakes are kept and who can export them — retention length is subpoena exposure, not housekeeping. A marketing tag on the same intake page can send a page request to a vendor host before anyone submits — and that page request alone can treat dog-behaviorist intake intent as an audience segment from the URL. A page request is not proof a bite history was collected. An intake answer is not a legal admission and not proof an incident occurred. Bite-history fields are fields you configure, not defaults. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which tags load on the intake page, and how long past intakes, files, and backups are kept.

Documentation review only. This is not legal advice, a dog-bite-law claim, a strict-liability or breed-legislation assessment, an insurance or litigation-outcome claim, a GDPR or other compliance assessment, or a judgment about owners or trainers.

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 bite-history intakes, session bookings, and page tags go

Entries, uploads, and bookings on your WordPress site

Check which bite-history, severity, prior-victim, muzzle-history, or quarantine fields you enable, who can open form entries and session bookings, where uploaded vet records or incident photos live in the uploads folder, which inboxes receive copies, who can export CSV intakes next to owner identities, and how long past intakes, files, and backups are kept after the consult ends. Notification emails can also copy the same household identity and incident answers off-site. Ask your web vendor not to put every incident detail next to an owner name on one open table when a short intake ID would do — and ask how long last year's bite-history rows are kept.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the dog-behaviorist intake page. That page request can reach a vendor host before anyone submits. Review which tags you enable, account access, and retention there. Keep marketing tags off intake and booking pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or who exported the intakes. A "confidential client records" badge is not a verified storage or visibility path.

Dog-behaviorist bite-history intake, session booking, 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 dog-behaviorist 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 behavior consult or follow-up session is a booking you create; a service name such as aggression assessment or muzzle training is a label you configure. Neither is a documented default. Bite-history, severity, prior-victim, muzzle-history, or quarantine questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof an incident occurred — and a CSV export of intakes next to owner identities is the sheet that leaves with whoever can open admin. Emails can include those custom fields. 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.

Behavior-consult and follow-up session 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. Bite-history, incident-date, prior-victim, severity, has-bitten-before, muzzle-history, quarantine, or owner-contact questions are fields you add; they are not documented defaults. A vet-record, quarantine letter, or incident photo/video upload is a file you accept; it is not a documented default. One owner-authored entry can store every incident detail next to a household identity — and the same row that holds "has bitten before" also names a third party who never saw the form. An intake answer is not a legal admission and not proof an incident occurred. Ask how long intakes are kept and who can export them: retention length is subpoena exposure, not housekeeping. 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.

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 bite history, prior-victim description, or severity answer was sent. A page request from this script on a dog-behaviorist intake page is not proof a bite history was collected — and a pre-consent tag on that page can still treat dog-behaviorist intake intent as an audience segment from the URL alone. The page URL can say dog behaviorist even when no form is submitted. Consent timing has not been tested. Review which tags you enable on intake 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. Bite-history answers, severity scales, prior-victim descriptions, muzzle history, or quarantine notes often depend on the fields you configure. An intake answer is not a legal admission and not proof an incident occurred. A marketing-tag page request is not proof a bite history was collected. Ending the consult later does not erase the incident dates already stored next to an owner name — and last year's intake may still be the exhibit. Ask your web vendor who can open entries, who can export intakes, where uploaded files live, whether a marketing tag loads on the intake page, and how long past intakes and backups are kept. A "confidential client records" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and intake-export paths only and does not assess dog-bite law, strict-liability doctrine, breed legislation, insurance exclusions, or litigation outcomes. Review stored records, bookings, connected services, exports, notification emails, marketing tags on intake 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-dog-behaviorist-plugin-privacy