INFORMATION & SUPPORT
Request Data or Account Help
The class and resource pages of this website do not create learner accounts. The learner app on this website offers optional accounts, explained in Website privacy & learning notes and the App privacy policy. If you need help with an account on a separate service or information already sent to the team, contact Ravi.
Tell us which service you mean
Include the website or service name and the type of request: access, correction, deletion or account help. Use the adult contact associated with the enquiry where possible. Never send passwords or one-time codes.
What happens next
The team can identify the relevant system and explain the appropriate verification and handling process. This page sends no automatic deletion command and cannot delete an account on an external learning platform.
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.
First identify the service you are asking about
A request is easier to direct when it names the system involved. This website provides public information, free practice and an adult-managed enquiry composer. Its class and resource pages do not create a learner account. The learner app on this website (/dashboard) offers optional accounts, as explained in Website privacy & learning notes and the App privacy policy; deletion steps are on the account & data deletion page. If you remember signing into another app or portal, include that service's name or address in your question rather than assuming the current website controls it.
The difference matters because a website contact cannot automatically operate every external account that may be used in a class arrangement. A message sent through email exists in an email service; a conversation in WhatsApp exists in that messaging environment; a separate learning portal may have its own administrator and account controls.
Begin with the question “Which record or account do I mean?” Then identify whether you need help locating the right service, correcting information already sent or discussing an existing account. The team can use that context to explain the appropriate next contact or process. This page does not display a delete button that pretends to remove data from an unidentified external system.
Choose the type of help you need
Access, correction, deletion and account troubleshooting are different requests. An access question asks what relevant information or account record exists. A correction question identifies a detail that appears wrong. A deletion question asks about removing a record or account. A sign-in problem may simply concern how to reach the appropriate service.
State the type of help near the beginning of your message. You might write that an enquiry contains an old time-zone preference, that you need to identify a platform mentioned in an earlier conversation or that you want to discuss information previously sent. This gives the recipient a clear reason to examine the relevant arrangement.
Do not choose a deletion request merely because you cannot find a password. Account recovery and removing an account can have different consequences. Ask for clarification before proceeding if you are unsure. The class and resource pages do not manage either function. For a learner-app account, the App privacy policy explains the Forgot PIN and deletion steps; for any other service, the team first needs to establish which real service is involved and which controls that service provides.
Use an adult contact associated with the enquiry
When possible, start from the adult email address or messaging channel used in the earlier class conversation. This can help the team recognise the relevant enquiry without receiving additional information about the child. Explain the relationship to the record in broad terms, such as being the parent who made the original request.
If that contact channel is no longer available, say so and ask what proportionate verification process the responsible operator can offer. Do not invent a verification method yourself by sending identity documents into a general text field. Ask why a proposed detail is needed and which channel is appropriate before sharing it.
No particular identity-checking procedure has been supplied for this build. We therefore do not promise that a first name alone will authorise an account action, or require an arbitrary set of documents. The correct handling depends on the actual record and service. The purpose of the first message is to identify the request and obtain the relevant process, not to disclose a child's complete identity pre-emptively.
Explain a correction precisely
A correction request should identify the detail you want changed and the context in which it appears. For example, a parent might have selected the wrong class format in an enquiry or later discover that a preferred day no longer works. State the corrected information clearly so that the recipient does not have to infer it from a long story.
Keep the scope narrow. If a time-zone preference changed, there is usually no need to repeat all the learner's information from the original message. Refer to the relevant adult enquiry and explain which detail should be updated in the team's actual records or conversation.
This website cannot edit a sent external message in another person's inbox. Sending a correction is a new communication that clarifies the earlier one. Ask the team to confirm how the correction will be handled in the relevant process. Do not assume that changing a field in a new browser draft also changes a copy that you already sent through another service.
Ask about deletion without assuming an automatic result
If you want to discuss deleting information or an account, identify the record or system as clearly as possible. Explain whether you mean the earlier enquiry, a separate learner account or material held in another service. A general instruction to delete everything may leave the recipient unable to determine which systems and records you are referring to.
Ask what the responsible operator can do and what information it needs to understand the request. The answer should concern the actual data and applicable circumstances. This page does not invent a retention period, promise immediate removal or claim that one message can erase copies held by unrelated providers or people.
Before deleting a real learning account, consider asking what access, files or class-related functions would be affected. That is a practical consequence question, not an instruction to keep information unnecessarily. Make the decision after the real service has explained its process. The static class and resource pages here have no learner-account database and therefore cannot perform such an action directly; learner-app account deletion is described on the account & data deletion page.
Keep credentials out of support messages
Never send a password, banking credential or one-time sign-in code to obtain routine class or account help. The free resources on this site do not require those details. If a separate platform has a genuine recovery process, use the platform's recognised controls or the appropriate administrator's explained procedure.
A support message can identify the service and the problem without revealing the secret used to enter the account. For example, say that the password-reset message did not arrive or that the sign-in page reports an error. Include the error wording if helpful, but remove private tokens and account recovery links from a screenshot.
Be careful with forwarded messages. A reset email can contain a live link that grants access. It is not the same as a harmless booking reference. If you are unsure whether something is sensitive, ask how to describe the problem safely before forwarding the complete message. A clear description of the failed step is often enough to start the conversation.
Distinguish browser history from a provider-held record
A browser may keep history, downloaded worksheets, saved drafts or autofill information according to its own settings. Those device-held items are different from information actually sent to the class team. Removing a browser history entry does not necessarily delete a message in an external inbox, and asking the team about an enquiry does not clear files saved on your computer.
Identify which location matters to your concern. If you want to remove a downloaded blank worksheet from a shared device, that is a device file task. If you want to correct a sent enquiry, contact the recipient. If a draft remains in an email application, inspect that application's draft folder or settings.
The practice activities on the class and resource pages do not create saved scores; the learner app's saved progress is explained in Website privacy & learning notes. The composer does not use local storage to maintain a learner profile. Those facts can help you narrow the question, but they do not describe every feature of your browser or a sending app. A precise account of where you saw the information will make support more useful.
Follow a request with a clear reference
Keep a copy of the request you sent and the adult channel used. If the team gives a safe reference or identifies a particular service, use that context in a follow-up. Avoid repeatedly sending the entire personal history when the remaining question concerns one action or record.
For example, you could say that you are following up on the request to correct the class preference in a previous enquiry, then ask which step remains. If the team has directed you to another administrator, make sure the new contact understands the specific service involved. Do not assume that every recipient has access to earlier communications.
This build does not create automated support tickets or guarantee a response deadline. It provides a contact route and practical guidance for making the request understandable. Ask the real operator how the request can be tracked through its own process. A message marked sent in your app shows the sending step in that app; it does not establish that every requested action has been completed.
Raise questions about a child's record carefully
A parent-managed request should use the minimum information needed to identify the relevant arrangement. If more than one learner is involved, distinguish the records without circulating sensitive details through a broad group. Ask the team which limited reference will help it locate the correct case.
The child's full name, school and private history should not become the default content of every support message. Begin with the adult contact and the type of request. A responsible verification discussion can then be tailored to the actual system and record, rather than prompted by an over-detailed first message.
The parent-managed enquiry page explains how to keep the initial conversation focused. It does not claim a formal consent or deletion mechanism for an uninspected portal. Where a separate service is involved, obtain the explanation that applies to that service and the person authorised to handle the record.
A short request structure to adapt
You can organise the first message into four parts: the service involved, your adult relationship to the enquiry, the type of help requested and the specific next question. Keep it readable enough that the recipient can identify the task quickly. An illustrative opening might say that you are the parent who made an enquiry through a named channel and want to correct the preferred lesson mode.
For an account you believe exists elsewhere, ask the team to confirm the platform and the appropriate administrator. For information already sent, ask how the relevant record can be reviewed or corrected. For a deletion question, identify the record and ask for the actual process and consequences.
Use the published contact options for that first conversation. This page remains honest about the role of the class and resource pages: no student account is created there, no automatic deletion is performed and no external system is silently controlled. Its purpose is to help an adult move from an uncertain request to a clear, correctly directed support discussion.
Separate a local resource question from an external account request
A visitor can read the resources and use the browser activities in this build without creating a student account. If a login screen appears on a different service, note its actual web address before asking for account help. The team needs to know which system you mean; the existence of a learning brand does not prove that every associated service shares one account database.
For information already sent by email or WhatsApp, describe the communication and the request using the adult contact involved where possible. Do not paste a password, one-time code or full payment credential into a general enquiry. The operator can explain an appropriate verification route if it is necessary to identify the relevant record.
This page does not issue a technical deletion command. It provides a contact path and the distinctions needed to frame a request. Any actual account or record-handling step belongs to the system and operator concerned, with its real process explained to the requester rather than inferred from this page's title.