Privacy policy
This policy describes what personal data TutMeet (operated by TutMeet) processes, why, and the choices you have. It describes what the system actually does.
Data we collect
- Account data: name, email address, hashed password (never stored in plain text), role (student/tutor), optional country, currency and time zone preferences, and — if you provide it — your phone / WhatsApp number (see “Phone numbers” below).
- Profile data (tutors): headline, biography, subjects, levels, languages, rate, city/country and profile status — the parts marked public appear on your public profile once approved.
- Marketplace data: job posts, applications, messages between users, trial booking requests and reviews.
- Verification data: email verification and password-reset tokens are stored only as hashes with an expiry time.
- Technical data: basic logs needed to run and secure the service, and the cookies described in our cookie policy.
We do not collect payment card details or process payments on this website. Teachers who request Credits pay the academy directly (outside this website); an administrator confirms the payment and records the credit grant — the only payment-related data we store is the credit request, its status and the ledger entries in the teacher's wallet.
How we use it
- To create and secure your account, verify your email and let you reset your password.
- To operate the marketplace: publishing approved profiles and jobs, matching applications, delivering messages and trial requests.
- To review profiles, moderate content, prevent spam and abuse, and respond to reports.
- To send transactional email (verification, password reset and important account notices) where an email service is configured.
We do not sell personal data, and we do not use marketplace messages for advertising.
What is public
An approved tutor's public profile (name, headline, biography, subjects, rate, location and reviews) is visible to anyone. Job posts show the posting student's first name and the job details. Messages are visible only to the participants in that conversation and, where needed for moderation or safety, to administrators.
Phone numbers — shared only after an application
Phone numbers are never public on TutMeet: they do not appear on profiles, job pages, search results or any public page. They are shared in exactly one situation:
- When a student posts a job, they give a contact number for that job. That number is revealed only to teachers who apply to that job — after their application (a teacher's first application is free; later ones cost credits, which is part of how we stop numbers being harvested by unknown accounts).
- A teacher's number is likewise shown only to a student whose job that teacher has applied to.
- The owner of the account and platform administrators can also see the relevant numbers for operating and moderating the marketplace. If you do not want a number shared this way, do not add it — but a job cannot be published without a contact number, because applied teachers need a way to reach the student.
Administrator access to conversations
Platform administrators may review any conversation on TutMeet for safety, moderation and dispute resolution. This access is read-only — administrators cannot post in your conversations — and every time an administrator opens a conversation, the view is recorded in the platform's audit log with the administrator's identity.
Children
Accounts are held by adults only. We do not knowingly collect a child's name, date of birth, photo or contact details; a parent account may record only a learner age range where the product asks for it.
Retention and your choices
- Account data is kept while your account is active. You may ask us to export or delete your data via the contact page.
- Deletion requests are reviewed by an administrator. Some records (for example a review or message that another user relies on) may be anonymised rather than erased where retention is necessary for the other party or for moderation records.
- Expired verification and reset tokens are purged.
Security
Passwords are hashed, sessions use signed, http-only cookies, and access to private data is checked on the server for every request. No system is perfectly secure, but we design and review the service with that standard in mind. Questions about this policy: contact us.