INFORMATION & SUPPORT
Cookie Policy
This build does not add advertising trackers or third-party analytics. Its class and resource pages do not use a cookie-based preference system; the learner app on this website can keep progress and preferences with a private cookie or browser storage, as explained in Website privacy & learning notes.
What runs in the page
On the class and resource pages, the menu, filters, quizzes and message composer use ordinary browser JavaScript. They do not use cookies, local storage or a persistent learner identifier. Responses are not saved after the page is closed. The Telugu Varnamala learner app on this website (/dashboard) is different: it can use a private cookie or this browser’s local storage to keep learning progress and optional sign-in, as explained in Website privacy & learning notes and the App privacy policy.
Hosting and external links
The hosting provider may use its own security or sign-in mechanisms, particularly for a private preview. Choosing WhatsApp, email or a map opens an external provider that can apply its own privacy and cookie practices.
If tracking is introduced later
The business should update this notice with the actual vendors, purposes and controls before adding optional tracking. This build has no visitor analytics dashboard (the learner app’s staff dashboard of account progress and activity is described in the App privacy policy) and does not claim a cookie consent banner has been connected to a consent platform.
What this browser-based website actually does
The site is built from ordinary web pages, local styles, original illustrations and a small script that makes selected controls interactive. You can read the class information and educational text directly in the page. JavaScript enhances the menu, resource filters, word practice and enquiry composer. The website does not need an advertising identifier to show those features.
A cookie is not the same thing as every temporary change in a page. When you open a FAQ or choose an answer, the browser can update the current page without storing a lasting preference for the website. On the class and resource pages, the practice responses and menu state are not placed in a cookie or a persistent learner record; the learner app's saved progress is explained in Website privacy & learning notes.
This description concerns the code supplied with this website. It does not describe every setting in your browser, every extension you have installed or every external service you may choose to open. Understanding that boundary helps a parent distinguish the site's own features from the broader device and application environment.
Menu choices are temporary page interactions
The mobile menu opens when you choose its button and closes when you use the available controls. The class submenu uses a native expandable element to show links to the available class pages. These changes make navigation usable on a small screen; they do not create a stored profile of which type of class interests you.
If you leave the page or reload it, the menu can return to its initial state. The code does not need to remember the open menu across visits. A browser may independently restore a tab or a page state, but that is not a claim that this website has saved a visitor's navigation preference on a server.
You can use the links to move between resources without consenting to a marketing tracker. There is no advertising or behavioural analytics script in this build that turns menu selections into a campaign audience. If tracking is added to a later implementation, its real purpose and controls should be described before the notice is changed to claim that such a system exists.
Resource search filters the visible collection
The search boxes in the learning hub and parent-guide directory help you narrow the cards already present in those pages. Typing a topic changes which cards are shown and updates the number of matching items. This is a local display operation, not a query sent to a separate search provider or a request to create a learner account.
For example, searching for worksheets in the resource directory shows the relevant resource card. It does not tell the team that a named child needs handwriting practice. The visitor has not supplied that identity, and the filter does not save a search history in the site's own database.
If a search shows no matches, clear or change the word and try a broader topic. You can also use the all-pages directory. The current implementation does not personalise the card order for different visitors or use past searches to recommend a paid plan. It presents the same authored resource collection and lets you choose which part to display.
Practice feedback stays with the current exercise
The word quiz tells you whether the selected choice matches the small task. The word game changes the prompt and displays a response to the selected word. These are examples of page logic: the script compares the current choice with the answer for that round and changes the feedback text.
The game does not ask for a name, assign a permanent user identifier or send a score to a teacher dashboard. It does not build a history of the learner's attempts. A parent can use the task as a shared activity without treating the result as a formal report.
If you want to revisit the words, use the visible vocabulary cards or start another round. If you want to discuss what the child found difficult, describe the observation to the teacher in your own adult-managed enquiry. The website does not automatically attach exercise responses to that message. This separation keeps a small free practice activity distinct from a progress-record system such as the saved progress in the learner app.
Understand the enquiry composer before using it
The composer reads the fields you complete and creates a message for review. It can use a known plan or mode selection from a class or pricing link to prefill the relevant choice. That visible context helps you avoid retyping the same preference. It does not mean the website has created a tracking profile from previous visits.
Preparing the message does not send it to a server inbox. The next step is your choice: open an email draft or a WhatsApp handoff, review the message there and send it if you want to contact the team. The external service may then store a draft, a sent item or a conversation according to its own operation and your account settings.
The site does not use browser local storage to keep the form after the session. Nevertheless, browser autofill and an external sending app can have their own memory features. Review those device-level settings if you use a shared computer, and check the account selected by the sending application before you transmit anything.
Downloads do not create a student login
The worksheet links open or download actual PDF files included with the website. The printer-friendly versions show the corresponding task in HTML. Choosing a file does not ask the site to create an account, assign a homework record or keep a named list of downloaded resources.
Your browser will handle the file according to its settings. It may show the PDF in a viewer, save it to a downloads folder or ask where you want it stored. Those are browser and device choices. The website cannot promise that a downloaded file disappears when you close the page, because a file you save is now held on your device.
For a shared device, choose a location that the adult can find later and avoid saving personal work in a public folder. The blank starter sheet itself does not contain a child's identity. If a family later writes names or notes on a printed or digital copy, that is a separate use of the resource rather than a feature that sends the completed work back to this website.
External destinations have their own technology
The contact page includes actions that hand off to phone, email, WhatsApp or map services. The alphabet page also links to an external character reference. These destinations are separate from the authored pages in this build. They may use their own cookies, security mechanisms, account features or service analytics.
Look at the destination when you choose a link. An external map can help you inspect a venue query, while a messaging app can help you prepare a conversation. You can choose whether to continue in that service. The site does not embed an always-open map or chat widget that is needed simply to read the learning pages.
If you do not want to use a particular provider, choose another available contact channel or continue reading the resources without opening that link. This notice does not list imaginary vendor categories to fill a template. It describes the external handoffs actually provided and recognises that the destination provider is responsible for explaining its own technology and settings.
A hosting environment is separate from page features
The current delivery is a local website and ZIP. A local preview server serves the files from the computer running it. The source has not been uploaded for a public hosted release. If the site is deployed later, the selected hosting provider may process request information to serve files, protect infrastructure or manage access.
A private hosting preview could also have a provider-managed sign-in layer. That layer is not the same as a student account created by Telugu Varnamala. Its behaviour should be explained by the hosting arrangement actually chosen, rather than inferred from the existence of a simple resource page.
Before public deployment, the operator should review the real hosting features and update the notice where necessary. The present build does not claim that a particular provider's entire logging configuration has been inspected or that the absence of an analytics script eliminates every infrastructure record. Page-level code and hosting-level operations are related, but they are not interchangeable descriptions.
What to check if someone proposes analytics later
A future request to measure visits should identify what will be measured and why. Ask whether the proposal counts page visits, contact clicks, actual message receipt or completed bookings. These are different events. A click on an email link cannot honestly be described as a confirmed enquiry received by the team.
Also ask which provider would receive the information, whether identifiers or personal data would be included and what choices a visitor would have. Do not assume a generic banner controls every script unless the code and configuration actually do so. A notice should match the implemented tools rather than advertise a consent platform that has not been connected.
No third-party analytics or advertising integration is currently supplied in this build. If the business later introduces one, it should document the real data flow and relevant controls before reporting visitor measurements. The aim is an accurate explanation of the feature, not a long vendor list copied from an unrelated website.
Ask about a browser feature using a concrete example
If you are unsure what happened on a page, describe the feature and the result. For instance, explain that the resource filter changed the visible cards, that a PDF opened in the browser or that an email application kept an unsent draft. This makes it easier to identify whether the behaviour belongs to the website, the browser or an external app.
Include the relevant page address and the type of device if that helps. Do not send private child details or screenshots of unrelated accounts to report a technical question. Start with the smallest description that shows the issue, then ask whether any further information is needed.
The privacy notice explains the enquiry data flow, and the contact page provides the adult-managed channels for questions. For the class and resource pages, this technology notice remains grounded in the actual build: readable static content, local interactive controls and user-chosen external handoffs. It does not claim a tracking dashboard, stored preferences or a cookie management system for those pages; the learner app's saved progress and preferences, and any private cookie it uses, are explained in Website privacy & learning notes.
Distinguish closing the website from deleting an external message
Closing this website ends the current browser activity, but it does not undo a message the visitor chose to send through email or WhatsApp. Once a sending app is used, that communication belongs to the relevant external workflow. Clearing this site's page state is therefore a different action from managing messages in another service or asking the team about information already received.
The local practice buttons do not create an account history or persistent score. Returning to the page starts the built-in activity again. The composer likewise needs to be prepared again after the page is closed or reloaded. These observations describe the code included in this build; they do not claim that every browser, hosting environment or external app stores no information of its own.
If optional analytics or another storage feature is added later, the business should describe the actual change rather than leaving this notice to imply that the original build and the new implementation behave identically. Visitors can use the listed contact route to ask which website version or service their question concerns.