Animal rescue plugin privacy
An adoption application can audit your home and your schedule
A rescue adoption application can store landlord name and phone, own-or-rent status, household members and their ages, work hours, hours nobody is home, yard and fence details, vet references, and what happened to prior pets in the same WordPress table. Applicants type this in on a volunteer-run site to prove they are good enough for a dog. A shared staff login can open a dossier about housing and daily absence. A marketing tag on the application page can send a page request to a vendor host before anyone submits. The page URL can say adopt. A page request is not proof that an application was submitted. A submitted application is not a background check and is not an approved placement. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and files, which tags load on the application page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, an animal-welfare-law claim, a charity-status claim, an adoption-outcome claim, 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, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where home details, schedules, and page tags go
Applications and files handled on your WordPress site
Check which landlord, household, schedule, yard, vet-reference, or prior-pet fields you enable, who can open form entries, which inboxes receive copies, and how long records, emails, and backups are kept. Notification emails can also copy the same answers off-site. One entry can store the applicant next to a landlord, household members, and a vet even when only the applicant typed. Ask your web vendor not to collect landlord phones, household ages, or hours nobody is home on a public form, not to accept home photos, lease scans, or ID scans on a public application page, and to purge applications that never became placements. A privacy-policy page does not by itself limit who can open an application list.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the application page. That page request can reach a vendor host before anyone submits. The page URL can say adopt even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off application pages if you do not want that page request. A browser scan cannot inspect stored applications. A "secure application" badge is not a verified storage path.
Animal-rescue application, upload, 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 rescue-management software without a WordPress.org listing is outside this sample.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| Drag and Drop Multiple File Upload for Contact Form 7 Documented Contact Form 7 upload extension (plugin version 1.4.0). Version 1.4.0 drag-n-drop-upload-cf7.php defines wpcf7_dnd_dir as wp_dndcf7_uploads. The listing states the free version moves files to wp-content/uploads/wp_dndcf7_uploads, attaches them to mail, then removes them from that temporary folder about one hour after submission. That cleanup does not remove copies already sent as email attachments. Home photos, fence photos, lease scans, or ID scans are files you accept; they are not documented defaults. An uploaded home photo is not a home visit. An uploaded lease is not a background check. Pro documents saving to the Media Library, changing the upload directory, auto-delete timers, and remote storage to OneDrive, Google Drive, Amazon S3, Dropbox, or FTP. Public upload-page browser hosts are unverified. | Visitor files stored under wp-content/uploads/wp_dndcf7_uploads | 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 plus payment-form options. 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. Landlord-name, landlord-phone, own-or-rent, household-member, household-age, work-schedule, hours-nobody-is-home, yard, fence, vet-reference, or prior-pet fields are fields you add; they are not documented defaults. One form entry can store the applicant next to a landlord phone, household ages, and hours the house sits empty. Those other people never consented and never visited the site. Completing the form can record an adoption inquiry. A submitted application is not a background check and is not an approved placement. A volunteer staff login can open that dossier in the same submissions list. Notification emails can copy field values 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 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 application answers or landlord fields were sent. A page request from this script is not proof that an application was submitted. The page URL can say adopt even when no form is submitted. Consent timing has not been tested. Review which tags you enable on application 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. Landlord, household, schedule, yard, vet-reference, or prior-pet fields often depend on the fields you configure. The listed landlord, household members, and vet never consented and never visited the site. A submitted application is not a background check and is not an approved placement. An uploaded home photo is not a home visit. A marketing-tag page request is not proof that an application was submitted. The page URL can say adopt even when no form is submitted. Ask your web vendor who can open entries, where uploaded files live, whether a marketing tag loads on the application page, and how long records and backups are kept. A "secure" or "application portal" 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 animal-welfare law, charity status, or adoption outcomes. Review stored records, uploaded files, connected services, exports, notification emails, marketing tags on application pages, and backups.
Documentation snapshot: Oct 13, 2026. Sources are linked in each reviewed row.
Related pages
- WordPress veterinary plugin privacy
- WordPress volunteer plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-animal-rescue-plugin-privacy