Dog grooming plugin privacy
The grooming card that logs the bite history, the meds, and your empty Tuesdays
A dog-grooming WordPress stack is not only a standing appointment calendar — it is often a household dossier. Every confirmed card can store bite history, medication lists, vaccination uploads, vet name, behavioral notes, and a recurring every-other-Tuesday slot that proves when the house is empty. The intake follows the dog (and owner) around town; the rota publishes the weeks nobody is home. A page request is not proof anyone booked. A vaccine file is a stored upload, not a medical record claim. A bite note is stored text, not a temperament diagnosis. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where vaccine files land, which inboxes receive copies, and how long past bookings, files, and backups are kept.
Documentation review only. This is not legal advice, a veterinary claim, a pet-sitting claim, a dog-boarding claim, a burglary-risk claim, a GDPR or other compliance assessment, or a judgment about dog groomers.
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 bite notes, vaccine files, and grooming rotas go
Entries, bookings, and uploads on your WordPress site
Check which bite-history, medication-list, vaccine-upload, vet-name, behavioral-note, standing-slot, owner-absence, or booking fields you enable, who can open form entries and recurring appointments, where uploaded vaccine files live in the uploads folder, which inboxes receive copies, and how long past cards, files, and backups are kept after a groom that never happened. Notification emails can also copy the same meds, bite notes, and file links off-site.
Uploads or connected destinations off your WordPress site
Some upload tools can send files to FTP, SFTP, or cloud destinations you enable. Review which destinations you turn on, account access, and retention there. A browser scan cannot inspect stored form entries, bookings, or who opened the grooming calendar. A "cage-free salon" badge is not a verified storage path.
Dog-grooming booking, vaccine-upload, and bite-history 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 grooming SaaS platforms without a WordPress.org listing are 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). WordPress admin screens cover locations, services, workers, an appointments list, a customer list, custom form fields, and CSV export. A standing slot or a "every other Tue 10am — bite history yes — meds: apoquel" access note is a booking you create; a service name such as dog grooming is a label you configure. Neither is a documented default. Bite-history, medication-list, vaccine-upload, vet-name, behavioral-note, standing-slot, or owner-absence questions are custom fields you add; they are not documented defaults. A booking is a calendar row, not proof of a groom — and a CSV export of "Tue 10am + bite history + meds" next to a named owner is still a calendar that publishes when the house is empty. 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. | Dog-grooming 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. Bite-history, medication-list, vaccine-upload, vet-name, behavioral-note, standing-slot, owner-absence, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional vaccine uploads are files you accept; that file type is not a documented default. A vaccine file is a stored upload, not a medical record claim. A bite note is stored text, not a temperament diagnosis. A dog-grooming form is not proof anyone groomed a dog. 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 a record sits after a groom that never happened is not a documented default of the plugin. | Bite-history and med answers stored in WordPress; optional vaccine uploads in the site uploads/forminator folder | Browser hosts not verified | Not assessed | Not tested |
| |
| Iptanus File Upload Documented frontend upload form (formerly WordPress File Upload). By default files land inside the wp-content directory of the site; the upload path is configurable. Uploaded files can be added to Media or attached to the current page. FTP and SFTP destinations are documented. The Professional version documents uploads to Google Drive, Dropbox, OneDrive, or Amazon S3. A vaccine file is a file you accept; that file type is not a documented default. An uploaded vaccine file is a stored file, not a veterinary claim. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enable. The listing claims GDPR compliance without a tested EXIF-strip or retention length here. Review upload directory, Media attachment, and cloud destinations. Browser hosts for the visitor upload path were not verified for this snapshot. How long a file sits after a groom that never happened is not a documented default of the plugin. | Vaccine and document uploads stored under the site wp-content path | Browser hosts not verified | Not assessed | Not tested |
|
What this table does and does not prove
This is a documentation review, not a test of your site. Bite-history, medication-list, vaccine-upload, standing-slot, owner-absence fields often depend on the fields you configure. A vaccine file is a stored upload, not a medical record claim. A bite note is stored text, not a temperament diagnosis. A dog-grooming booking is not proof anyone groomed a dog. A page request is not proof anyone booked. The page URL can say dog grooming even when no form is submitted. Ask your web vendor who can open entries and uploads, whether photos remain reachable by direct URL, and how long records and backups are kept. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess veterinary, pet-sitting, dog-boarding, burglary-risk. Review stored records, uploaded photos, connected services, exports, notification emails, and backups.
Documentation snapshot: Oct 20, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress booking plugin privacy
- WordPress forms privacy
- WordPress payment gateway privacy
- All privacy guides
/wp-dog-grooming-plugin-privacy