University AI Policy Tracker
APIGitHub
Language
ENZHFRPL

Change log

Indian Institute of Science

Source-backed change history with no release-to-release policy diff rows recorded yet; current claims, official sources, review state, and freshness remain visible across 0 public release records.

Review: Agent reviewedLast checkedMay 15, 2026Last changedMay 15, 2026Claims3Sources2Release records0
University pagePublic JSONMonthly reportUniversity index

Change summary

Current public record freshness and review state.

Indian Institute of Science currently has 3 source-backed claim records and 2 official source attributions. Latest tracked changed date: May 15, 2026. No tracker diff rows are recorded in the latest public release.

This page combines all public release diffs for Indian Institute of Science. Individual release snapshots remain available from their release-specific URLs.

No release-to-release policy diff rows are recorded for this university yet. The page still tracks current source-backed claims, official source attributions, review state, source freshness, and public JSON for discovery and citation.

This tracker is not legal advice, not academic integrity advice, and not an official university statement unless a linked source is the university's own official page.

Newly extracted claims are tracker additions and are not necessarily newly published by the university. Source snapshot changes show hash changes for the same source URL and are not by themselves policy changes.

Diff categories

Semantic classification for this release diff.

Policy text0Newly extracted0Evidence0Source snapshots0Source text0Source added0Source removed0

Combined release diff

Unified tracker diff generated from all public release snapshots for this university.

Indian Institute of Science combined release diff

Initial tracked release. Lines represent public claim/evidence records entering the release snapshot.

+6-0
11 # Indian Institute of Science AI policy record
2+privacy: IISc faculty-facing AI guidance says entering data into an open AI tool should be treated like posting it publicly unless there are strong reasons to trust the tool, and says not to input sensitive, confidential, or restricted information into open AI tools.
3+Evidence (en, 704962d44534): Hence, entering data into an AI tool should be regarded as equivalent to posting it in public (unless there are strong reasons to trust that a specific tool will not use your queries). Do not enter, contribute, or otherwise input sensitive, confidential, or restricted information into open AI tools.
4+research: The IISc committee report recommends full, precise, and transparent disclosure of generative AI use in research publications, theses, and other Institute documents, with details depending on how the tools were used.
5+Evidence (en, 711c21895ddd): Use of generative AI should be fully disclosed, with attribution that is precise, transparent, and with adequate details. In particular, when one is using generative AI in publications, one should follow the guidelines of the Journal, Conference, or Publisher. For thesis and other Institute documents, one should follow the guidelines for publications given below.
6+teaching: An IISc committee report recommends 'allowed with attribution' as the default institutional policy for AI tool use in courses, while allowing instructors, departments, divisions, or programmes to tailor the baseline policy.
7+Evidence (en, 711c21895ddd): We recommend allowed with attribution as the default institutional policy. This default policy should be articulated via an appropriate channel, such as the Student Handbook. Furthermore, this default policy can be tailored at each level in the hierarchy: individual course instructor, department, division, or programme.

Release history

0 public release diffs

Claim changes

3 claim records

privacy

IISc faculty-facing AI guidance says entering data into an open AI tool should be treated like posting it publicly unless there are strong reasons to trust the tool, and says not to input sensitive, confidential, or restricted information into open AI tools.

Review: Agent reviewedConfidence94%Evidence1Languagesen

research

The IISc committee report recommends full, precise, and transparent disclosure of generative AI use in research publications, theses, and other Institute documents, with details depending on how the tools were used.

Review: Agent reviewedConfidence93%Evidence1Languagesen

teaching

An IISc committee report recommends 'allowed with attribution' as the default institutional policy for AI tool use in courses, while allowing instructors, departments, divisions, or programmes to tailor the baseline policy.

Review: Agent reviewedConfidence91%Evidence1Languagesen

Source snapshots

2 source attributions