Cookie Policy

1. What Are Cookies and Similar Technologies?

Cookies are small text files stored on a browser or device. ScholarSync may also use related technologies such as local storage, session storage, software development kits (SDKs), mobile identifiers, pixels, and similar technical tools. In this Policy, we refer to these technologies collectively as "cookies".

2. Types of Cookies and Technologies We May Use

2.1 Strictly Necessary

These technologies support essential functions such as authentication, session management, security, access control, load balancing, and core platform operation. Blocking them may prevent parts of the Service from working correctly.

2.2 Preferences and Functionality

These technologies may remember settings such as language, display choices, dismissed notices, or other preferences so the Service can provide a more consistent experience.

2.3 Analytics and Performance

ScholarSync may use analytics technologies, including Google Firebase analytics where configured, to understand feature usage, session activity, performance, errors, and aggregate usage patterns so we can improve the Service.

2.4 Notifications and Mobile Technologies

Our mobile applications may use SDKs and device tokens, including Firebase Cloud Messaging tokens, to deliver assignments, grades, messages, reminders, and other authorized notifications. Invalidated push tokens are automatically cleaned up in accordance with our retention practices.

2.5 Advertising

ScholarSync is an educational platform. We do not use cookies to sell personal data. If advertising or marketing cookies are introduced in the future, we will update this Policy and provide appropriate notice and consent controls where required by law.

3. Information Collected Through These Technologies

Depending on the technology and device, information may include device type, operating system, browser type, screen resolution, IP address, access times, pages or features used, session duration, error logs, notification tokens, and cookie or local-storage identifiers. We do not intend to store passwords, grades, assignment content, or facial embeddings directly in browser cookies.

4. Why We Use Cookies

• Keep users signed in and authenticate sessions.
• Apply role-based access and security controls.
• Remember user preferences and Service settings.
• Deliver and manage push notifications.
• Monitor performance, diagnose errors, and protect against abuse.
• Understand aggregated Service usage and improve features.

5. Third-Party Technologies

ScholarSync uses service providers described in our Privacy Policy. Relevant technologies may include Microsoft Azure for hosting and infrastructure and Google Firebase for notifications and analytics. OpenAI / Azure OpenAI and Bhashini (MeitY) may support AI, translation, or speech features; their use is governed by the feature being provided and our data-minimization practices rather than by a general-purpose advertising cookie program.

Third-party providers may process technical information under their own terms and privacy policies. We seek to configure integrations so that they receive only information reasonably necessary for their function.

6. Your Choices

You can control browser cookies through your browser or device settings. Depending on the ScholarSync application and implementation, additional in-product controls may be provided for optional analytics, notifications, or other non-essential technologies. Disabling strictly necessary technologies may cause login, security, or other core functions to stop working.

You can also withdraw consent for optional features where consent applies. For school-managed accounts, some settings may be controlled by the educational institution or administrator, subject to applicable law and the institution's policies.

7. Children and School-Managed Accounts

Because ScholarSync is designed for K-12 use, cookie and device information may relate to users under 18. Student accounts are created by school administrators rather than directly by minors. We seek to limit technical collection to what is reasonably necessary to provide, secure, and improve the educational Service, with parent/guardian consent where required for optional features.

8. Retention

Cookie lifespans vary by purpose. Session technologies may expire when a session ends, while persistent identifiers may remain for a defined period. Information derived from cookies or SDKs may also be retained in security, analytics, or application logs according to the retention periods described in the ScholarSync Privacy Policy. Invalid push notification tokens are automatically cleaned up.

9. Security

ScholarSync uses technical and organizational safeguards described in the Privacy Policy, including TLS encryption in transit, access controls, multi-tenant isolation measures, authentication controls, and rate limiting. Cookie and token values should be treated as security-sensitive where they can identify or authenticate a session.

10. Changes to This Cookie Policy

We may update this Cookie Policy as our technology, integrations, or legal obligations change. The updated version will be posted with a revised "Last updated" date. Where a change materially affects optional tracking or consent choices, we will provide additional notice or controls as appropriate.

11. Contact Us

For questions about this Cookie Policy or our use of cookies and similar technologies, contact:

Email: [email protected]
Organization: ScholarAI Systems OPC Pvt Ltd
Location: Bangalore, Karnataka, India