Bookkeeping plugin privacy
The catch-up request that dates how long the books have been a secret
A bookkeeping firm's site can look like a calendar and a short catch-up form. The same form often asks how many months behind you are, what monthly revenue looks like, why you are switching, which software you use, and whether you got an IRS letter — and asks for a bank statement or a prior-year P&L — 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 discovery-call booking next to a months-behind confession, a bank-statement PDF with every payee for a year, and a marketing pixel — the catch-up request that dates how long the books have been a secret, typed once into a vendor table next to a newsletter signup. A months-behind answer is the owner's estimate, not an audit finding. A monthly-revenue figure is what the prospect typed, not a verified financial statement. An IRS-letter checkbox is a disclosure of mail received, not of wrongdoing. An uploaded bank statement is a stored client document, not the bookkeeper's work product. Payees in a statement are third parties who never consented to the upload. A discovery-call booking is an inquiry, not an engagement. A page request is not proof any business is behind on its books. The page URL can say bookkeeping even when no form is submitted. Ask what happens to the bank statements and months-behind answers after the engagement closes — the quietest fields are the reason-for-switching note and the IRS-letter checkbox that turn a cleanup lead into an audit disclosure. This sample reviews three plugins' documentation. Check which fields you collect, who can open entries and bookings, which tags load on the catch-up page, and how long records, emails, and backups are kept.
Documentation review only. This is not legal advice, a claim about tax law or IRS compliance, a CPA or licensure claim, an audit-outcome 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 discovery-call bookings, bank-statement uploads, and page tags go
Bookings and notes on your WordPress site
Check which months-behind, monthly-revenue, reason-for-switching, software-used, or irs-letter-question fields you enable, who can open form entries and discovery-call or monthly-close-review bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a catch-up engagement closes — when the catch-up request that dates how long the books have been a secret. Notification emails can also copy those fields off-site. One table can list every Tuesday discovery call next to a bank-statement PDF and a prior-year P&L. Ask your web vendor not to keep bank-statement or prior-year-P&L uploads next to plaintext months-behind and revenue 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 an engagement. A months-behind answer in a form table is not an audit finding.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the bookkeeping discovery-call or catch-up page. That page request can reach a vendor host before anyone submits. The page URL can say bookkeeping even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off discovery-call, monthly-close-review, and catch-up pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted books" badge is not a verified storage path.
Discovery-call / monthly-close-review booking, catch-up 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 bookkeeping 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 discovery call or a monthly-close-review slot is a booking you create; a service name such as catch-up consult or monthly close review is a label you configure. Neither is a documented default. Months-behind, monthly-revenue, reason-for-switching, software-used, or irs-letter questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry, not an engagement — and a CSV export of a discovery-call row next to a months-behind and a reason-for-switching note is still a calendar that holds a solvency confession 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. | Discovery-call and monthly-close-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. Months-behind, monthly-revenue, reason-for-switching, software-used, or irs-letter-question fields are fields you add; they are not documented defaults. Completing the form can store a months-behind answer next to a monthly-revenue figure, a reason-for-switching note, a software-used answer, an IRS-letter checkbox, and optional bank-statement or prior-year-P&L uploads — typed once as the catch-up request that dates how long the books have been a secret, into the same tables as a newsletter signup. A months-behind answer is the owner's estimate, not an audit finding. A monthly-revenue figure is what the prospect typed, not a verified financial statement. An IRS-letter checkbox is a disclosure of mail received, not of wrongdoing. An uploaded bank statement is a stored client document, not the bookkeeper's work product — and a staff login can open "Acme LLC, 14 months behind, ~$40k/mo, got an IRS letter, QuickBooks Desktop, bank-statement.pdf with every payee for a year, prior-year P&L" next to everyone else's resume. Payees in a statement are third parties who never consented to the upload. 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. | Catch-up intake entries stored in WordPress; optional bank-statement and prior-year-P&L 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 months-behind, monthly-revenue, reason-for-switching, software-used, or irs-letter field was sent. A page request from this script is not proof any business is behind on its books. The page URL can say bookkeeping even when no form is submitted. Consent timing has not been tested. Review which tags you enable on discovery-call, monthly-close-review, and catch-up 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. Months-behind, monthly-revenue, reason-for-switching, software-used, or irs-letter-question fields often depend on the fields you configure. A months-behind answer is the owner's estimate, not an audit finding. A monthly-revenue figure is what the prospect typed, not a verified financial statement. An IRS-letter checkbox is a disclosure of mail received, not of wrongdoing. An uploaded bank statement is a stored client document, not the bookkeeper's work product. Payees in a statement are third parties who never consented to the upload. A discovery-call booking is an inquiry, not an engagement. A marketing-tag page request is not proof any business is behind on its books. The page URL can say bookkeeping even when no form is submitted. The catch-up request that dates how long the books have been a secret — that is a storage path next to a bank-statement PDF, not a feature these plugins claim. This page is about that bookkeeping catch-up intake, not a tax-preparer SSN folder, a payroll-service staff roster, or a bankruptcy-attorney distress form. Ask your web vendor who can open entries, whether a marketing tag loads on the catch-up page, and how long bank-statement rows and backups are kept after the engagement closes. A "trusted books" 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 tax law or IRS compliance, CPA/licensure status, audit outcomes, the firm's data-security practices, or provider quality. Review stored records, bookings, connected services, exports, notification emails, marketing tags on catch-up 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-bookkeeping-plugin-privacy