Cookie Policy - Eduplore

1.1. This Cookie Policy explains how Eduplore, an Indian learning management system and learning application for students, teachers, schools, and parents, uses cookies, local storage, software development kits, and similar technologies on the website eduplore.in and in the Eduplore mobile application published on the Google Play Store (https://play.google.com/store/apps/details?id=com.eduplore.app). In this Policy, references to Eduplore, we, us, and our are references to the operator of eduplore.in and the Eduplore application. References to you and your are references to any person who accesses or uses the website, the application, or any service provided through them.

1.2. This Policy should be read together with the Privacy Policy, the Terms of Use, and the Disclaimer. The Privacy Policy explains what Personal Data Eduplore collects, why it collects it, how it uses it, how long it keeps it, who it shares it with, and what rights you have. This Cookie Policy focuses on the specific technologies listed in Section 3, on what each technology does, on how long it lasts, and on how you can manage or delete it. If there is any inconsistency between this Policy and the Privacy Policy on a question of Personal Data, the Privacy Policy will generally prevail, unless this Policy expressly states otherwise for a specific technology.

1.3. Eduplore is designed for students in Classes 8 to 10 in Karnataka, India, and for the teachers, schools, and parents who support them. The content is provided in Kannada and in English. Many users are Minors under the age of 18 years. This Policy therefore explains, in plain English, how cookies and similar technologies affect Minors, what consent is required from a Parent or Guardian, and how a Parent or Guardian can manage settings on behalf of a Minor. Section 12 deals with children's data in detail.

1.4. By accessing or using Eduplore, you acknowledge that you have read this Cookie Policy, that you understand how cookies and similar technologies are used, and that you accept the use described here, subject to the choices and controls described in Sections 10 and 11. If you do not agree with any part of this Policy, you should use the controls in Sections 10 and 11 to limit the technologies used, or you should not use Eduplore. If you are a Parent or Guardian of a student under the age of 18 years, you should read this Policy together with the student and explain it to the student in language the student can understand.

1.5. This Policy is written in plain English so that students, parents, teachers, and school administrators can understand it without legal training. Where a legal term is used, its meaning is explained in Section 2. Where Indian law is mentioned, the reference is given so that a reader can check the law, and the summary in this Policy is not a substitute for reading the law itself or for obtaining independent legal advice.

2.1. In this Policy, the following terms have the following meanings, unless the context requires otherwise.

2.2. Application means the Eduplore mobile application available on the Google Play Store, and any successor application published by Eduplore for the same service.

2.3. Website means eduplore.in and any subdomains or related web pages operated by Eduplore for the same service.

2.4. Platform means the Website and the Application together, and all services, features, and content provided through them.

2.5. Cookie means a small text file that a website places on a user's device, typically in the web browser, so that the website can remember information about the user's visit, such as language preference, login state, or pages visited. Cookies are described in more detail in Section 3.

2.6. Local Storage means storage provided by a web browser or by a mobile operating system that allows a website or an application to store data on a user's device, such as preferences, progress, or cached content, in a form that persists after the browser or application is closed, until the user deletes it or it is removed by the application.

2.7. Session Storage means storage provided by a web browser that holds data only for the duration of a single browsing session, and that is deleted when the browser tab or window is closed.

2.8. Software Development Kit, also called an SDK, means a set of software tools and code provided by a third party and included in an application, so that the application can use a service provided by that third party, such as analytics, crash reporting, push notifications, video playback, or payment processing.

2.9. Analytics means the collection and analysis of information about how users use the Platform, such as which pages are visited, which lessons are watched, how long a user spends on a lesson, which quizzes are attempted, and whether an error occurs, for the purpose of understanding use, improving the Platform, and fixing problems.

2.10. Personal Data means any data about an individual who is identifiable by or in relation to such data, as defined under the Digital Personal Data Protection Act, 2023.

2.11. Data Principal means the individual to whom Personal Data relates, as defined under the Digital Personal Data Protection Act, 2023. Where the Data Principal is a Minor, the Parent or Guardian acts on behalf of the Minor where the Act requires it.

2.12. Data Fiduciary means the person who alone or in conjunction with other persons determines the purpose and means of processing Personal Data, as defined under the Digital Personal Data Protection Act, 2023. Eduplore is the Data Fiduciary for the Personal Data it collects through the Platform, except where the Privacy Policy states that another person is the Data Fiduciary for a specific purpose.

2.13. Consent means consent given by a Data Principal, or, in the case of a Minor, by the Parent or Guardian, in accordance with the Digital Personal Data Protection Act, 2023, where consent is the lawful basis for processing.

2.14. Minor means a person under the age of 18 years, as defined under the Digital Personal Data Protection Act, 2023, and under general Indian law.

2.15. Parent or Guardian means a parent, legal guardian, or other person who has lawful responsibility for a Minor, and who gives consent on behalf of that Minor where consent is required.

2.16. Student means a person who uses the Platform to learn, whether that person is enrolled through a school, through a parent or guardian, or directly, and whether that person is under 18 years of age or 18 years of age or older.

2.17. Teacher means a person who uses the Platform to teach, assign work, review student progress, or manage a classroom, whether employed by a school or acting independently.

2.18. School means a government school, a private school, an aided school, a coaching institution, or any other educational institution that uses the Platform for its students or teachers.

2.19. Third Party means any person, organisation, service, website, application, or platform that is not Eduplore, including the Google Play Store, a payment processor, an analytics provider, a video hosting provider, and any external website linked from the Platform.

2.20. Do Not Track, also called DNT, means a setting in a web browser that sends a signal to websites asking them not to track the user's browsing activity. Section 11.7 explains how Eduplore responds to that signal.

3.1. A cookie is a small text file that a website asks a web browser to store on a user's device. When the user returns to the website, the browser sends the cookie back to the website, so that the website can recognise the device and remember information from the earlier visit. A cookie does not normally contain a person's name, address, or other direct identifier, but it may contain a unique identifier, such as a random string of letters and numbers, that allows the website to distinguish one device or browser from another.

3.2. Cookies are used for many different purposes. A cookie may remember that a user is logged in, so that the user does not have to log in again on every page. A cookie may remember a language preference, such as Kannada or English, so that the website shows the preferred language on the next visit. A cookie may remember what is in a shopping basket, which video was last watched, or which lesson was last opened. A cookie may also record which pages were visited, in what order, and for how long, so that the operator can understand how the website is used.

3.3. Local storage is similar to a cookie, but it can store larger amounts of data, and it is controlled through the browser's storage settings rather than through cookie settings. An application may use local storage to remember a user's preferences, to store a lesson for offline viewing where that feature is provided, to store progress so that it can be synced later, or to store a token that keeps the user logged in. Local storage persists until the user deletes it, until the application deletes it, or until the browser's data is cleared.

3.4. Session storage is similar to local storage, but it lasts only for a single session. When the user closes the browser tab or window, session storage is deleted. Session storage may be used to remember information while the user moves between pages in a single visit, such as a quiz in progress or a form that has been partly completed.

3.5. A software development kit, or SDK, is a piece of software included in a mobile application so that the application can use a service provided by a third party. For example, an analytics SDK may record how the application is used, a crash reporting SDK may record when the application stops working unexpectedly, a push notification SDK may deliver a reminder about a lesson, and a video SDK may play a video lesson. An SDK may use its own identifiers, cookies, or local storage, and may send data to the third party that provides the SDK, as described in the Privacy Policy and in Section 8.

3.6. Other similar technologies include web beacons, pixels, tags, and device identifiers. A web beacon or pixel is a tiny, often invisible, image or piece of code embedded in a web page or in an email, which records that the page was viewed or the email was opened. A tag is a piece of code that loads a service, such as an analytics service, when a page is viewed. A device identifier is a unique identifier assigned to a mobile device or to an application installation, which may be used to distinguish one device from another for analytics, for security, or for delivering a service.

3.7. Cookies, local storage, SDKs, and similar technologies are not inherently harmful, and many of them are necessary for a website or application to work properly. However, some of them can be used to track a user's activity across different websites or over a long period, and that is why this Policy explains what Eduplore uses, why it uses it, and how you can control it.

3.8. This Policy covers the technologies used on the Website and in the Application. It does not cover technologies used by a Third-Party Service that a user visits by following a link from the Platform, or by a website that is embedded in the Platform but operated by a Third Party. Those services have their own cookie policies, and the user should read them before using those services.

4.1. Eduplore uses cookies, local storage, session storage, SDKs, and similar technologies for the purposes described in this Section, and in Sections 5 to 8. The purposes are limited to operating the Platform, providing the educational service, improving the service, keeping the service secure, and, where applicable, communicating with users about the service.

4.2. Eduplore does not use cookies or similar technologies to sell Personal Data, and does not use them to share Personal Data with a data broker for the data broker's own marketing. Any sharing of data with a Third Party is described in the Privacy Policy and in Section 8 of this Policy, and is limited to the purposes described there.

4.3. Eduplore does not use cookies to collect sensitive personal information such as passwords in plain text, payment card numbers, or health information, and does not store such information in a cookie or in local storage in a form that is readable by any other website. Login tokens and session identifiers are stored in a form that is intended to be secure, and are protected as described in the Privacy Policy.

4.4. The specific cookies and technologies used may change over time, for example when Eduplore adds a new feature, changes an analytics provider, or updates the Application. Eduplore will update this Policy when a material change occurs, and will update the cookie list in Section 9 where practicable. The list in Section 9 is intended to be a helpful summary, not a complete technical inventory, and the purposes described in Sections 5 to 8 are the authoritative description of how the technologies are used.

5.1. Strictly Necessary cookies and similar technologies are those that are essential for the Platform to work. Without them, the Website or the Application cannot provide the basic service that the user has requested, such as logging in, moving between pages, or completing a purchase. These technologies are used on the basis that they are necessary for the provision of the service, and they cannot be switched off through the Platform's own settings, although a user may block them through browser settings as described in Section 11. If a user blocks a Strictly Necessary technology, parts of the Platform may not work.

5.2. Examples of Strictly Necessary technologies include a session cookie that keeps a user logged in while the user moves between pages, a security cookie that helps to prevent fraud and to detect unauthorised access, a load balancing cookie that directs a user to the correct server, and a cookie that remembers that a user has seen a notice, such as this Cookie Policy or a consent banner, so that the notice is not shown on every page.

5.3. Functional cookies and similar technologies are those that remember a user's choices and preferences, so that the Platform can provide a more personal and convenient experience. They are not strictly necessary for the Platform to work, but without them the experience is less convenient. A user may be able to disable some Functional technologies through the Platform's settings or through browser settings, as described in Section 11, and the Platform will continue to work, but with the relevant preference not remembered.

5.4. Examples of Functional technologies include a cookie or local storage entry that remembers the user's language preference, Kannada or English, a setting that remembers whether the user prefers a particular video quality, a setting that remembers the last lesson opened or the last position in a video, a setting that remembers the user's preferred text size or display mode where that feature is provided, and a setting that remembers that a user has dismissed a tutorial or a welcome message.

5.5. Functional technologies may also remember a user's progress in a course, such as which lessons have been completed, which quizzes have been attempted, and which bookmarks have been saved, so that the user can resume where they left off. That progress is also stored on Eduplore's servers as described in the Privacy Policy, so that it can be shown in progress reports and synced across devices where the user is logged in to the same Account.

5.6. Eduplore will take reasonable steps to ensure that Strictly Necessary and Functional technologies use the minimum data necessary for their purpose, that they are set with appropriate security attributes where applicable, such as the Secure flag for cookies sent over a secure connection and the HttpOnly flag where the cookie should not be accessible to client-side scripts, and that they expire after a reasonable period.

6.1. Analytics and performance technologies collect information about how users use the Platform, so that Eduplore can understand which lessons are popular, which topics are difficult, where users encounter errors, how long pages take to load, and how the Platform can be improved. The information is generally collected in aggregated or pseudonymised form, meaning that it is grouped together or linked to a random identifier rather than to a person's name, except where the Privacy Policy states that it is linked to an Account for the purpose of progress analytics.

6.2. Analytics may record the pages visited, the lessons watched, the time spent on a lesson, the quizzes attempted, the score obtained, the device type, the operating system, the browser type, the screen size, the approximate location derived from an internet address, and whether an error occurred. Analytics does not normally record the content of a user's private messages, the content of a user's answers beyond the score and the answer chosen for the purpose of marking, or any sensitive personal information.

6.3. Performance technologies measure how quickly pages load, whether a video plays smoothly, whether a Three-Dimensional Lab renders correctly, and whether any part of the Platform is slow or unavailable. That information helps Eduplore to fix problems, to improve loading times, and to decide which devices and browsers to support.

6.4. Preference technologies remember a user's choices, as described in Section 5. In the analytics context, a preference technology may also remember that a user has chosen not to be included in a particular type of analytics, where the Platform provides such a choice, so that the choice is respected on future visits.

6.5. Eduplore uses analytics to improve teaching, not to judge a Student. Analytics that are linked to a Student's Account are used to generate progress reports for the Student, for the Parent or Guardian, and for the Teacher, as described in the Privacy Policy. Analytics that are aggregated across many Students are used to understand which topics need better explanations, which quizzes are too easy or too difficult, and which features are most helpful.

6.6. Where Eduplore uses a third-party analytics provider, the provider may set its own cookies or use its own SDK, and may process data on Eduplore's behalf in accordance with a contract with Eduplore. The provider must not use the data for its own purposes except as described in the Privacy Policy and in Section 8. The user can manage third-party analytics cookies through the controls described in Section 11, and through the provider's own opt-out where one is provided.

6.7. Eduplore does not use analytics to track a Minor across other websites or applications, and does not use analytics to build a profile of a Minor for advertising. Any analytics relating to a Minor is limited to the educational purpose of the Platform, and is subject to the consent of the Parent or Guardian as described in Section 12.

7.1. Eduplore does not direct advertising at Minors, and does not use advertising cookies to track Minors for advertising purposes. This Section explains the position for adult users and for the Platform generally, so that the position is clear, and so that a Parent or Guardian can understand what does and does not happen on the Platform.

7.2. Advertising cookies, where used on any website, are cookies that are used to show a user advertisements that are relevant to that user, to limit the number of times a user sees the same advertisement, and to measure whether an advertisement was effective. They may be set by the website itself, or by a third-party advertising network, and they may track a user's browsing across different websites.

7.3. Eduplore does not currently use third-party advertising cookies to show personalised advertisements to users of the Platform, and does not sell advertising space to third-party advertisers that track users across the Platform. If Eduplore changes this position in the future, this Policy will be updated before any such advertising begins, and the change will be drawn to the attention of users, and the consent of the Parent or Guardian will be obtained for any Minor where consent is required by law.

7.4. The Platform may contain a notice, a banner, or a message about Eduplore's own courses, laboratories, or features, for example a message that a new laboratory is available, or that a course has been updated. That is not third-party advertising, and it is not based on tracking across other websites. It is a communication about Eduplore's own service, and it may be shown based on the user's use of the Platform, such as the class the user is studying or the course the user has enrolled in.

7.5. The Google Play Store, and any other store through which the Application is distributed, may show advertisements or recommendations that are governed by Google's own policies, and not by this Policy. Eduplore does not control the advertisements shown in the Google Play Store, and is not responsible for them.

7.6. If a user follows a link from the Platform to a Third-Party Service, that service may set its own advertising cookies. The user should read the cookie policy of that service, and should use the controls described in Section 11 to manage those cookies. Eduplore is not responsible for the advertising cookies set by a Third-Party Service.

7.7. Where an advertising cookie is used, the user will generally be able to opt out through the cookie settings provided by the Platform, through the browser settings, through the device's advertising settings, or through the advertising network's own opt-out page. Section 11 explains those controls in detail.

8.1. Eduplore uses a limited number of Third-Party Services to operate the Platform. Each service is chosen because it is necessary for a specific function, such as hosting videos, delivering content, analysing use, reporting crashes, sending push notifications, or processing payments. This Section summarises those services and the technologies they use. The full list of recipients of Personal Data, and the purposes for which data is shared, is in the Privacy Policy.

8.2. Video hosting and delivery. Video lessons may be hosted by a third-party video platform or content delivery network, so that videos load quickly and play smoothly. The video service may set cookies or use local storage to remember playback position, video quality, and whether a video has been watched. The video service may also collect analytics about video playback, as described in Section 6.

8.3. Analytics providers. Eduplore may use one or more analytics providers to understand how the Platform is used. The analytics provider may set cookies or use an SDK, and may collect the information described in Section 6. The provider processes the data on behalf of Eduplore, under a contract that limits the provider to the purposes instructed by Eduplore, and that requires the provider to protect the data.

8.4. Crash reporting and performance monitoring. Eduplore may use a crash reporting service to record when the Application stops working unexpectedly, what error occurred, and what device and operating system version were in use, so that the problem can be fixed. The crash report does not normally include the content of a lesson, the content of a quiz answer beyond what is necessary to reproduce the error, or any sensitive personal information.

8.5. Push notifications. Where a user has enabled notifications, Eduplore may use a push notification service to send reminders about a lesson, a quiz, or a new feature. The push notification service may use a device token, which is a unique identifier for the application installation on a device, so that the notification can be delivered to the correct device. The user can turn off notifications in the device settings or in the Application settings, as described in Section 11.

8.6. Payment processing. Payments for Subscriptions and In-App Purchases are generally processed by Google Play billing or by another authorised payment processor. The payment processor may set cookies or use its own technologies to process the payment, to prevent fraud, and to comply with legal obligations. Eduplore does not receive or store full payment card details, as described in the Privacy Policy.

8.7. Content delivery and security. Eduplore may use a content delivery network or a security service to deliver Content quickly, to protect the Platform from abuse, and to detect and prevent attacks. That service may set a cookie to distinguish a legitimate user from an automated request, and may collect an internet address and browser information for security purposes.

8.8. Each Third-Party Service has its own privacy policy and cookie policy, and the user should read those policies for the full detail of how that service uses cookies and similar technologies. Eduplore will take reasonable steps to ensure that each service is reputable, that it has appropriate security measures, and that it processes data only as instructed by Eduplore, but Eduplore does not control the operation of the service.

8.9. Eduplore does not authorise a Third-Party Service to use data collected through the Platform for the Third Party's own advertising, or to track Minors across other websites or applications, except where the Privacy Policy expressly states otherwise and the required consent has been obtained.

9.1. The table below is a summary of the categories of cookies and similar technologies that Eduplore uses, or may use, on the Platform. The specific names, providers, and durations may change over time, and the purposes described in Sections 5 to 8 are the authoritative description. Where a cookie name is given, it is an example of the type of cookie used, and the exact name may differ by browser, device, or version of the Platform.

9.2. Strictly Necessary. Purpose: to keep a user logged in, to maintain security, to balance load, and to remember that a notice has been seen. Duration: session cookies last until the browser or Application is closed, and persistent cookies in this category generally last for a period that is reasonable for the purpose, for example up to one year, unless the user deletes them earlier. Provider: Eduplore and, where applicable, a security or hosting provider acting on behalf of Eduplore.

9.3. Functional and Preferences. Purpose: to remember language preference, Kannada or English, video quality, last lesson, display preference, and other choices made by the user. Duration: generally persistent, for a period that is reasonable for the purpose, for example up to one year, or until the user changes the preference or deletes the data. Provider: Eduplore.

9.4. Analytics and Performance. Purpose: to understand how the Platform is used, to measure performance, to identify errors, and to improve Content and features. Duration: varies by provider, generally from a single session up to two years for a persistent analytics cookie, unless the user deletes it earlier or opts out. Provider: Eduplore and one or more analytics providers acting on behalf of Eduplore.

9.5. Push Notification and Device Token. Purpose: to deliver reminders and updates to a device where the user has enabled notifications. Duration: the device token persists until the user disables notifications, uninstalls the Application, or the operating system refreshes the token. Provider: the operating system provider and the push notification service acting on behalf of Eduplore.

9.6. Payment and Store. Purpose: to process a purchase through the Google Play Store or another authorised payment processor, and to verify that a purchase has been made. Duration: as determined by the payment processor and by the Google Play Store. Provider: Google and the payment processor.

9.7. Video Playback. Purpose: to play video lessons, to remember playback position and quality, and to measure video performance. Duration: session or persistent, depending on the video service, generally up to one year for a preference, and for a session for playback state. Provider: the video hosting or content delivery provider acting on behalf of Eduplore.

9.8. Security and Fraud Prevention. Purpose: to detect and prevent unauthorised access, abuse, and fraud, and to protect the Platform and its users. Duration: session or persistent for a reasonable period, for example up to one year. Provider: Eduplore and a security provider acting on behalf of Eduplore.

9.9. Eduplore will review this list periodically, and will update it when a new category is added or when a category is removed. If a user has a question about a specific cookie or technology, the user may contact Eduplore using the details in Section 15, giving the name of the cookie or technology where known, and the browser or device used.

10.1. You have choices about cookies and similar technologies. This Section explains how to manage cookies in a web browser when using the Website. Section 11 explains how to manage settings in the Application, how to manage advertising identifiers on a device, and how Do Not Track works.

10.2. Cookie banner and consent. When you first visit the Website, you may be shown a cookie banner or notice that explains that cookies are used and that gives you a choice, for example to accept all cookies, to reject non-essential cookies, or to choose which categories to allow. Your choice will be remembered, and you can change it later through the cookie settings link on the Website, where provided, or through your browser settings as described in this Section.

10.3. Browser settings. Every major web browser allows you to control cookies through its settings. You can generally choose to block all cookies, to block third-party cookies only, to delete cookies that have already been set, to be asked before a cookie is set, or to delete cookies automatically when the browser is closed. The exact steps depend on the browser and the version, and the browser's help pages will give the current instructions.

10.4. Google Chrome. In Google Chrome, you can manage cookies by opening Settings, then Privacy and security, then Third-party cookies, where you can block third-party cookies, see the cookies that have been set, and delete cookies for a specific site. You can also clear browsing data, including cookies, by opening Settings, then Privacy and security, then Delete browsing data. The steps may change with new versions of Chrome, and the help pages for Chrome will give the current steps.

10.5. Mozilla Firefox. In Mozilla Firefox, you can manage cookies by opening Settings, then Privacy and Security, then Cookies and Site Data, where you can manage exceptions, delete cookies, and choose how long cookies are kept. You can also use the Enhanced Tracking Protection settings to control tracking. The steps may change with new versions of Firefox, and the help pages for Firefox will give the current steps.

10.6. Apple Safari. In Apple Safari on a Mac, you can manage cookies by opening Settings or Preferences, then Privacy, where you can block cookies, remove stored website data, and manage website data. In Safari on an iPhone or iPad, you can manage cookies by opening Settings, then Safari, then Privacy and Security, where you can block cookies and clear history and website data. The steps may change with new versions of Safari, and the help pages for Apple will give the current steps.

10.7. Microsoft Edge. In Microsoft Edge, you can manage cookies by opening Settings, then Cookies and site permissions, then Manage and delete cookies and site data, where you can block cookies, see cookies that have been set, and delete cookies for a specific site. You can also clear browsing data by opening Settings, then Privacy, search, and services, then Clear browsing data. The steps may change with new versions of Edge, and the help pages for Microsoft will give the current steps.

10.8. Other browsers. If you use a different browser, such as Brave, Opera, or a browser on a mobile device, the browser's settings will include a privacy or cookies section where you can block, delete, or manage cookies. The browser's help pages will give the current steps for that browser.

10.9. Effect of blocking cookies. If you block all cookies, or if you delete cookies, some parts of the Website may not work as intended. For example, you may need to log in again on every visit, your language preference may not be remembered, your progress may not be shown until you log in and the data is loaded from the server, and a video may not remember where you stopped watching. Strictly Necessary cookies cannot be disabled through the Website's own settings without affecting the basic operation of the Website, as explained in Section 5.

11.1. Managing cookies in the Application is different from managing cookies in a web browser, because a mobile application does not use a browser in the same way. The Application uses local storage, SDKs, and device identifiers, as described in Section 3, and those are managed through the Application settings and through the device settings, as explained in this Section.

11.2. Application settings. Inside the Application, you may be able to manage certain settings, such as language preference, video quality, notifications, and whether analytics are included, where the Application provides those settings. The exact settings available may change with new versions of the Application. If a setting is not available in the Application, you can use the device settings described below, or you can contact Eduplore using the details in Section 15.

11.3. Clearing application data on Android. On an Android device, you can clear the Application's cached data or all of its stored data by opening Settings, then Apps, then Eduplore, then Storage, where you can choose Clear cache or Clear data. Clearing the cache generally removes temporary files, and the Application will continue to work, but may need to reload some content. Clearing all data generally removes local storage, preferences, and login state, so you will need to log in again, and any content stored for offline use, where that feature is provided, may need to be downloaded again. The steps may change with new versions of Android, and the help pages for the device will give the current steps.

11.4. Clearing application data on other devices. If you use the Website on a mobile browser, you can clear cookies and site data through the browser settings as described in Section 10. If you use Eduplore on any other device, you can use that device's settings to manage application data, or you can uninstall and reinstall the Application, which generally removes local storage and SDK data, although data stored on Eduplore's servers, such as progress linked to your Account, will remain as described in the Privacy Policy.

11.5. Notifications. You can turn off push notifications by opening the device Settings, then Apps, then Eduplore, then Notifications, and turning notifications off, or by using the notification settings inside the Application where provided. Turning off notifications does not delete any data, and does not affect your ability to use the Platform, but you will not receive reminders about lessons, quizzes, or new features.

11.6. Advertising identifiers on Android. An Android device has an advertising identifier, which is a unique identifier that applications can use for advertising purposes. You can manage that identifier by opening Settings, then Privacy, then Ads, where you can delete the advertising identifier or opt out of ads personalisation. Deleting the advertising identifier creates a new identifier, and opting out of ads personalisation tells applications not to use the identifier to show personalised advertisements. Eduplore does not use the advertising identifier to show personalised advertisements to Minors, as explained in Section 7, and does not use it to track Minors for advertising.

11.7. Do Not Track. Do Not Track, or DNT, is a setting in some web browsers that sends a signal to websites asking them not to track the user's browsing activity. There is no single, legally binding standard for how a website must respond to a Do Not Track signal, and different websites respond in different ways. Eduplore respects the choice that a user makes through the cookie banner and through the browser settings described in Section 10, and will not use the Do Not Track signal as a substitute for those choices. If you enable Do Not Track in your browser, Eduplore will continue to use Strictly Necessary technologies so that the Platform works, and will continue to respect any choice you have made through the cookie banner or through your browser settings to block or delete cookies. If you wish to limit tracking, the most reliable method is to use the cookie controls in Section 10, to block third-party cookies in your browser, and to use the Application and device controls in this Section.

11.8. Global Privacy Control. Some browsers and browser extensions support a Global Privacy Control signal, which is similar to Do Not Track and which asks websites not to sell or share personal information. Eduplore does not sell Personal Data, as explained in Section 4.2 and in the Privacy Policy. Where a Global Privacy Control signal is received, Eduplore will treat it as a request to limit the use of non-essential cookies where practicable, and will respect any choice made through the cookie banner.

11.9. Opting out of analytics. Where an analytics provider offers its own opt-out, for example a browser add-on that prevents the provider's cookies from being set, or a setting on the provider's website, you may use that opt-out in addition to the controls in this Policy. Eduplore will provide a link to any such opt-out where it is available and where Eduplore is aware of it, and will update this Policy if the provider changes.

11.10. Effect of managing settings in the Application. If you clear application data, delete the advertising identifier, or turn off notifications, the Application will continue to work for its core educational purpose, but some conveniences may be lost, such as remembered preferences, offline content where provided, and reminders. Progress that is stored on Eduplore's servers and linked to your Account will generally be restored when you log in again, as described in the Privacy Policy.

12.1. Eduplore is used by Minors, and this Section explains how cookies and similar technologies affect Minors, what consent is required, and how a Parent or Guardian can exercise control. The full detail about children's Personal Data is in the Privacy Policy, which should be read together with this Policy.

12.2. Under the Digital Personal Data Protection Act, 2023, the Personal Data of a Minor may be processed only with the verifiable consent of a Parent or Guardian. Eduplore will obtain that consent before collecting Personal Data from a Minor through cookies or similar technologies, where consent is the lawful basis for the processing, and will take reasonable steps to verify that the consent is given by a Parent or Guardian.

12.3. Eduplore must not undertake tracking or behavioural monitoring of Minors, and must not direct advertising at Minors, except to the extent permitted by the Digital Personal Data Protection Act, 2023, and by any rules made under it. Eduplore complies with those requirements. Analytics relating to a Minor are limited to the educational purpose of the Platform, such as recording which lessons the Minor has completed and which quizzes the Minor has attempted, so that progress can be shown to the Minor, to the Parent or Guardian, and to the Teacher.

12.4. A Parent or Guardian should review the cookie and application settings on the device used by a Minor, should discuss with the Minor what cookies and similar technologies are, should help the Minor to understand that some technologies are necessary for the Platform to work and that others can be limited, and should make the choices described in Sections 10 and 11 on behalf of the Minor where the Minor is not able to make those choices alone.

12.5. A Parent or Guardian may, at any time, withdraw consent for the processing of a Minor's Personal Data, subject to the consequences explained in the Privacy Policy. Withdrawal of consent may mean that the Minor can no longer use certain features of the Platform, or can no longer use the Platform at all, if the feature or the Platform cannot be provided without the data. Eduplore will explain the consequence at the time the withdrawal is requested, and will take reasonable steps to delete the Minor's Personal Data as described in the Privacy Policy, subject to any legal obligation to retain it.

12.6. A Parent or Guardian may request information about what cookies and similar technologies have been used in relation to a Minor's Account, may request a copy of the Minor's Personal Data, may request correction or deletion of that data, and may raise a grievance, in each case as described in the Privacy Policy and in Section 15 of this Policy. Eduplore may ask for verification that the person making the request is the Parent or Guardian of the Minor, before sharing any information about the Minor.

12.7. Teachers and Schools should ensure that they have the necessary consent from Parents or Guardians for Students under 18 years of age before enrolling those Students on the Platform, and should inform Parents and Guardians about the use of cookies and similar technologies. A School that enrols Students should have a process for answering questions from Parents about cookies, analytics, and data, and should direct Parents to this Policy and to the Privacy Policy.

12.8. Minors should not change cookie, application, or device settings without the guidance of a Parent, Guardian, or Teacher, should not accept cookies or permissions on behalf of another person, and should not share passwords, one-time passwords, or other login details. If a Minor is unsure about a notice, a banner, or a permission request, the Minor should ask a Parent, Guardian, or Teacher before proceeding.

12.9. If Eduplore becomes aware that Personal Data has been collected from a Minor without the verifiable consent of a Parent or Guardian, Eduplore will take reasonable steps to delete that data, subject to any legal obligation to retain it, and will inform the Parent or Guardian where practicable.

13.1. Retention means how long a cookie, a local storage entry, or other data is kept before it is deleted or expires. Different technologies have different retention periods, as summarised in Section 9. Session cookies and session storage are deleted when the browser or Application session ends. Persistent cookies and local storage persist until they expire, until the user deletes them, or until the Application deletes them.

13.2. Eduplore will set retention periods that are reasonable for the purpose of the technology. A language preference may be kept for up to one year, so that the user does not have to choose a language on every visit. An analytics cookie may be kept for up to two years, so that Eduplore can understand use over time, unless the user deletes it earlier or opts out. A security cookie may be kept for a shorter period, for example for the duration of a session or for a few days, so that it does not persist longer than necessary.

13.3. Data collected through cookies and similar technologies, and stored on Eduplore's servers, is retained as described in the Privacy Policy. That Policy explains how long different types of Personal Data are kept, when data is deleted, and how a user can request deletion. The retention periods in this Policy apply to the technology on the user's device, and the retention periods in the Privacy Policy apply to the data stored on Eduplore's servers.

13.4. Security. Eduplore takes reasonable technical and organisational measures to protect the data collected through cookies and similar technologies, including using secure connections where practicable, setting cookies with appropriate security attributes where applicable, limiting access to the data to persons who need it for the purposes described in this Policy, and reviewing the security of Third-Party Services. The full detail of security measures is in the Privacy Policy.

13.5. No method of transmission over the internet, and no method of electronic storage, is completely secure. Eduplore does not warrant that data collected through cookies or similar technologies will never be accessed by an unauthorised person, but it will take reasonable steps to protect it, and will respond to a security incident as described in the Privacy Policy and as required by the Digital Personal Data Protection Act, 2023, and by the Information Technology Act, 2000.

13.6. A user can reduce the risk to their own data by keeping the browser and the Application up to date, by using a secure network, by not sharing login details, by logging out on a shared device, and by deleting cookies and local storage on a shared device after use, as described in Sections 10 and 11.

14.1. Under the Digital Personal Data Protection Act, 2023, a Data Principal has rights in relation to their Personal Data, including the right to access a summary of the Personal Data being processed, the right to request correction or completion of Personal Data, the right to request erasure of Personal Data, the right to withdraw consent where consent is the basis for processing, and the right to raise a grievance. The full detail of those rights, and how to exercise them, is in the Privacy Policy.

14.2. In relation to cookies and similar technologies specifically, a user has the right to choose which non-essential cookies to accept, to change that choice at any time through the cookie settings or through browser settings, to delete cookies and local storage as described in Sections 10 and 11, to opt out of analytics where an opt-out is provided, and to turn off notifications and to manage advertising identifiers as described in Section 11.

14.3. To exercise a right under the Digital Personal Data Protection Act, 2023, a user may contact Eduplore using the details in Section 15, giving the user's name, Account details where relevant, the right the user wishes to exercise, and any information that will help Eduplore to identify the data concerned. Eduplore may ask for verification of identity before acting, to protect the user's data from unauthorised access.

14.4. Where the Data Principal is a Minor, the Parent or Guardian may exercise the Minor's rights on behalf of the Minor, as described in Section 12. Eduplore may ask for verification that the person is the Parent or Guardian of the Minor, before sharing any information about the Minor or acting on a request.

14.5. Eduplore will respond to a request within the time prescribed by the Digital Personal Data Protection Act, 2023, and by any rules made under it, subject to the nature of the request and to any further information reasonably required from the user. If Eduplore cannot comply with a request, it will explain why, and will inform the user of the right to raise a grievance as described in Section 15 and in the Privacy Policy.

14.6. A user also has rights under the Consumer Protection Act, 2019, where the user is a consumer, and under the Information Technology Act, 2000, where applicable. Those rights are not affected by this Policy, and this Policy should be read subject to them.

14.7. A user who believes that Eduplore has not complied with this Policy, or with the Digital Personal Data Protection Act, 2023, may raise a grievance with Eduplore as described in Section 15, and may also complain to the Data Protection Board of India, or to any other appropriate authority, as described in the Privacy Policy.

15.1. If you have a question about this Cookie Policy, if you wish to change your cookie choices, if you wish to exercise a right under the Digital Personal Data Protection Act, 2023, or if you wish to make a complaint about the use of cookies or similar technologies, you may contact Eduplore using the details below.

15.2. General contact email: venkatesh@eduplore.in

15.3. Grievance Officer: Venkatesh C

15.4. Grievance Officer email: venkatesh@eduplore.in

15.5. Registered address: 1st Floor, SLA Inn, 7, Hootagalli, Hutagalli, Mysuru, Karnataka 570018

15.6. Data Protection Officer, where one has been appointed: Revant

15.7. Data Protection Officer email: revanth@eduplore.in

15.8. In accordance with the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, where they apply, the Grievance Officer will acknowledge a complaint within the time prescribed by the Rules, and will resolve the complaint within the time prescribed by the Rules, subject to the nature of the complaint and to any further information reasonably required from the complainant.

15.9. When you contact Eduplore, please give your name, your Account details where relevant, a clear description of the question or issue, and the browser or device you are using, where relevant. Eduplore will treat your contact as confidential, subject to the need to investigate the issue and to comply with any legal obligation.

15.10. Parents, Guardians, Teachers, and Schools may contact Eduplore on behalf of a Student, giving the Student's name and class where relevant, and explaining their relationship to the Student. Eduplore may ask for verification of that relationship before sharing any information about the Student's Account.

16.1. Eduplore may update this Cookie Policy from time to time, for example to reflect a change in the law, a change in the cookies or technologies used, a change in the Third-Party Services used, a change in the Platform, or a change in Eduplore's practices. The updated version will be published on eduplore.in and, where practicable, inside the Application.

16.2. The Last Updated date at the top of this page will show the date on which the current version was last updated. Users should check this page periodically for changes. Continued use of the Platform after an update means that the user accepts the updated Policy, subject to any rights the user has under applicable law, and subject to any new consent that is required by law.

16.3. Where a change is material, for example where a new category of cookie is added, where a new Third-Party Service is used, or where the purpose of an existing technology changes, Eduplore will take reasonable steps to draw the user's attention to the change, for example by a notice on the Website or in the Application, by an update to the cookie banner, or by an email to the email address associated with the Account, where the user has provided one and has not opted out of such notices.

16.4. If you do not agree with an updated version of this Cookie Policy, you should use the controls in Sections 10 and 11 to limit the technologies used, or you should stop using the Platform and, if you have an Account, you may close the Account in accordance with the Terms of Use and the Privacy Policy. Any rights or obligations that arose before the update will continue to be governed by the version of the Policy that was in force at the time.

17.1. This Cookie Policy is governed by the laws of India. The principal laws that apply to cookies, Personal Data, and online services in India include the Information Technology Act, 2000, the Digital Personal Data Protection Act, 2023, and the Consumer Protection Act, 2019, together with the rules made under those Acts, including the Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021, and the Consumer Protection (E-Commerce) Rules, 2020, where applicable.

17.2. The Digital Personal Data Protection Act, 2023, requires that Personal Data be processed with consent or another lawful basis, that the Data Principal be given notice of the data collected and the purpose, that the Data Principal have rights to access, correction, erasure, and grievance redressal, and that the Data Fiduciary take reasonable security safeguards. This Policy, together with the Privacy Policy, is intended to meet those requirements in relation to cookies and similar technologies.

17.3. The Information Technology Act, 2000, and the rules made under it, require intermediaries to follow due diligence, to publish a grievance redressal mechanism, and to act on complaints within the prescribed time. Eduplore will comply with those requirements where they apply to the Platform.

17.4. The Consumer Protection Act, 2019, protects consumers from unfair trade practices, and gives consumers the right to complain to a consumer forum. Nothing in this Policy limits any right that a user has as a consumer under that Act.

17.5. This Policy should be read together with the Privacy Policy, the Terms of Use, and the Disclaimer. The Privacy Policy is the authoritative document on Personal Data, the Terms of Use are the authoritative document on the contract for use of the Platform, and the Disclaimer is the authoritative document on the limits of the educational Content and the Three-Dimensional Labs.

17.6. If any provision of this Policy is found to be unlawful, void, or unenforceable by a court or tribunal of competent jurisdiction, that provision will be read as limited to the extent necessary to make it lawful and enforceable, or, if it cannot be so limited, it will be severed, and the remaining provisions will continue in full force and effect.

18.1. This Annex gives practical examples of how this Cookie Policy applies in everyday use. The examples are illustrative only, and they do not change the terms in Sections 1 to 17. If there is any difference between an example and a Section, the Section prevails.

18.2. Example for a Student. If a Student chooses Kannada as the language, a Functional cookie or local storage entry remembers that choice, so that the Platform shows Kannada on the next visit. If the Student deletes cookies, the Platform will show the default language on the next visit, and the Student will need to choose Kannada again.

18.3. Example for a Parent. If a Parent wishes to limit analytics for a Minor, the Parent can use the cookie settings on the Website to reject non-essential cookies, can block third-party cookies in the browser, and can check the Application settings on the device. The Parent can also contact Eduplore to ask what analytics are used for the Minor's Account.

18.4. Example for a Teacher. If a Teacher uses the Website on a shared computer at school, the Teacher should log out after use, and should delete cookies and browsing data on the shared computer, so that the next person who uses the computer does not have access to the Teacher's Account.

18.5. Example for a School. If a School provides devices for Students, the School should set the browser and device settings so that cookies are managed in a way that is consistent with the School's policies and with the consent given by Parents, and should inform Students and Parents about those settings.

18.6. Example for a purchase. If a user makes a purchase through the Google Play Store, Google may set its own cookies to process the payment. Those cookies are governed by Google's policies, not by this Policy, and the user should read Google's policies for the detail.

18.7. These examples are intended to help users apply this Policy in practice. They are not a complete list of situations, and users should apply the principles in this Policy to any new situation, and should contact Eduplore if they are unsure.