Aquarium maintenance plugin privacy

The service schedule that admits a stranger into the house every week

An aquarium-maintenance WordPress stack is not only a list of tanks — it is a standing appointment inside the home. Every confirmed subscription dates the same weekday and hour a non-resident is expected at the front door, and the same row often holds the gate code, lockbox, access notes, and whether anyone is home. No breach required: the booking is the product and the leak. Last year's visit calendar is still a map of when that door opens for service. A marketing tag on the same booking page can send a page request to a vendor host before anyone submits — and that page request alone can treat aquarium-maintenance booking intent as an audience segment from the URL. A page request is not proof anyone booked. A booking is not proof anyone entered. An access note is a field you configure, not a default. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded files land, which techs sync the calendar, which tags load on the booking page, and how long past bookings, files, and backups are kept.

Documentation review only. This is not legal advice, a burglary-risk claim, an insurance claim, a home-security or crime-statistics assessment, a GDPR or other compliance assessment, or a judgment about service techs.

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, tech calendar syncs, email inboxes, staff permissions, vendor accounts, or backups.

Where visit bookings, access notes, and page tags go

Entries, bookings, and the visit calendar on your WordPress site

Check which gate-code, lockbox, access-note, or "anyone home?" fields you enable, who can open form entries and visit bookings, where uploaded tank or equipment photos live in the uploads folder, which inboxes receive copies, which techs sync the calendar that lists every weekly door-open for service, and how long past bookings, files, and backups are kept after the visit ends. Notification emails and phone syncs can also copy the same household identity and access notes off-site. Ask your web vendor not to put every access detail next to a standing visit window on one open calendar when a short booking ID would do — and ask how long last year's subscription rows are kept.

Page tags handled by a vendor

Some marketing-tag tools load a vendor script when a visitor opens the aquarium-maintenance booking 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 booking and intake pages if you do not want that page request. A browser scan cannot inspect stored form entries, bookings, or who synced the calendar. A "bonded tech only" badge is not a verified storage or visibility path.

Aquarium-maintenance booking, access-note 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 aquarium 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 weekly reef clean or monthly tank service is a booking you create; a service name such as saltwater maintenance or filter swap is a label you configure. Neither is a documented default. Gate-code, lockbox, access-note, or "anyone home?" questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is a schedule, not proof anyone entered — and a calendar that lists every Tuesday at 10 for the same address is the standing-access record that outlasts one visit. 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.

Recurring tank-service visit windows 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. Gate-code, lockbox, access-note, "anyone home?", emergency-contact, or preferred-visit-day questions are fields you add; they are not documented defaults. A tank photo or equipment-serial upload is a file you accept; it is not a documented default. One client-authored entry can store every access detail next to a household identity — and the same row that holds "lockbox under the planter" also holds the weekday the tech is expected. An access note is a configured field, not a default. A submitted form is not proof anyone entered. 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 gate code, lockbox note, or visit window was sent. A page request from this script on an aquarium-maintenance booking page is not proof anyone booked — and a pre-consent tag on that page can still treat aquarium-maintenance booking intent as an audience segment from the URL alone. The page URL can say aquarium maintenance even when no form is submitted. Consent timing has not been tested. Review which tags you enable on booking and intake 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. Gate codes, lockbox notes, access instructions, or "anyone home?" answers often depend on the fields you configure. A booking is not proof anyone entered. An access note is a configured field, not a default. A marketing-tag page request is not proof anyone booked. Ending the subscription later does not erase the visit windows already stored next to a household name — and last year's calendar may still show the standing pattern. Ask your web vendor who can open entries, who syncs the booking calendar, where uploaded files live, whether a marketing tag loads on the booking page, and how long past bookings and backups are kept. A "bonded tech only" badge is not a verified storage or visibility path. Consent timing, access controls, and retention have not been tested. This page describes storage and booking-calendar visibility paths only and does not assess burglary risk, insurance coverage, home-security efficacy, or crime statistics. Review stored records, bookings, connected services, exports, notification emails, marketing tags on booking pages, and backups.

Documentation snapshot: Oct 15, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-aquarium-maintenance-plugin-privacy