College consultant plugin privacy
The intake that files the family's ambition next to its bank balance
An independent college consultant's site can look like a calendar and a short new-family form. The same form often asks for a student's name and grade, GPA and test scores, a target-school list with reach and safety labels, disciplinary history, and a budget range — and asks for a transcript and an activities resume — and stores those answers next to the parent's contact for the life of the form table. Those fields are configured, not documented defaults. One WordPress row can hold a strategy-session booking next to a GPA claim, a reach/safety school ranking, a disciplinary-history note, a budget-range answer, and a marketing pixel — the intake that files the family's ambition next to its bank balance, typed once into a vendor table next to a newsletter signup. A strategy-session booking is an inquiry, not an engagement. A GPA typed by a parent is a claim, not a school record. An uploaded transcript is a stored client document, not a verified academic file. A disciplinary-history answer is the family's account, not the school's. A budget range is what the parent chose to disclose, not a financial statement. The student named rarely touched the form. A page request is not proof any child is applying anywhere. The page URL can say college-consultant even when no form is submitted. Ask what happens to the transcripts and target-school rows after the family leaves — the quietest field is the target-school list with its reach/safety labels, a written ranking of how far the family believes the child can go, stored before the student has heard of half the schools. 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, an admissions-outcomes or acceptance-odds claim, a financial-aid or FAFSA-rules claim, a test-prep-efficacy claim, a consultant-certification claim, a claim about the consultant'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 strategy-session bookings, college-consultant intake, and page tags go
Bookings and notes on your WordPress site
Check which student-name-and-grade, gpa-and-test-scores, target-schools, disciplinary-history, or budget-range fields you enable, who can open form entries and strategy-session or application-review bookings, which inboxes receive copies, and how long records, emails, and backups are kept after a family leaves — when the intake that files the family's ambition next to its bank balance. Notification emails can also copy those fields off-site. One table can list every strategy session next to a transcript upload and a budget-range answer. Ask your web vendor not to keep transcript uploads next to plaintext GPA, target-school, disciplinary-history, and budget-range rows in one open submissions list longer than operations need, and to purge intake rows when the consulting relationship ends. A privacy-policy page does not by itself limit who can open a submissions list. A stored booking is not an engagement. A GPA in a form table is not a school record the plugin claims to verify.
Page tags handled by a vendor
Some marketing-tag tools load a vendor script when a visitor opens the college-consultant strategy-session or intake page. That page request can reach a vendor host before anyone submits. The page URL can say college-consultant even when no form is submitted. Review which tags you enable, account access, and retention there. Keep marketing tags off strategy-session, application-review, and college-consultant intake pages if you do not want that page request. A browser scan cannot inspect stored entries or bookings. A "trusted admissions partner" badge is not a verified storage path.
Strategy-session / application-review booking, college-consultant 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 admissions-consulting 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 strategy-session or an application-review slot is a booking you create; a service name such as strategy session or application review is a label you configure. Neither is a documented default. Student-name-and-grade, gpa-and-test-scores, target-schools, disciplinary-history, or budget-range questions are custom fields you add (textarea, select, input, or checkbox); they are not documented defaults. A booking is an inquiry calendar row, not an engagement — and a CSV export of a strategy-session row next to a student name and a budget note is still a calendar that holds ambition beside a bank-balance field. 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. | Strategy-session and application-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. Student-name-and-grade, gpa-and-test-scores, target-schools, disciplinary-history, or budget-range fields are fields you add; they are not documented defaults. Completing the form can store a GPA and test-score claim next to a student name and grade, a target-school list with reach/safety labels, a disciplinary-history note, a budget-range answer, and optional transcript and activities-resume uploads — typed once as the intake that files the family's ambition next to its bank balance, into the same tables as a newsletter signup. A GPA typed by a parent is a claim, not a school record. An uploaded transcript is a stored client document, not a verified academic file. A disciplinary-history answer is the family's account, not the school's. A budget range is what the parent chose to disclose, not a financial statement — and a staff login can open "Jordan, grade 11, 3.6 GPA, 1380 SAT, reach UMich / target IU / safety State, one suspension sophomore year, budget $35k/year, transcript.pdf, activities.docx" next to everyone else's resume. The student named rarely touched the form. 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. | College-consultant intake stored in WordPress; optional transcript and activities-resume 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 student-name-and-grade, gpa-and-test-scores, target-schools, disciplinary-history, or budget-range field was sent. A page request from this script is not proof any child is applying anywhere. The page URL can say college-consultant even when no form is submitted. Consent timing has not been tested. Review which tags you enable on strategy-session, application-review, and college-consultant 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. Student-name-and-grade, gpa-and-test-scores, target-schools, disciplinary-history, or budget-range fields often depend on the fields you configure. A strategy-session booking is an inquiry, not an engagement. A GPA typed by a parent is a claim, not a school record. An uploaded transcript is a stored client document, not a verified academic file. A disciplinary-history answer is the family's account, not the school's. A budget range is what the parent chose to disclose, not a financial statement. The student named rarely touched the form. A marketing-tag page request is not proof any child is applying anywhere. The page URL can say college-consultant even when no form is submitted. The intake that files the family's ambition next to its bank balance — that is a storage path next to a transcript upload, not a feature these plugins claim. This page is about that college-consultant intake, not a scholarship-application essay, a tutoring student profile, or a special-education-advocate school file. Ask your web vendor who can open entries, whether a marketing tag loads on the intake page, and how long target-school and budget rows and backups are kept after the family leaves. A "trusted admissions partner" 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 admissions outcomes or acceptance odds, financial-aid or FAFSA rules, test-prep efficacy, consultant certification, the consultant'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-college-consultant-plugin-privacy