Privacy Policy
CSS with Sir Waseem (ustaad.wazeem.com) is a CSS exam preparation service: you read the subject chapters, practise MCQs, and submit essays and outlines for us to grade and coach you on. This page explains what information we hold and how we use it, in plain language.
What we collect
- Your email address and name, when you create an account or register for the masterclass.
- Your city and exam-preparation details, if you choose to share them.
- The work you submit (typed essays and outlines, or photos of handwritten pages) and the transcripts, grades, feedback, and coaching we generate from them.
- What you read and practise: which chapters you have opened or marked read, and your answers to MCQs (multiple-choice questions), so the chapters can show you where you are and which ones you got wrong.
- Records of credit purchases (amount, date, reference). Payments are made through your bank or payment app. We never see or store card numbers.
- Basic technical logs (sign-in events, errors) needed to run the service securely.
How we use it
- To grade your submissions and produce feedback, drills, and progress tracking.
- To give you the subjects you have paid for, and to keep your place in them: what you have read, and how your practice is going.
- To sign you in (one-time email codes or Google sign-in).
- To send you what you asked for: seat confirmations, reminders, and calendar invites for the masterclass or a course you registered for.
- To keep the service working, prevent abuse, and fix problems.
AI processing
What we share and what we don't
Advertising measurement
If you reach us from an ad (for example on Facebook or Instagram) and then register, we send the ad platform a one-way scrambled (hashed) form of your email, not your readable address, together with the ad's click identifier, so the platform can confirm that the ad led to a sign-up. This is used only to measure our own ads. It is never used to send you marketing from anyone, and a visitor who did not come from an ad sends none of it.
Our public pages (the home page, the payment page, and the free chapters and tests) also load Meta's pixel. It tells Meta when someone opens one of these pages, taps WhatsApp, taps to pay, or taps to say they have paid, so we can see which of our ads work and show them to people likely to want the course. Meta may use its own cookies for this. The pixel does not run on the pages you use after signing in.