Privacy Policy 

LetMeTeach is developed and operated by Sripto Corporation Private Limited (“Sripto”, “we”, “us”), a company incorporated in India. This policy explains what personal data we collect when you use this website (letmeteach.in), the LetMeTeach learner app (letmeteach.in) and the emails and services that go with them, why we use it, who processes it for us, how long we keep it and the rights you have.

LetMeTeach is offered to learners around the world, so this policy is written for every country we serve. Sripto decides how and why your personal data is used: it is the “controller” under the GDPR, the “Data Fiduciary” under India’s Digital Personal Data Protection Act, 2023 and the “business” under US state privacy laws. Where the law of your country gives you more protection than this policy, that law applies.

In short: we collect what we need to teach you, to bill you and to keep the service safe. We do not sell your personal data. There is no advertising inside LetMeTeach. You can delete your account from the app at any time.

What you give us

• Account details: your name, email address, mobile number, date of birth, country and state, and a password (stored only as a one-way argon2id hash) or, if you sign in with Google, your Google account identifier. We email you one-time codes to confirm sign-ups and password sign-ins.
• Learner profile: your avatar, native language, age, stage of study and level, the curriculum or exam you follow and your interests, so lessons are pitched at the right level.
• Billing details: your plan, payments, refunds and invoices, and the billing address, company name and tax ID if you add them. Card, UPI and bank details are entered on the checkout of our payment provider, Razorpay; we never receive or store full card numbers.
• What you send while learning: the topics and questions you type or say, your doubts, the documents and images you upload, your answers in checkpoints and tests, the courses you request and any feedback you give.
• Support and contact: what you write to support and its attachments, emails you send us, and inquiries sent through the Connect page (name, work email, institution, role, student count and message).

What is created as you learn

• Progress: the lessons and courses you take, test attempts and scores, how well you know each concept, practice and certificates.
• Learning memory: so the tutor can carry on where you left off, an AI model notes the preferences and facts you share about your learning (for example, how you like things explained) and short summaries of past sessions, and keeps them with your account.
• Session records: the history and summaries of your sessions and the state of a lesson, so you can resume it.

Your voice

• LetMeTeach uses your microphone only when you start talking to the tutor. It never uses your camera and never records your screen.
• Live voice tutoring is streamed through our servers to the AI provider as you speak. We do not record or store that audio.
• A spoken doubt is held in memory only long enough to turn it into text, then discarded; we keep the text of your question, not the recording. If your browser turns speech into text itself, that is done by your browser’s speech service under its own terms.

What is collected automatically

• Cookies, marketing records and product analytics in the learner app, described in Cookies, analytics and marketing records.
• Security records: sign-ins, one-time codes and account changes, with the IP address and browser details, to protect your account and detect abuse.
• Error reports: technical details of a failure (what broke, where, on which browser), sent without your name, email, cookies or the content of your requests.

This website

letmeteach.in itself sets no cookies and runs no analytics or advertising scripts; the campaign cookies the learner app sets for the whole letmeteach.in domain (see Cookies) are also sent to it. Our hosting records each request (IP address, time and page) for security and reliability. If you arrived through a link with a referral code or campaign tags (ref, utm_*), those tags are passed on when you follow a link into the learner app, so the app can credit the referrer.

We use personal data only for the purposes below. Where a law asks for a legal basis (for example the GDPR), the basis is shown in brackets.

• To teach you: to plan, narrate and visualize lessons, answer doubts, run the live voice tutor, tests and courses, remember your progress and preferences, and pitch each lesson to your age and level (performing our contract with you).
• To run your account and keep it safe: sign-in, one-time codes, fraud and abuse prevention, rate limits, malware scanning of uploads and checks against fake sign-ups (contract; our legitimate interest in a secure service).
• To take payment: checkout, renewals, invoices, refunds, taxes and accounting (contract; legal obligation).
• To talk to you: service emails such as codes, receipts, plan reminders and replies to support (contract; legitimate interest). If we send news or offers, we do so only where the law allows, and every such email has an unsubscribe link.
• To improve LetMeTeach: product analytics and error reports, to see where lessons fail or learners drop off and fix it (legitimate interest).
• To measure how learners find us: campaign and referral records, and running the referral programme (legitimate interest, or consent where your law requires it).
• To meet the law: keeping tax records, answering lawful requests and enforcing our terms (legal obligation; legitimate interest).

