Public adjuster plugin privacy
The claim intake that inventories everything you lost while you're still in the hotel
A public adjuster's site can look like a calendar and a short intake form. The same form often asks what caused the loss, the insurer and claim number, a room-by-room contents inventory, where you are living now, and whether you have prior claims — and asks for damage photos or a policy declaration page — and stores those answers next to the owner's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a damage-walkthrough booking next to a cause-of-loss narrative, an insurer-and-claim-number pair, a priced contents inventory typed from a hotel lobby, and a marketing pixel — the claim intake that inventories everything you lost while you're still in the hotel, typed once into a vendor table next to a newsletter signup. A claim intake is an inquiry, not a coverage determination. A cause-of-loss narrative is the policyholder's account, not an adjuster's finding. A contents inventory is what the owner recalls and values, not an appraisal. An uploaded declaration page is a stored client document, not proof of coverage. A prior-claims answer is self-report, not a claims-history database. A page request is not proof anyone suffered a loss. The page URL can say public-adjuster even when no form is submitted. Ask what happens to the damage photos and contents-inventory rows after the claim engagement closes — the quietest field is the inventory itself, a priced catalog of a household's entire material life next to a hotel address. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the intake page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a claim about insurance or claims-handling law, an adjuster-licensing claim, a settlement-outcome claim, a carrier-conduct claim, a policy-interpretation claim, a claim about the firm's data-security practices, a provider-quality 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, bookings, uploaded files, email inboxes, staff permissions, vendor accounts, or backups.
Where damage-walkthrough bookings, contents-inventory uploads, and page tags go
Bookings and notes on your WordPress site
Check which cause-of-loss, insurer-and-claim-number, contents-inventory, current-living-situation, or prior-claims-question fields you enable, who can open form entries and damage-walkthrough or claim-review bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a claim engagement closes — when the claim intake that inventories everything you lost while you're still in the hotel. Notification emails can also copy those fields off-site. One table can list every Tuesday walkthrough next to a damage-photo ZIP and a declaration PDF. Ask your web vendor not to keep damage-photo or policy-declaration uploads next to plaintext cause-of-loss and contents-inventory rows in one open submissions list longer than operations need, and to purge intake rows when the engagement closes. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not a coverage determination. A contents inventory in a form table is not an appraisal.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the public-adjuster damage-walkthrough or intake page. That page request can reach a vendor host before anyone submits. The page URL can say public-adjuster even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off damage-walkthrough, claim-review, and public-adjuster intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted claims advocate" badge is not a verified storage path.
Damage-walkthrough / claim-review booking, public-adjuster intake, 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 claims-adjusting 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 Tuesday damage walkthrough or a claim-review slot is a booking you create; a service name such as damage walkthrough or claim review is a label you configure. Neither is a documented default. Cause-of-loss, insurer-and-claim-number, contents-inventory, current-living-situation, or prior-claims questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry, not a coverage determination — and a CSV export of a damage-walkthrough row next to an insurer-and-claim-number and a contents-inventory note is still a calendar that holds a priced household catalog beside a contact name. 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. | Damage-walkthrough and claim-review 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. Cause-of-loss, insurer-and-claim-number, contents-inventory, current-living-situation, or prior-claims fields are fields you add; they are not documented defaults. Completing the form can store a cause-of-loss narrative next to an insurer and claim number, a room-by-room contents inventory, a current-living-situation note (hotel, family, temporary housing), a prior-claims answer, and optional damage-photo or policy-declaration uploads — typed once as the claim intake that inventories everything you lost while you're still in the hotel, into the same tables as a newsletter signup. A claim intake is an inquiry, not a coverage determination. A cause-of-loss narrative is the policyholder's account, not an adjuster's finding. A contents inventory is what the owner recalls and values, not an appraisal. An uploaded declaration page is a client document, not proof of coverage — and a staff login can open "kitchen fire 10/3, Acme Mutual claim 448291, living-room TV $800 / bedroom dresser $200 / jewelry missing, hotel on I-10, prior claim 2021 wind, damage-photos.zip, declaration.pdf" next to everyone else's resume. A prior-claims answer is self-report, not a claims-history database. 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. | Public-adjuster intake entries stored in WordPress; optional damage-photo and policy-declaration 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 cause-of-loss, insurer-and-claim-number, contents-inventory, current-living-situation, or prior-claims field was sent. A page request from this script is not proof anyone suffered a loss. The page URL can say public-adjuster even when no form is submitted. Consent timing has not been tested. Review which tags you enable on damage-walkthrough, claim-review, and public-adjuster intake 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. Cause-of-loss, insurer-and-claim-number, contents-inventory, current-living-situation, or prior-claims-question fields often depend on the fields you configure. A claim intake is an inquiry, not a coverage determination. A cause-of-loss narrative is the policyholder's account, not an adjuster's finding. A contents inventory is what the owner recalls and values, not an appraisal. An uploaded declaration page is a stored client document, not proof of coverage. A prior-claims answer is self-report, not a claims-history database. A marketing-tag page request is not proof anyone suffered a loss. The page URL can say public-adjuster even when no form is submitted. The claim intake that inventories everything you lost while you're still in the hotel — that is a storage path next to a damage-photo ZIP, not a feature these plugins claim. This page is about that public-adjuster intake, not a restoration cleanup crew, a home-inspection defect list, a crime-scene-cleanup form, or a hoarding-cleanup inventory. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long contents-inventory rows and backups are kept after the engagement closes. A "trusted claims advocate" 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 insurance or claims-handling law, adjuster licensing, settlement outcomes, carrier conduct, policy interpretation, the firm's data-security practices, or provider quality. 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
- WordPress booking plugin privacy
- WordPress file upload plugin privacy
- WordPress ads plugin privacy
- All privacy guides
/wp-public-adjuster-plugin-privacy