Privacy notice
This page covers what happens when you use Manthika on the web — leaving an email, working through a lesson, suggesting a fix to something we got wrong, or buying a print copy. It is short on purpose; a fuller policy (terms, refunds, the full trust suite) is coming, but nothing on this page waits for that.
What we collect
When you use a “notify me” or “tell us to prioritise this” field, we store: the email address you enter, your preferred language (if you tell us), which book you asked about, which page the form was on, your browser’s user-agent string, your account id if you’re signed in, and the time you submitted it. We do not ask for a child’s name or any other personal detail in this flow.
This is separate from the lesson loop itself, which asks for a child’s first name only so their progress can be saved on the same device, and — only with a parent/guardian’s explicit, separately-recorded consent — a practice log used to measure whether the lessons are actually teaching. This log is not anonymous: it is stored under the child’s learner profile (which holds their first name and class) inside your account (which holds your email address). We do not use it for anything beyond measuring whether a lesson works, and interest-capture data and that consent-gated learner log are never merged.
If you use “suggest a fix” on a lesson, we store the correction text and reason you send us, which lesson and which part of it you were looking at, the id of the learner profile you were using (not their name) so one learner can’t flood us with submissions, your account id if you’re signed in, your browser’s user-agent string, and the time you sent it. We use this only to check the correction and, if you’re right, fix the lesson.
If you sign up on the collaborate page to read a chapter before it is final, or to make videos from one, we store: the email address you enter, the role you pick (teacher, tutor, student, subject expert, parent, creator), the subject, class and chapter you name, whether the reader is under eighteen (in which case the email is a parent’s, and we never ask for the learner’s name), the date and wording of the consent you ticked, your account id if you’re signed in, your browser’s user-agent string, and the time. We use it to email you a chapter or a kit and to record what you found; a finding we accept is credited by the name you give us then, and only with your say-so. Write to the address below to be removed.
Beyond forms, using the free pages at all — clicking a link, opening a lesson, reaching a step in it — logs a coarse, anonymous event: which step, a random per-visit session id, and roughly when. This happens whether or not you ever type anything in, and it carries no name, email or other identity — it exists so we can tell whether a page is actually working, not to follow you around.
Why we collect it
To tell you when a book you’re waiting for is ready to read or ready to print; to decide — from real demand rather than guesswork — which books to build next and in which languages; to check corrections readers send in and fix lessons that are wrong; and to see, from real usage rather than guesswork, whether the site’s pages and links are actually working.
How long we keep it
Until the book you asked about ships and we’ve told you, or until you ask us to delete it — whichever comes first. Write to us at the address below and we will remove your record.
If you hold a Manthika account, you can delete it yourself, any time, from your account page — every learner, order and record under it is removed, along with the sign-in itself. No need to write in first. An account has no fixed retention period of its own: it, and any order under it, is kept until you delete it or ask us to — we don’t yet close an account automatically just because it has gone unused.
A correction you send is kept while we review it, and afterward as a record of what was suggested and changed. The anonymous usage events above aren’t tied to your name or email, so there is no individual record to look up and delete — only aggregate counts we use to see what’s working.
Who sees it
Not just us, and not just email addresses — here is the honest list of who else touches this data, and why.
- Google Cloud / Firebase runs Manthika’s backend — the database that stores everything on this page lives there. Firebase doesn’t guarantee its servers sit inside India, so this can mean your data is processed outside the country. India’s DPDP Act calls this a cross-border transfer (§16) and asks us to say so plainly, which is what this line is.
- Razorpay, a licensed Indian payment processor, handles any payment you make — for example, reserving or buying a print copy. Your card, UPI or bank details go straight to Razorpay; Manthika never sees or stores them.
- Videos on The Feed are served from Google Cloud Storage (
storage.googleapis.com), not from Manthika’s own servers. Playing one is a direct request from your browser to Google, the same as any other video host would receive. - Shopify runs the print-book shop, reachable from /pricing — buying there gives Shopify your order and delivery details, the same as any other store built on it.
- Resend would deliver any mail we send you (a verification link, a receipt, a notice). It is built into Manthika but not yet switched on — named here ahead of that, not after.
- Anthropic would grade a typed answer in a conversation-practice exercise, when that feature is live. It is also built but not yet switched on, named here for the same reason.
- None of this is us selling or sharing your data for someone else’s use. These are the processors Manthika runs on, not outside parties we hand your information to.
Grievance Officer
India’s DPDP Act requires us to name a Grievance Officer — someone you can take a data complaint to directly, separate from a general question. Grievance Officer: Mohnish Sharma. Write to the address below with “Grievance” in the subject line and we will treat it as one.
Contact
Questions, or want your data removed? Write to mohnish2021@gmail.com.
Last updated 2026-09-30.