COMPLETE AI PROMPT INSTRUCTION: Generate the TutorMitra Platform Documentation

Role: You are a highly skilled technical documentation expert and legal compliance specialist for an EdTech startup. Your task is to create the most comprehensive, detailed, and legally sound Terms, Policies, and Rules document for "TutorMitra," an online-offline tutoring marketplace. The document must be detailed, actionable, and ready for implementation, covering every facet of the platform's operation.

Context: This is a live project with an existing codebase. The current project workspace, located at C:\Users\alc\Downloads\TutorMitra_Complete_Working\Workspace, contains client and server directories. The platform integrates React/TypeScript (frontend) and Node.js/Express (backend) with MongoDB. The system is designed to prevent "hand-to-hand" cash transactions, which is the most critical business rule.

Primary Objective: To produce a single, authoritative master document that will govern all user interactions, ensure platform security, and protect revenue. Every policy must be explained with step-by-step instructions on how it will be technically enforced within the existing application architecture.

Format & Style: Use clear, professional English. Structure the document with hierarchical headings, subheadings, and code blocks where processes are defined. Present it as a formal legal document that is still understandable to users.

---

CORE PRINCIPLES TO ENFORCE (Must be reflected throughout the document):

1. Payment is the Gatekeeper: The in-app chat, call system, and detailed contact sharing are strictly locked and only become available after a student has successfully booked and paid for a session (Trial, Demo, or Paid) through the platform's Razorpay gateway.
2. Zero-Tolerance for Off-Platform Transactions: Any attempt to bypass platform payments (cash, direct UPI, bank transfer) is the most severe violation. The system must actively detect, penalize, and eliminate this behavior.
3. Verification is Mandatory: User trust is built on verified identities. Tutor KYC is non-negotiable.
4. Platform Protection is Conditional: All platform protections (refunds, dispute resolution, safety support) are only valid for transactions processed through the official payment gateway.

---

DOCUMENT STRUCTURE TO GENERATE

Create the document with the following exact sections and content:

1. PLATFORM OVERVIEW

· Define TutorMitra as an online-offline tutoring marketplace.
· State its core functions: connecting verified tutors with students, managing the entire booking-to-payout lifecycle, offering a 3-Day Free Offline Demo, and ensuring secure payments via Razorpay.

2. ROLES AND DEFINITIONS

· Student/Parent: The consumer who books and pays for services.
· Tutor: The service provider who must complete KYC, pays a platform commission, and is subject to platform rules.
· Platform/Company: TutorMitra, responsible for the ecosystem's safety, security, and fair operation.
· Session Types: Clearly define:
· Trial Session: Paid demo class (₹39-49).
· Paid Session: Regularly scheduled, paid classes.
· Offline Demo: Free 3-day access to downloadable study materials (serves as a lead-in to paid bookings).

3. REGISTRATION & KYC POLICY (Technical Flow)

· Standard User Flow (All): Detail steps: App Download → Mobile Number Entry → OTP Verification → Email Verification → Profile Completion (Name, Location, Photo) → Account Activation.
· Tutor-Specific Flow: Detail the "Become a Tutor" path: Application → KYC Document Upload (Aadhaar Front/Back, PAN, Live Photo, Qualifications, Address Proof) → Bank/UPI Details for Payouts → 24-48 Hour Admin Review → Profile Activation.
· Strict Rules: Enforce: One account per mobile number, OTP verification is mandatory, and fraudulent data leads to immediate suspension/ban.

4. PAYMENT, REFUND, & ANTI-CIRCUMVENTION POLICY (CRITICAL SECTION)

This section must be the most detailed, explaining not just the "what" but the "how" of enforcement.

4.1. Mandatory Platform Payment Rule

· The Rule: All financial transactions MUST occur via the integrated Razorpay gateway.
· The "Why" for Students: Frame platform payment as "purchasing protection." List benefits: Eligibility for refunds, access to dispute mediation, verified transaction records, and platform safety support. Emphasize that offline payment voids all protections, leaving them at full risk.
· The "Why" for Tutors: Frame accepting platform payments as "accessing the marketplace." Explain that it ensures timely, guaranteed payouts and professional credibility. Emphasize that off-platform payments are a direct violation of their agreement and will be severely punished.

4.2. Payment Flow & Communication Lock

Provide the exact technical user journey:


1. Student selects a Tutor and clicks "Book Session."
2. Student chooses a date/time slot.
3. System redirects to the Razorpay payment page (showing amount, options: UPI/Card/NetBanking/Wallets).
4. Upon successful payment confirmation from Razorpay:
a. Booking is marked "Confirmed."
b. Confirmation notifications (SMS/Email/In-app) are sent.
c. ***THE IN-APP CHAT WINDOW FOR THAT SPECIFIC BOOKING IS AUTOMATICALLY UNLOCKED.***
d. Masked contact information (if needed for offline session coordination) may become visible.


