INFORMATION & SUPPORT
Privacy Policy
This notice describes the website built here and the contact choices it provides. It does not describe an uninspected student portal or a separate service operated on another website.
Using the website
The site serves information and learning resources. Its class and resource pages do not create student accounts, take payments or send form entries to a website database. Quiz answers and practice interactions on those pages stay in the current page and are not saved. The Telugu Varnamala learner app on this website (/dashboard) is different: it can keep learning progress and optional accounts, as explained in Website privacy & learning notes and the App privacy policy.
Preparing and sending an enquiry
The demo form builds a message in your browser. You choose whether to open email or WhatsApp and send it through that service. Your message then uses that provider’s systems and privacy terms. The class team receives only a message you actually send. Avoid sending sensitive information or a child’s full identifying details.
Hosting and external services
The hosting provider may process request information necessary to serve and protect the site. A private preview may require the hosting provider’s sign-in. Map, email, phone and WhatsApp links open the relevant external service only when you choose them. No advertising pixels or analytics scripts are included in this build.
Information in an existing enquiry
For questions about information you have already sent, contact Ravi using the channel below. Explain the request using the minimum information needed. The operator must confirm any applicable retention, lawful basis, service vendors and legal identity in a final business privacy notice before introducing stored enrolment records or a student portal for classes. The learner app’s optional accounts and saved progress are described separately in the App privacy policy.
For a question about your information or an existing booking, contact Ravi at brollyjuniors.in@gmail.com or +91 95423 44555. Use a parent or guardian’s contact details.
Follow the information from your device to your chosen contact app
We want a parent to understand what happens before deciding what to share. On this website, reading a page, trying a word choice and preparing an enquiry are different activities. A reading page gives you information. An exercise changes what is displayed in the current browser page. The enquiry composer turns the details you type into a message you can inspect. None of those steps, by itself, delivers a class enquiry to Ravi.
If you choose the email action, your device asks an email application or webmail handler to open a draft. If you choose WhatsApp, that service receives the handoff needed to show a proposed conversation and message. You still decide whether to send. This distinction matters when you are reviewing a message that contains information about a child. You can remove unnecessary detail while it is a draft instead of assuming that clicking a website button has already completed the communication.
For an ordinary first enquiry, a broad age range, present Telugu familiarity and a suitable class preference are enough to begin the discussion. A personal history of the child is not needed to ask whether a batch may be suitable.
Decide what a first message needs to say
Consider an illustrative parent enquiry: an adult wants a class for a child who hears Telugu at home and usually replies in English. The useful information is the starting situation, the age range and the practical class preference. The family does not need to attach a school report, identify other children in the household or explain private family circumstances. A short statement such as “We would like to discuss speaking practice for a learner aged eight to ten” gives the team a relevant starting point.
Before sending, read each line with a simple question in mind: does this help the team answer the question I am asking now? If a detail is useful only for a later enrolment decision, keep it out of the initial message and ask how the team would collect it if it becomes necessary. The existence of a text box should not be treated as an invitation to provide every record you have.
The composer includes an optional question field so that you can describe a specific class-selection concern. Keep that question about the service, available format or learning goal. Avoid placing passwords, financial credentials or sensitive records in a general enquiry.
Understand what the practice activities keep
The built-in word exercise and word game respond to choices on the current page. They do not create a student profile or add a result to a teacher dashboard. The site does not ask you to identify the learner before trying a vocabulary card, opening a guide or reading a story. These practice pages have no progress account to sign into and no saved score associated with an email address. The learner app is different: its optional accounts and saved progress are explained in Website privacy & learning notes.
A parent might watch a child choose an answer and make a personal note about what to practise later. That is something the parent chooses to do outside the website. It should not be confused with the site automatically monitoring the child. Similarly, a browser can remember a tab in its own history, but that does not mean this site has created an educational record containing the answers.
Closing or reloading a practice page can reset the exercise. If you need to discuss learning with the teacher, describe the task and the observation in general terms. You can say that a learner recognised a practised word with help, without sending a screenshot that reveals unrelated material on the device.
Review shared-device use
Families sometimes open the website on a household computer, a borrowed phone or a device used for work. Think about the device as well as the website. A prepared draft may remain visible in the tab while the page stays open. A sending application can keep its own drafts or conversation history after you leave the website. Those behaviours belong to the device and application settings, so the website cannot promise to erase them.
When using a shared device, avoid adding personal details until you are ready to review and send the message. Check which account is signed into the sending application. A parent who intends to send from a personal address should not accidentally use a workplace mailbox simply because that mailbox is the default handler on the computer.
After the enquiry, close the draft or tab as appropriate and check the sending app if you want to remove an unsent copy. Do not assume that clearing one text field also deletes a copy already saved by another service. If a device belongs to someone else, follow that person's rules about downloads, browser use and signed-in accounts.
Know the difference between a link and an embedded service
The website offers links for phone, email, WhatsApp, map directions and a relevant script reference. Choosing one of those links can move you to another application or website. The provider of that destination may handle information according to its own settings and terms. This build does not embed a live WhatsApp conversation, a payment form or a map that tracks the learner inside the page.
A useful way to notice the transition is to look at the application or address bar after choosing a link. A map request uses the nominated venue query so you can look for directions. It does not tell the class team that you visited the map. An email handoff opens the recipient in your chosen mail handler; it does not demonstrate that the recipient has received a message.
You can choose a different contact method if you prefer not to use a particular external service. The contact page lists the available channels. This notice describes the connections supplied by the build; it does not certify the privacy settings of every app installed on a visitor's device.
Handle an enquiry you have already sent
Once you actually send a message, the recipient has a communication to respond to. If you later notice a mistake, send a concise correction through the same adult contact channel when possible. Identify the earlier question well enough for the team to understand the correction, without repeating all of the original personal information. For example, explain that the preferred day has changed or that a class-mode selection was accidental.
If your concern is about information in the message rather than the class itself, say that clearly. A request to correct an email address is different from asking whether a particular group has space. Clear subject wording helps the team distinguish an administrative information request from an ordinary availability enquiry.
This build does not supply a system that automatically searches mailboxes, edits external messages or guarantees that a sent message can be recalled. Ask the team what information it holds in the relevant service and what process is available for your request. The identity of the actual record system and operator needs to be established before a precise answer about that record can be given.
Ask a focused privacy question
A useful privacy question names the activity involved. You might ask which provider will host an online class, whether a proposed lesson is recorded, or how the team intends to share an update with a parent. These are separate questions. Asking them individually makes it easier to understand the answer and identify anything that remains unclear.
Keep a copy of the explanation that applies to the service you are considering. If the team later introduces a different platform or a student portal, ask whether the explanation still applies to that new arrangement. An answer about the current message composer should not be assumed to cover an account system, such as the learner app's optional accounts, or a class recording or payment integration.
There is no need to make a general enquiry more revealing in order to ask these questions. Use an adult's contact details and describe the service feature you want explained. If a further verification step is proposed, ask why that step is needed and which secure channel should be used. Do not place verification documents into an ordinary website question field merely because someone needs to identify a previous record.
Use screenshots and attachments carefully
The form in this website does not offer an upload field. If you later send an attachment through email or a messaging app, review the entire attachment first. A screenshot intended to show a broken button may also display the child's name, a browser account icon, another conversation or notifications from unrelated services. Crop or redact material that is not needed to explain the issue.
A technical report often needs only the page address, a description of the action and the text of an error. You can usually say “the message review did not appear after I completed the required fields” without sending a photograph of the child's work area. Start with that limited explanation and ask whether anything else is necessary.
Do not send card details, passwords, one-time codes or account recovery information as evidence for a website problem. This site has no payment checkout to investigate and does not require a student password to use its free resources. If a request for such information appears to come from the program, stop and verify the channel using the published contact details rather than replying with the requested credentials.
Read this notice alongside the feature you use
Different pages explain different parts of the website. The technology and cookie notice describes the page features in this build. The parent-managed enquiry guidance focuses on keeping a child's information minimal. The media page separates website illustrations from questions about class recordings and promotional use.
Those pages should work together without turning a simple enquiry into a broad consent to every possible future activity. Reading a resource, contacting the team and agreeing to a separate recorded class are not interchangeable choices. Ask for an explanation that matches the activity you are actually considering, and keep optional activities separate in the conversation.
The class and resource pages of the present site are a local website build with information, practice and contact handoffs; the learner app on the same website is covered by Website privacy & learning notes and the App privacy policy. A final business-wide privacy notice would need the operator's real identity, actual processing systems and other operational details. Those have not been manufactured here. If the service changes, its notice should change with the real implementation rather than rely on text written for an earlier, simpler website.
A practical review before you leave the page
Before leaving an enquiry session, check whether you merely prepared a draft, opened a sending app or actually sent a message. If you sent it, note which adult account you used. If you did not, decide whether to keep or discard the draft in the relevant app. These small checks make later questions about a communication much clearer.
When contacting Ravi about privacy, include the type of request and the service involved. Keep the first message brief enough that the team can tell what you need without receiving unnecessary child information. You can ask for access help, a correction, a discussion about deletion or an explanation of a proposed data use. The appropriate handling depends on the actual record and system involved.
We provide the website contact path so that such questions can be raised. We do not label the site as certified compliant with every jurisdiction, promise a retention period that the operator has not approved or claim control over third-party inboxes. The useful outcome is a clear account of what this build does, what you choose to send and which further business details need a direct answer.