ai_tool_treatment
The University of Chicago maintains a page listing approved, restricted, and unauthorized AI tools, with use conditions and review information for the university community.
Open, evidence-backed AI policy records for public reuse.
Change log
Source-check timeline, source snapshot hashes, claim review state, and a diff-style preview of current source-backed claim evidence.
Current public record freshness and review state.
University of Chicago currently has 14 source-backed claim records and 4 official source attributions. Latest tracked changed date: May 6, 2026.
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.
Diff-style preview built from current public claim/evidence records. Full old/new source diffs require paired historical snapshots.
Inserted lines represent current public claim and evidence records in the source-backed dataset.
14 claim records
The University of Chicago maintains a page listing approved, restricted, and unauthorized AI tools, with use conditions and review information for the university community.
At the University of Chicago, if a proposed AI tool use exceeds standard risk tolerance but is not prohibited by compliance regulations, a Risk Acceptance Letter may be prepared to document reviewed and accepted risks under specific conditions.
At the University of Chicago, use of confidential data with publicly available generative AI tools is prohibited without prior security and privacy review. This includes personally identifiable employee data, FERPA-covered student data, HIPAA-covered patient data, and research that is not yet publicly available.
At the University of Chicago, generative AI systems, applications, and software products that process, analyze, or move confidential data require a security review before they are acquired, even if the software is free.
At the University of Chicago, use of University data by vendors to train or improve their AI models is not permitted.
At the University of Chicago, confidential, sensitive, or restricted data should not be used with generative AI tools unless the tool and the use have been reviewed and approved through the appropriate University process.
At the University of Chicago, even when an AI tool is listed as approved, it is not risk-free. Approval means the tool can be used under specific conditions, but users are still responsible for evaluating the sensitivity of their data and ensuring confidential, regulated, or contract-restricted information is not shared unless explicitly allowed.
At the University of Chicago, PhoenixAI is the university's internal generative AI platform, approved for general use and can be used for sensitive information with IRB approval.
At the University of Chicago, ChatGPT 3.5 and ChatGPT 4.0 are approved only for data that is made publicly available by its source, with restrictions limiting use to non-sensitive information.
At the University of Chicago, AI-generated content may be misleading or inaccurate, and it is the responsibility of the tool user to review the accuracy and ownership of any AI-generated content.
The University of Chicago provides a central hub at genai.uchicago.edu for information on generative AI tools, training, resources, and guidance for the university community.
At the University of Chicago, AI transcription or assistant tools may not be used to secretly record or join meetings, per the Business Conduct Policy.
At the University of Chicago, AI tools may not be used to generate harassing, discriminatory, or otherwise unlawful content, including the use of AI to create or alter images, audio, and videos, per the Policy on Harassment, Discrimination, and Sexual Misconduct.
At the University of Chicago, entering sensitive data into AI tools without review and approval by security, privacy, and the appropriate data steward may create an unauthorized data disclosure that may violate University policy, federal and state law, sponsor or contract obligations, and data use agreements.
4 source attributions
official_guidance checked May 5, 2026
official_guidance checked May 5, 2026
official_guidance checked May 5, 2026
official_policy_page checked May 5, 2026