· Technical Enforcement Note: The backend API endpoint for fetching chat messages/contact info must check the booking.payment_status field. If not "confirmed," return an empty or unauthorized response.

4.3. Off-Platform Transaction Detection & Enforcement System

Outline a multi-layered detection strategy:

1. Automated Chat Monitoring: System algorithms scan all in-app messages for keywords and patterns (/cash/, /pay outside/, /direct transfer/, /[0-9]{10}/ for phone numbers). Flagged conversations are queued for admin review.
2. User-Initiated Reporting: A prominent "Report Offline Payment Offer" button is placed within every chat window and the post-session feedback form.
3. Attendance-Payment Audit Trail: For offline sessions, mandatory QR-code/OTP check-in at the session location is logged. The system automatically flags sessions with a "completed" attendance log but no corresponding platform payment record.

4.4. Penalty Process for Violations

Define a clear, escalating penalty workflow:

· Step 1 - Detection & Investigation: Upon a credible report or system flag, admin investigates chat logs and payment records.
· Step 2 - Penalty Issuance: If a violation is confirmed:
· The involved Tutor is issued a 15% Penalty Fee on the total value of the offline transaction.
· They receive a formal notice and a Final Warning. Their profile is temporarily suspended.
· They must pay the penalty to the platform within 7 days to restore their account.
· Step 3 - Escalation for Non-Compliance: If the penalty is not paid, the tutor faces Permanent Ban, removal of their profile, and forfeiture of any earnings held by the platform.
· Step 4 - Student Consequences: The involved Student is notified that their platform protections are void for that transaction. Any related complaint or refund request is automatically invalidated.

4.5. Refund Policy

· Valid Grounds for Refund: Tutor no-show (100%), critical platform failure (100%), proven serious quality issue (evidence-based, partial/full), accidental booking (admin discretion).
· Non-Refundable: Conducted Trial sessions, Student no-shows, complaints filed >7 days post-session, and ANY payment made outside the platform.
· Refund Process: Detail the in-app complaint form flow, ticket generation, admin review timeline (3-10 business days), and possible resolutions (full/partial refund, session credit, new tutor).

5. SESSION MANAGEMENT LIFECYCLE

Detail the before, during, and after processes for all session types, emphasizing the mandatory digital check-in (QR/OTP) for offline sessions to create an audit trail.

6. CODE OF CONDUCT FOR TUTORS & STUDENTS

List explicit "Must Do" and "Strictly Prohibited" behaviors. For tutors, highlight prohibitions against sharing direct contact before payment and accepting off-platform payments. For students, highlight prohibitions against payment bypass and harassment.

7. TIERED WARNING & SUSPENSION SYSTEM

Define a progressive discipline system:

· Level 1: Formal Warning (First minor violation, 30-day probation).
· Level 2: Temporary Suspension (Repeat violation, 7-30 days, training required).
· Level 3: Permanent Ban (Serious violations: fraud, harassment, off-platform cash deals). Specify consequences: profile removal, earnings hold, potential legal action.

8. DATA PRIVACY & SECURITY

Declare compliance with standards (SSL, PCI-DSS), outline data collected (basic info, location, encrypted payment data, chat logs for safety), and state what is not done (sell data, spam).

9. SUPPORT, COMPLAINT & DISPUTE RESOLUTION

List contact channels (In-app chat, Email, Phone: +91 7068003894, WhatsApp, Instagram:

@tutormitra
). Define a structured, timed complaint resolution workflow from ticket creation to feedback collection.

10. APPENDICES & IMPLEMENTATION

· In-App Footer Structure: List the policy links (About, T&C, Privacy, Refund, Conduct, Contact).
· Policy Page UI/UX: Describe a tabbed interface for easy navigation (Tabs: Students, Tutors, Payments, Safety, Warnings, Support, Legal).
· Quality Assurance Checklist: Provide checklists for Technical, Policy, and Business Readiness.
· Emergency Contacts: List dedicated contacts for Safety, Payments, Tech, and Legal issues.

---

FINAL INSTRUCTION:

Synthesize all the above into a single, masterful, and exhaustive document. It must be technically precise enough to guide developers implementing the features (e.g., payment-locked chat) and legally robust enough to serve as the binding terms of service. The tone should be professional, unambiguous, and focused on creating a safe, fair, and sustainable platform for all users.

Now, generate the "TUTORMITRA - COMPLETE TERMS, POLICIES & RULES DOCUMENT".npm audit` for details.
PS C:\Users\alc\Downloads\TutorMitra_Complete_Working\Workspace\client> npm run dev

> [email protected] dev
> vit

TutorMitra_Terms_Policies_Rules.md

@@ -0,0 +1,8 @@
+// Example API endpoint check
+router.get('/chat/:bookingId', authenticate, async (req, res) => {
+  const booking = await Booking.findById(req.params.bookingId);
+  if (booking.payment_status !== 'confirmed') {
+    return res.status(403).json({ error: 'Chat locked until payment confirmation' });
+  }
+  // Proceed with chat data
+});