Privacy Policy
Effective date: 17 October 2026
How information is handled in this E2 Assessment application. This policy does not claim that every enrolled or offline student has a record here.
Scope and contact
This notice covers ptm.excellenteducators.in and the assessment, report, recovery, payment and staff functions inspected in this application. The main marketing website and external services may have separate notices. Contact Excellent Educators at the address and email below for privacy questions. The individual operator is Munish Sharmaa, operating under the brand Excellent Educators.
Student details and responses
The student form collects student full name, class, optional school name, parent/guardian WhatsApp number and a permission confirmation. The application records the selected assessment level and the answers submitted for the 25 questions. It does not ask students for an email address, a student account password, Aadhaar or card/bank credentials in the assessment form.
When you choose Pay or use a complimentary access code, the backend may save the submitted details and answers before payment or redemption succeeds. Stored report records include an internal report reference, creation time, report date, amount/currency, payment/order state and report-access information. Historical records are not rewritten by policy or timezone updates.
Report scores, selected response patterns and guidance are calculated from the answers. The inspected payment database stores the answers and report/access metadata; it does not upload or store the generated PDF file as part of normal report generation. The PDF is generated in your browser and can be saved on your device.
Browser drafts, recovery credentials and staff cookies
The application uses sessionStorage for the assessment draft, including entered details, answers, level and active report/submission state. It uses localStorage to remember the most recent private report credential for recovery. Session storage generally lasts for the browser tab session; browser session restore may preserve it. Local storage remains until replaced or cleared. Storage may be unavailable in some browser settings.
Clear draft or Start another assessment clears the local assessment draft; it does not delete submitted server records and does not necessarily remove the last recovery credential. Browser site-data controls can remove locally saved information. Keep a separate safe copy of a report code you wish to use later.
The private report credential is sent to the backend to authorise report access. The report lookup is stored as a hash in the database, while the browser may retain the usable credential. Do not post it publicly or send it in an ordinary support message.
Staff login uses Supabase Authentication and a secure, HttpOnly, SameSite staff-session cookie on this site. Student assessment access does not require that staff cookie. No analytics tracker is added in the inspected assessment frontend; hosting and payment services may process operational/security information.
Payments and complimentary access records
Razorpay handles checkout. The application passes checkout details such as order amount/currency and may prefill the supplied name and phone number. It stores payment/order identifiers, verification state, captured-payment time and processed payment event identifiers/types/times needed for verification, duplicate handling and recovery. It does not receive or store card numbers, CVV, UPI PINs, bank passwords or OTPs in its own assessment database. Test Mode uses simulated payments.
Complimentary records include a code hash, masked identifier, maximum uses, used count, expiry/revocation state, creator/reference timestamps and report entitlements. The full complimentary code is revealed to the main admin at creation; a hash is used for validation. Internal reasons are visible to authorised administrators, not included in student report responses. Attempts are counted in backend rate-limit records to reduce guessing.
Staff and support information
For staff who use the application, Supabase Authentication processes email/password authentication. Staff membership stores the staff user reference, display name, role, enabled status, password-change/reset state and operational timestamps. Admin operations can create accounts or reset passwords; these credentials must be shared privately. These are staff records, not accounts for every student.
If you contact support, the information you choose to provide, such as a payment reference, issue description or screenshot, will be used to investigate and respond. Please omit passwords, OTPs, PINs, full private report codes and unnecessary personal information. Authorised support staff handle complaints, payment issues and duplicate-charge enquiries through the listed WhatsApp and email contacts.
Purposes, providers and disclosures
We use the information to run and score the requested assessment, deliver and recover authorised reports, verify payments, issue complimentary access, prevent misuse, administer staff access and resolve service or payment problems. The application does not automatically enrol every assessed student into a course or publish a public student directory.
The application uses Sites hosting/infrastructure, Supabase for database/Auth/Edge Functions and Razorpay for checkout and payment verification. These services may process request metadata, including IP address, device/browser information, timestamps and security logs. If you choose WhatsApp, that service receives your message and handles it under its own terms. The programme-enquiry button does not automatically include your scores, phone number, student name or private report code.
We do not sell assessment information. Access may be given to authorised staff and relevant service providers for the purposes described, or disclosed where required by applicable law. Provider infrastructure may process information outside your location; this notice does not promise that all data or backups remain in India.
Retention and deletion — decisions still pending
A fixed retention period and an automated server-record deletion schedule have not yet been finalised for this application. Records currently remain available for report recovery, payment reconciliation, access administration and support, subject to applicable obligations. We do not promise deletion after an invented number of days.
Contact support to request access, correction, deletion or withdrawal of permission. We will verify authority using proportionate information and review the request, relevant legal obligations and effects on report recovery. There is no student self-service server-data deletion tool at present. Clearing browser storage does not delete backend records. Payment/dispute or legally required records may need to be retained. Requests do not require sharing your password or OTP.
Withdrawal or deletion may prevent future report recovery or processing that depends on the affected information. It does not undo lawful processing already completed or remove applicable consumer remedies.
Children, security and complaints
Students may be under 18. A parent/guardian should review this notice and authorise participation. The checkbox records a permission declaration; this application does not independently verify the identity of the consenting parent or guardian. A guardian may contact support about a child’s information.
Private report credentials, staff role checks, restricted database permissions and payment verification protect access, but no online service can guarantee absolute security. Use a trusted device and do not share private credentials. Send privacy concerns or complaints to the support email below and identify the request without disclosing secret credentials.
Excellent EducatorsBuilding Careers. Creating Leaders.