A note before this policy takes effect
The app’s data practices have not been supplied for verification. This draft must be reviewed and completed by Caco Innovations before it is used as the official Google Play privacy policy. Review notes below identify what still needs confirmation.
View verification notesIntroduction and scope
This document concerns HS School App (HelloStores School App), provided by Caco Innovations in India. It is intended for students, parents or guardians, teachers, and school administrators who use the app.
It describes the privacy topics that apply to the app and how to contact Caco Innovations about personal information. It concerns the Android application identified as com.edubridge.edubridge. A school may also provide its own notices covering information it manages independently.
This is a draft pending verification of the app’s actual data practices. It is not yet an effective statement of those practices. The effective date will be set when Caco Innovations completes its review and approves the policy.
Information collected from users
The information collected by HS School App has not yet been verified. No specific category of information, device permission, or collection method is represented here as being used by the app.
The final policy must identify information entered by users, supplied by a school, or collected automatically, if any. It must explain which information is required, which is optional, why it is needed, and what happens if a user chooses not to provide it.
Confirm all collected data categories, sources, permissions, and automatic collection against the app, its server services, and its included SDKs.
Student, parent, teacher, and administrator information
Different members of a school community may interact with different parts of the app. The final policy must distinguish the information handled for students, parents or guardians, teachers, and school administrators, rather than assume that every role provides the same information.
Whether the app handles school records, account details, communications, or any other role-specific information remains unverified. The final policy must also explain who supplies each type of information and which school roles can access it.
Confirm the actual information and access available to each user role, including any sensitive information concerning children.
How personal information is used
Each use of personal information must be tied to an actual app function and explained in the final policy. A purpose should not be listed merely because it is common in other school applications.
The developer must verify whether information is used to operate accounts, deliver school services, facilitate communications, provide support, maintain the service, or for any other purpose. Any advertising, profiling, or automated decision-making must be separately disclosed if present.
Map every verified data category to its specific purpose and applicable basis for processing; confirm whether any secondary use occurs.
Data storage and security
The app’s hosting arrangements, storage locations, and security measures have not been verified for this document. This draft does not assert encryption, a particular hosting country, or a security certification.
Before approval, Caco Innovations must describe the safeguards that are actually implemented, how access is managed, and whether information is transferred or stored outside India. No system can be guaranteed to be completely secure.
Verify hosting providers, locations, access controls, transfer arrangements, and any security statements before adding them to the policy.
Third-party services
No third-party service has been confirmed as part of HS School App. No provider is identified in this draft as receiving app information.
The developer must review the production app and its dependencies. Only services actually used should appear in the approved policy, together with their purpose, relevant data handling, and a link to the provider’s privacy notice.
Review all SDKs and services, including any authentication, notifications, crash reporting, hosting, or analytics services. Do not list an unused provider.
Children’s privacy and consent
As a school application, HS School App may be used in a context involving children. Its actual intended ages, availability to children, and consent arrangements must be confirmed before this policy is approved.
The final policy must explain the role of the school and parent or guardian, how any required authorization is obtained, and how a parent or guardian can raise a concern or request a review of a child’s information. This draft does not assert that consent is already collected or that a school’s authorization replaces parental consent.
Parents, guardians, and schools may contact the privacy email below with questions. Please avoid sending a child’s school records or other sensitive information in an initial email.
Confirm intended age groups, applicable child-privacy obligations, consent and verification processes, and any restrictions on child accounts.
Data retention and deletion requests
Retention periods and deletion behavior have not been verified. The final policy must explain how long each relevant category is retained, or the criteria used to decide this, including any school-controlled records, backups, or required retention.
To raise a deletion request or ask about retention, email nitheshreddy.email@gmail.com with the subject “HS School App – Privacy request”. Identify your relationship to the school and provide only the minimum details needed to describe your request. Do not send passwords.
The developer must confirm how identity and authority are checked, which requests are handled by a school, how app accounts can be deleted if accounts exist, and any limits or timelines. This draft does not promise a particular deletion outcome or deadline.
Confirm retention schedules, deletion steps, backup handling, exceptions, and whether Google Play requires a separate account-deletion request webpage for this app.
Your rights and choices
Privacy rights depend on applicable law, the information involved, and the respective roles of Caco Innovations and the school. Requests may concern access, correction, deletion, withdrawal of consent where applicable, or questions about how information is handled.
You can raise a privacy question using the contact details in this document. The approved policy must explain how applicable requests are assessed, any necessary identity checks, the school’s involvement, available complaint channels, and any applicable response periods. This draft does not guarantee rights or procedures that have not been confirmed.
Confirm applicable rights and the actual process for exercising them, including any relevant grievance contact or escalation requirements.
Changes to this policy
Caco Innovations may update this document to reflect verified app practices or other relevant changes. The last updated date identifies the most recent revision of this page.
Before an approved version becomes effective, its effective date must be published here. The developer must determine how users will receive notice of material changes and whether a new consent or other action is required.
Contact us
For questions about this document, or to raise a privacy-related request concerning HS School App, contact Caco Innovations using the details below.
Please include “HS School App – Privacy request” in your email subject. Share only what is necessary to explain your question; do not include passwords or sensitive student records.