Home About
HealNTrack VaidSetu Bizcare Scholarly All Products
Healthcare Solutions Software Development Manufacturing ERP IT Consulting
Contact
Contact Us WhatsApp

Scholarly Privacy Notice

How Galant processes student, researcher and institutional information through Scholarly when acting as a processor for universities, colleges and schools.

Effective date: November 20, 2026  |  Last updated: November 20, 2026

1. Read this notice with your institution’s notice

Scholarly is an AI research workspace provided to universities, colleges and schools. The institution that gives its students, researchers, faculty and administrators access to Scholarly normally decides why and how their information is processed, and therefore acts as the Data Fiduciary or Controller. Galant normally processes that information on the institution’s documented instructions as its Data Processor or Processor.

The institution’s own privacy notice, policies and any consents it collects apply to its use of Scholarly. This notice explains Galant’s role and baseline practices. Where Galant itself decides the purpose of processing (for example website enquiries, licence administration, billing or security of Galant’s own systems), the Corporate Website Privacy Policy applies.

Scholarly may also be deployed in a hybrid arrangement in which the institution hosts its own database and files. In that case the institution’s hosting terms and security controls apply to the data it hosts.

2. Information that may be processed

Depending on how the institution configures Scholarly, the product may process:

2.1 Account and organisation data

  • name, email address, role, department and profile details provided by the user or the institution;
  • sign-in credentials (stored hashed where applicable) or, where the institution enables single sign-on, identity attributes supplied by the institution’s identity provider;
  • organisation membership, groups, invitations and sharing settings;
  • API keys that an institution chooses to supply for optional integrations or its own AI models, which are stored encrypted.

2.2 Research and academic content

  • uploaded PDF and Word documents, titles and metadata;
  • highlights, annotations and notes;
  • AI-generated summaries, answers, note explanations and review drafts;
  • manuscripts, versions, reviewer comments, ratings and decisions entered by reviewers or supervisors;
  • search terms entered in Search Literature.

2.3 Usage and diagnostics

  • access times and feature use needed for security, reliability and rate limiting;
  • optional first-party page paths and pseudonymous session keys for product-usage reporting, without third-party advertising trackers when this mode is enabled.

Do not upload health records, government identifiers, payment-card details or other regulated or sensitive personal data unless the institution’s deployment has been approved for that use. The exact data set is defined in the institution’s order form, deployment documentation or data-processing terms.

3. Why information is processed

Galant processes institution-controlled information only to:

  • provide, host, configure and support the contracted Scholarly service;
  • authenticate users and enforce access controls and organisation boundaries;
  • deliver the features users request, including upload, library, reading, annotation, sharing, supervision, manuscript review, overlap screening, search and AI analysis;
  • keep the service secure, detect abuse and maintain backups and continuity;
  • respond to feedback and support requests; and
  • follow the institution’s documented instructions and applicable law.

Galant does not sell personal information and does not use Scholarly content for advertising.

4. AI processing and model training

To produce summaries, answers and annotation help, text from a document is sent to the AI services configured for the deployment. These may be open-source models run on managed GPUs operated for Galant, or, in a hybrid deployment, models running on the institution’s own infrastructure. An institution may also configure its own model provider; in that case content is processed under the institution’s arrangement with that provider.

Galant does not use customer documents, annotations, notes, manuscripts, review content or AI outputs to train or fine-tune AI models, and does not permit a model or infrastructure provider acting for Galant to do so. Any customisation using an institution’s content would take place only if the institution requests it under a separate written agreement and the processing is legally permitted.

AI output is assistive. It can be incomplete or incorrect and must be checked by the user. See the AI & Medical Use Disclaimer.

5. Literature search

When a user runs Search Literature, the words typed are sent to each public scholarly index that is switched on and selected: OpenAlex, PubMed, Europe PMC, Crossref, ClinicalTrials.gov, DOAJ, DataCite, arXiv and OpenAIRE. Galant’s service contact email address may be sent with these requests. Nothing from the user’s uploaded documents is sent to these indexes. Opening a result’s details may ask Europe PMC or OpenAlex for the abstract using the paper’s DOI.

A search topic can reveal unpublished work. Users can untick sources under Search options, and the institution’s administrator can switch sources off. Each index’s own privacy terms apply to the information it receives.

6. Students, minors and academic data

Scholarly is provided to institutions, not directly to individual students. The institution decides which students, staff and researchers receive accounts, and is responsible for giving its own notices and obtaining any consent or authorisation the law requires. For people under 18 this includes the consent of a parent or lawful guardian where required by applicable law, such as the Digital Personal Data Protection Act, 2023 in India.

Galant does not use student personal data for advertising, marketing to students or behavioural tracking for advertising purposes. Galant personnel access customer content only as needed for support requested by the institution, to investigate security incidents or misuse, or to meet legal obligations.

Scholarly’s AI features, overlap screening and review drafts are decision support. They do not make decisions about students. Institutions should not rely on them alone for grading, admission, academic-misconduct or disciplinary decisions.

7. Sharing and service providers

Content is shared only as the user or institution sets it up through visibility and collaboration settings (private, organisation or public) and group membership, or where required by law. Institution administrators can manage membership and shared content for their organisation.

Galant may use service providers for cloud hosting, GPU compute, email delivery, monitoring, support and backup under confidentiality, security and data-processing terms. A current service-provider list and a security appendix describing data flows, encryption and logging are available to customers under contract.

8. Security

Scholarly requires authentication, enforces access controls, keeps each organisation’s data separate and uses encrypted connections. Any API keys an institution supplies are stored encrypted. Depending on the deployment, further measures may include single sign-on through the institution’s identity provider (OIDC or SAML), audit logging, monitoring and backups. Security is a shared responsibility: institutions must manage users, roles and their own infrastructure appropriately. No system can be guaranteed completely secure.

9. Hosting and international transfers

In a fully hosted deployment Galant runs the application, database and AI for the institution. In a hybrid deployment Galant runs the web application and API while the institution hosts its database, files and, optionally, AI. The hosting arrangement and any cross-border processing are set out in the institution’s order form or deployment documentation and are carried out only as the contract and applicable law permit.

10. Retention, export and deletion

Account and document data are kept while the account or the institution’s licence is active, and for a limited period afterwards as needed for backups, legal obligations or abuse prevention. Users can delete their own documents where the product allows, and administrators can manage members and shared content for their organisation.

When a licence ends, sign-in stops after the end date. The institution can ask for an export of its data within the period stated in its contract (typically 30 days), after which the data is deleted as agreed. Galant does not promise immediate deletion from backups or where law or incident investigation requires controlled retention.

11. Your rights

Students, researchers and other users should normally send access, correction, deletion, consent or grievance requests to their institution, which controls the account. Galant will assist the institution as required by the agreement and applicable law. You can also contact Galant using the details below and we will direct the request appropriately.

12. Incidents

Galant maintains an incident-response process. Institutions should promptly report suspected unauthorised access or disclosure. Galant will notify institutions and authorities as required by the contract and applicable law.

13. Changes to this notice

We may update this notice as Scholarly or the law changes and will post the revised version with an updated date.

14. Contact

Scholarly support: scholarly.support@galantit.com
Privacy email: privacy@galantit.com
General: info@galantit.com

See also the Privacy Policy, Terms of Use and Healthcare Product Privacy Notice.