Tests and checkpoints are graded automatically and the tutor adapts lessons automatically. None of this produces a decision with a legal or similarly significant effect on you.

Lessons, answers, narration, voices, summaries and AI tests in LetMeTeach are generated by AI models run by our providers. To produce them, we send the provider your prompts and questions, your uploaded documents and images, the context of the session and a summary of your learning memory. For the live voice tutor we also send your name, age and language, so it can address you and pitch the lesson.

• Google: Gemini models, through Google Cloud, for lessons, answers, the live voice tutor and narration.
• Anthropic, OpenAI and Sarvam: for particular languages, voices or learners (Sarvam voices for Hindi, Telugu, Tamil and Bengali).

The providers process this data to provide their service to us, under their business terms. When you learn on LetMeTeach you are always talking to an AI, never to a person, and the tutor’s voices are generated by AI. AI output can be wrong or incomplete; check important facts before you rely on them.

• LetMeTeach is for learners of any age. A parent or guardian may create and manage the account for a child.
• A parent or guardian can ask us to see, correct or delete their child’s personal data at founder@letmeteach.in.
• We never sell a child’s personal data, we do not knowingly build profiles of children for advertising, and there is no advertising inside LetMeTeach.

The learner app (letmeteach.in) sets the cookies and keeps the records below, most of them before any account exists. Outside the regions named next, the visitor cookies can be set from a visitor’s first request. The website letmeteach.in itself sets no cookies.

Visitors in the European Economic Area, the United Kingdom or Switzerland, and visitors whose country we cannot tell, get none of the visitor or campaign cookies below and no marketing record until they consent. Sign-in cookies, which are needed for the service, are set as usual.

Cookies

• qv_anon: a random anonymous visitor id that holds no personal detail, set on the first visit and kept for 1 year. It is HttpOnly, so scripts in the page cannot read it. We use it to connect a first visit, the campaign that brought the visitor and the records below to the account the visitor later creates, so we can see which channels lead to sign-ups.
• qv_landing_seen: a session cookie that ends when the browser is closed. It tells us a visit has already been recorded, so it is not recorded again on every request.
• Campaign cookies (qv_utm_* and qv_click_*): when you arrive through a link with campaign tags, a referral code or an advertising click id, the page itself writes them into first-party cookies (qv_utm_source, qv_utm_medium, qv_utm_campaign, qv_utm_term, qv_utm_content, qv_utm_ref, qv_click_gclid, qv_click_fbclid, qv_click_msclkid, qv_click_ttclid) kept for 30 days on the whole letmeteach.in domain, so a sign-up can be credited to the campaign or friend that brought you. They are not HttpOnly: scripts in the page can read them. They are written only after the app has checked that your region needs no consent, or that you have given it.
• Sign-in cookies: once you sign in, cookies hold your session: an access token (2 hours) and a refresh token (30 days), both HttpOnly so scripts in the page cannot read them, and a marker that a session exists (qv_session, 30 days), which is not HttpOnly, so the page can read it to know you are signed in. They are needed to keep you signed in.
• Browser storage: the app also keeps a few settings in your browser’s local storage, such as your tutor voice, lesson settings and the id of the session you are in, so it works the same way on your next visit.

Marketing records

