University AI Policy Tracker
APIGitHub
Language
ENZHFRPL

Change log

University of Kentucky

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 20, 2026Last changedMay 20, 2026Claims4Sources3Release records0
University pagePublic JSONMonthly reportUniversity index

Change summary

Current public record freshness and review state.

University of Kentucky currently has 4 source-backed claim records and 3 official source attributions. Latest tracked changed date: May 20, 2026. No tracker diff rows are recorded in the latest public release.

This page combines all public release diffs for University of Kentucky. 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.

University of Kentucky combined release diff

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

+8-0
11 # University of Kentucky AI policy record
2+privacy: UK ADVANCE research guidance says data privacy review is needed before Protected Data is entered into a generative AI tool; it also says not to put PHI into such tools unless UKHC InfoSec has confirmed HIPAA compliance and PHI support, and not to place other non-public or proprietary research data into open-source AI without UK ITS GRC approval.
3+Evidence (en, 16cd4b625b4d): Data privacy review is needed before any Protected Data (AR 10.7) is entered into a generative AI tool. Unless the UKHC InfoSec Data Sharing Committee has confirmed the AI tool is HIPAA compliant and supports PHI input, do not put research data containing PHI into a generative AI tool or other software.
4+research: UK ADVANCE research guidance says generative AI tools may enhance research when used responsibly, generated content should be verified or validated, generative AI cannot be designated as an author, and researchers remain responsible for content and accuracy.
5+Evidence (en, 16cd4b625b4d): When using a generative AI tool, it is best practice to verify or validate all generated content using additional factors and reliable resources. Generative AI cannot be designated authorship as it cannot be held accountable.
6+teaching: UK ADVANCE provides instructional generative AI guidance that includes creating and clearly communicating course policies, responding to misuse, and designing learning experiences aligned with those policies.
7+Evidence (en, 7c2e4686fb0d): UK ADVANCE provides the following guidance and recommendations: Understanding Capabilities and Risks; Developing Course Policies: Creating and clearly communicating course policies regarding the use of generative AI; Responding to Misuse; Designing Aligned Learning Experiences.
8+ai_tool_treatment: University of Kentucky CELT guidance frames student generative AI use as a course-level instructor decision and recommends communicating allowed uses, tool restrictions, citation or acknowledgement expectations, and alternatives where privacy concerns exist.
9+Evidence (en, 30818b9420bf): It is up to the instructor to decide whether student use of generative AI (GenAI) is appropriate for their courses and to what extent. Instructors might also consider an assignment-by-assignment approach to identifying when generative AI is allowed.

Release history

0 public release diffs

Claim changes

4 claim records

privacy

UK ADVANCE research guidance says data privacy review is needed before Protected Data is entered into a generative AI tool; it also says not to put PHI into such tools unless UKHC InfoSec has confirmed HIPAA compliance and PHI support, and not to place other non-public or proprietary research data into open-source AI without UK ITS GRC approval.

Review: Agent reviewedConfidence93%Evidence1Languagesen

research

UK ADVANCE research guidance says generative AI tools may enhance research when used responsibly, generated content should be verified or validated, generative AI cannot be designated as an author, and researchers remain responsible for content and accuracy.

Review: Agent reviewedConfidence91%Evidence1Languagesen

teaching

UK ADVANCE provides instructional generative AI guidance that includes creating and clearly communicating course policies, responding to misuse, and designing learning experiences aligned with those policies.

Review: Agent reviewedConfidence90%Evidence1Languagesen

ai_tool_treatment

University of Kentucky CELT guidance frames student generative AI use as a course-level instructor decision and recommends communicating allowed uses, tool restrictions, citation or acknowledgement expectations, and alternatives where privacy concerns exist.

Review: Agent reviewedConfidence88%Evidence1Languagesen

Source snapshots

3 source attributions

Faculty Guidelines | ADVANCE Team

official_guidance Tracker checked at May 20, 2026, 1:59 AM

Snapshot hash
7c2e4686fb0d46d355bd91f3af981fd4cf31d8d09a199ef2cb86aed03c59e01b