Personal chef plugin privacy

The intake that pairs your food allergies with your gate code

A personal-chef WordPress stack is not only a menu planner — it is often a dietary intake stapled to a home-access kit. Every confirmed booking can store allergy and medical-diet notes next to a gate code, alarm workaround, spare-key location, and the weekly hours the family is home to eat. No clinic protections required for that pairing to sit in a forms table. A page request is not proof anyone booked. An allergy answer is a stored note, not a diagnosis. A gate code is stored text, not proof anyone entered. This sample reviews three plugins' documentation. Check which visitor fields you collect, who can open entries, where uploaded diet plans land, which inboxes receive copies, and how long past intakes, bookings, and backups are kept.

Documentation review only. This is not legal advice, medical advice, a HIPAA claim, a nutrition-outcome claim, a GDPR or other compliance assessment, or a judgment about chefs.

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

Where dietary intakes, home-access notes, and bookings go

Entries, bookings, and uploads on your WordPress site

Check which allergy, medical-diet, medication, gate-code, alarm, spare-key, or home-schedule fields you enable, who can open form entries and cook-in bookings, where uploaded diet plans live in the uploads folder, which inboxes receive copies, and how long past intakes, files, and backups are kept after a cooking week that never started. Notification emails can also copy the same client identity and access notes 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 weekly cook calendar. A "private chef kitchen" badge is not a verified storage path.

Personal-chef dietary intake, home-access booking, and upload 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 chef SaaS platforms without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Easy Appointments

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 diet plan or medical note is a file you accept; that file type is not a documented default. An uploaded file is a stored file, not a diagnosis. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. 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.

Diet-plan or medical-note uploads stored under the site wp-content pathBrowser 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. Reason-for-appraisal, rush-order, access-instructions, lockbox-code, owner-at-work, property-address, owner-name, phone, or email questions are fields you add; they are not documented defaults. Optional interior-photo or document uploads are files you accept; those file types are not documented defaults. A reason-for-appraisal answer is a stored select, not proof a divorce was filed. A rush order is a stored priority label, not proof a crisis happened. An interior-photo upload is a stored file, not a valuation. Access instructions are stored text, not proof anyone entered the home. A personal-chef form is not proof anyone completed an appraisal. 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 pairing sits after an appraisal that never happened is not a documented default of the plugin.

Appraisal intake and reason-for-appraisal entries stored in WordPress; optional uploads in the site uploads/forminator folderBrowser hosts not verifiedNot assessedNot tested
  • None
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. An interior photo, floor plan, or prior appraisal PDF is a file you accept; that file type is not a documented default. An uploaded interior photo is a stored file, not a valuation. Deleting a form entry later does not by itself prove the file was removed from the uploads path or from a cloud destination you enabled. 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 an interior-photo file sits after an appraisal that never happened is not a documented default of the plugin.

Interior-photo and document uploads stored under the site wp-content pathBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Allergy, medical-diet, medication, gate-code, alarm, spare-key, or home-schedule fields often depend on the fields you configure. An allergy answer is a stored note, not a diagnosis. A gate code is stored text, not proof anyone entered. A personal-chef booking is not proof anyone cooked. A page request is not proof anyone booked. The page URL can say personal chef even when no form is submitted. Ask your web vendor who can open entries and uploads, whether diet-plan files 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 medical advice, HIPAA, or nutrition outcomes. Review stored records, uploaded files, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-personal-chef-plugin-privacy