• Campaign touchpoints: when a visit arrives with campaign information we record the campaign tags in the link (UTM source, medium, campaign, term and content), a referral code, an advertising click id (Google gclid, Meta fbclid, Microsoft msclkid, TikTok ttclid), the address of the page that sent the visitor, the address of the page they landed on, their IP address, their browser’s user-agent text and the anonymous id. When an account is created these records are linked to it; if there are none, we record a direct visit with the IP address and user-agent text from the sign-up.
• Marketing events: a landing event when a browsing session starts or new campaign information arrives (landing address, referring address, campaign tags, IP address, user-agent text and whether the visit was direct), and a sign-up event when an account is created (campaign tags, and whether a referral link brought the learner and whose link it was).
• Retention: campaign touchpoints and marketing events are deleted automatically after 400 days. The first and the last touchpoint that an account’s attribution record points to are kept so we can still see which channel brought a learner, but after 400 days their IP address, user-agent text, advertising click ids, referring address and the part of the landing address after the question mark are removed.
• Purpose: to measure which campaigns, advertising clicks and referral links bring learners, and to run the referral programme. We do not send these records to advertising platforms.

Product analytics

• Product events: where product analytics is switched on, each event has a name from a fixed list (for example lesson started, step viewed, lesson completed, paywall viewed, sign-up, checkout started), its time, which app sent it, the anonymous id or, once you are signed in, your account id, a session key, a request id, whether the account is an internal test account, and a few details that belong to the event, such as a lesson step number, the time to the first visual, how a lesson ended, the subject and topic of a lesson or course request, or the plan and payment provider of a checkout. They carry no IP address and no user-agent text. Product events are deleted automatically after 400 days.
• Purpose: to see where learners leave a lesson or the sign-up, to find and fix failures, and to measure the quality of the product.

We do not sell your personal data, and we do not share it for cross-context behavioural advertising. We share it only with:

• Google Cloud: hosting, database, file storage and the Gemini AI models, in India (Mumbai) and the United States (Iowa).
• Anthropic, OpenAI and Sarvam: AI models and voices for particular languages, voices or learners (Anthropic and OpenAI in the United States, Sarvam in India).
• Razorpay: payments, renewals and refunds in every country (Razorpay processes them in India).
• Email delivery: Google Workspace or our email delivery provider, to send codes, receipts and reminders.
• Cloudflare: a check at sign-up that a person, not a bot, is signing up, where it is switched on.
• Sentry: error reports without your name, email, cookies or request content, where it is switched on.
• Authorities and courts: when the law requires it, or to protect the safety of a person, especially a child.
• A buyer or successor: if Sripto is merged, acquired or sells its business, under this policy or one at least as protective, and we will tell you first.

Each provider may use the data only to provide its service to us, under a contract that requires them to protect it.

Sripto is based in India and our main database is in India, with a copy in the United States. Some providers process data in the United States and other countries. Wherever your data goes, we protect it as this policy describes. Where the law requires a safeguard for a transfer, such as the European Commission’s Standard Contractual Clauses or the UK’s transfer addendum, we rely on the safeguards in our providers’ data processing terms. We do not transfer personal data to any country the Government of India restricts.

• Your account, profile, progress, learning memory and session history: for as long as your account exists.
• Uploaded files: the original file is deleted within minutes of being processed; the text and summary taken from it stay with the session until your account is deleted.
• Voice: not stored (see Your voice).
• One-time codes: deleted after 30 days. Sign-in tokens: deleted 7 days after they expire or are revoked.
• Security records: archived after 90 days and deleted after 365 days.
• Support attachments: deleted 15 days after the ticket is closed. Error reports: deleted after 14 days.
• Marketing records and product events: deleted after 400 days, as described above. Campaign cookies: expire after 30 days.
• Search text: what you type into the learner app’s topic and course search is logged and kept for 90 days to check the quality of search results, then deleted.
• Demo sessions that are never linked to an account: deleted automatically, starting 24 hours after they end.
• Invoices and payment records: for as long as tax and accounting laws require, which can be several years after your account is deleted.
• Connect-page inquiries: kept as business correspondence in our email, and deleted on request.

When you delete your account, we erase its personal data (email, name, mobile, date of birth, address), learning memory, uploaded documents, support ticket text and session history, and strip the analytics and marketing records of anything that identifies you. Invoices are kept as tax law requires. Copies in our encrypted backups are overwritten as the backups rotate.

