Tutoring student-profile privacy

The student profile behind the lesson booking

Tutoring and learning-center sites on WordPress can use booking or tutor-management plugins for lesson requests, student profiles, and homework notes. Those records can include a student name, age or grade, parent contact, learning notes, and progress history you configure — often for minors. This sample reviews three plugins' documentation. Check which fields you collect, who can open records, where vendor hosts store class or payment data, and how long student or lesson rows and backups are kept.

Documentation review only. This is not legal advice and is not a COPPA, FERPA, GDPR, or other compliance assessment.

Scan your site for third-party requests

The scan checks browser requests on the pages it visits. It cannot inspect student profiles, lesson records, staff permissions, vendor accounts, or backups.

Where tutoring student profiles are stored

Profiles stored on your WordPress site

Check which student or lesson fields you enable, who can open entries, and how long records and backups are kept. Lesson request, confirmation, and reminder emails can also copy the same details — or reveal a tutoring relationship — off-site.

Profiles or payments handled by a vendor

Some tools send class schedule or payment data into Zoom, Stripe, or another vendor when you enable those connectors. Review access and retention there. A browser scan cannot inspect those stored submissions.

Tutoring lesson-booking 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 tutoring-marketplace SaaS tools without a WordPress.org listing are outside this sample.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Marivya Tutor Manager

Documented self-hosted tutor workspace (plugin version 1.8.3). The listing states student profiles hold contact details, subject, level, hourly rate, status, and notes; lessons hold date, time, duration, status, meeting link, notes, and homework; materials can attach to a student. A student portal uses magic links or PINs without WordPress accounts. The privacy section states no tutoring data is sent to Marivya or another external service and that student, lesson, and material records remain in the WordPress database, with WordPress personal-data export and erase hooks. Age/grade or parent-contact fields beyond the listed contact and level fields depend on what you enter in notes — they are not fixed tutoring defaults. Retention of student or lesson rows after unenrollment is not specified as a default purge. Public portal browser hosts are unverified.

Student profiles, lessons, and homework stored in WordPressBrowser hosts not verifiedNot assessedNot tested
  • None
TutorHelper Bookings

Documented tutor lesson-booking Core plugin (version 1.1.0). Registered TutorHelper students request available lessons; tutors confirm from the Booking Hub; students see pending, upcoming, cancelled, and previous lessons on a dashboard. The listing states Core booking and availability information is stored within the WordPress database and that Core does not require or automatically send booking information to an external TutorHelper booking service. Request, confirmation, and cancellation emails can copy booking details off-site. Which student-profile fields beyond the registered account (age/grade, parent contact, learning notes) you keep depends on how you manage student records — they are not established as fixed tutoring defaults by the listing. Retention of booking history after cancellation is not assessed here. Public booking-form browser hosts are unverified.

Lesson requests and student bookings stored in WordPressBrowser hosts not verifiedNot assessedNot tested
  • None
Unified Private Class LMS (Zoom + Stripe enabled)

Documented private-tutor / small-academy class plugin (version 1.5.0) with teacher and student front-end dashboards, recurring weekly sessions, materials, and payment tracking. Without credentials it can run as a standalone on-site scheduler; this row reviews the documented Zoom + Stripe path when those integrations are configured. Zoom (server-to-server OAuth) receives class title/agenda, schedule, and recurrence at zoom.us/oauth/token and api.zoom.us/v2. Stripe receives student name and email for customers, prices, and subscriptions; the student browser is redirected to Stripe hosted Checkout at checkout.stripe.com. Class, session, and billing tables still live on the WordPress host by default. Age/grade or parent-contact fields are not established as fixed tutoring defaults. Retention of class or billing rows is not assessed here. Zoom API hosts are server-side, not visitor-browser endpoints in this snapshot.

Class roster and payments handled through Zoom and Stripe when enabledcheckout.stripe.comNot assessedNot tested
  • None

What this table does and does not prove

This is a documentation review, not a test of your site. Age, grade, parent-contact, or learning-note fields often depend on what you configure. Consent timing, access controls, and retention have not been tested. This page describes storage paths only and does not assess legal compliance status. Review stored student records, connected services, exports, notification emails, and backups.

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

Related pages

Scan your site for third-party requests

/wp-tutoring-plugin-privacy