• Everything between your browser and our servers is encrypted in transit (HTTPS), and Google Cloud encrypts our database and files at rest.
• Passwords are stored only as argon2id hashes, and every password sign-in also needs a one-time code sent to your email.
• The cookies that carry your sign-in tokens are HttpOnly, uploads are scanned for malware before they are read, and our network is protected by Google Cloud Armor.
• Only the people who need personal data to run LetMeTeach can reach it.

No system is perfectly secure. If a breach affects your personal data, we tell you without delay and report it to the authorities as the law requires, for example to the Data Protection Board of India and, where the GDPR applies, to the supervisory authority within 72 hours.

Wherever you live, you can:

• See and get a copy of your personal data, including in a portable format: export it from the app where available, or ask us.
• Correct or complete it: edit your profile in the app, or ask us.
• Delete it: delete your account from the app at any time (you confirm with a code sent to your email), or ask us.
• Object to or restrict a use based on our legitimate interests, and withdraw consent you gave, at any time, without affecting what was done before.
• Stop marketing emails with the unsubscribe link in any of them.
• Nominate a person to exercise your rights if you die or become unable to (India).
• Complain to us, and to the data protection authority where you live (see Country and region information).

To use a right, write to founder@letmeteach.in from the email address on your account (a parent, guardian or authorised agent can write for you). We may ask you to confirm your identity first. Using your rights is free, we will not treat you differently for using them, and we act on each request within the time your law sets, for example one month under the GDPR.

India

Under the Digital Personal Data Protection Act, 2023, the Digital Personal Data Protection Rules, 2025 and the Information Technology Act, 2000, Sripto is the Data Fiduciary. You can ask for a summary of your personal data and who it was shared with, its correction, completion, updating and erasure, and you can nominate a person to act for you. Raise a grievance with our Grievance Officer first (see Contact): we acknowledge it within 48 hours and resolve it within one month. If it is not resolved, you can complain to the Data Protection Board of India.

European Economic Area, United Kingdom and Switzerland

Sripto is the controller of your personal data. The legal bases are listed in How we use it. You have the rights of access, rectification, erasure, restriction, portability and objection, and the right to withdraw consent. You can complain to the supervisory authority where you live or work, for example the data protection authority of your EU country, the UK Information Commissioner’s Office or the Swiss FDPIC.

United States

Under the California Consumer Privacy Act and similar laws in other states, in the last 12 months we collected these categories: identifiers (name, email, mobile, account and device ids, IP address); customer and commercial records (plans, payments, billing address); internet activity in our app (the analytics and marketing records above); audio (live voice, streamed and not stored); education-related records (progress, tests, certificates); inferences (learning memory); and account log-in details, which we use only to sign you in. They come from you, your device and our providers, for the purposes in How we use it, and are disclosed only to the service providers listed above. We do not sell or share personal information, including that of anyone under 16. You can ask to know, delete and correct your personal information; if we decline, you can appeal by replying to our answer with the word “Appeal”. A parent or guardian can use these rights for their child (see Children).

Everywhere else

We give everyone the rights in Your rights and choices, and where the law of your country sets a stricter rule, we follow it. That includes, for example, Brazil (LGPD), Canada (PIPEDA and provincial laws), Australia and New Zealand (their Privacy Acts), Singapore (PDPA), Japan (APPI), South Korea (PIPA), South Africa (POPIA), and the United Arab Emirates and Saudi Arabia (their PDPLs). You can complain to your country’s data protection authority.

We update this policy when LetMeTeach or the law changes, and the date at the top shows the latest version. If a change matters to how we use your data, we tell you by email or in the app before it takes effect, and where the law requires your consent, we ask for it.

Sripto Corporation Private Limited, India.
Questions, requests and complaints about privacy: founder@letmeteach.in.

Grievance Officer and data protection contact: the Founder, Sripto Corporation Private Limited, at founder@letmeteach.in. Write with “Privacy” or “Grievance” in the subject: we acknowledge a grievance within 48 hours and resolve it within one month.