Policy presence
University of Maryland, Baltimore County has 3 source-backed public claims for policy presence; deterministic analysis status: unclear.
Open, evidence-backed AI policy records for public reuse.
Baltimore, United States
University of Maryland, Baltimore County has 5 source-backed AI policy claims from 3 official source attributions. Review state: agent reviewed; 5 reviewed claims. Last checked May 20, 2026.
v1 public contract
University of Maryland, Baltimore County has 5 source-backed AI policy claims from 3 official source attributions, including 5 reviewed claims. The record review state is agent reviewed; original-language evidence snippets, source URLs, confidence, and public JSON are preserved for citation. Last checked May 20, 2026. Discovery context: University of Maryland, Baltimore County is listed as QS 2026 rank 801-850.
As of this public record, University AI Policy Tracker lists University of Maryland, Baltimore County as an agent-reviewed AI policy record last checked on May 20, 2026 and last changed on May 20, 2026. The record contains 5 source-backed claims, including 5 reviewed claims, from 3 official source attributions. Original-language evidence snippets and source URLs remain canonical, with public JSON available at https://eduaipolicy.org/api/public/v1/universities/university-of-maryland-baltimore-county.json. The entity-level confidence is 94%. This tracker is not legal advice, not academic integrity advice, and not an official university statement unless the linked source is the university's own official page.
This reference record summarizes visible public data only. Official sources and original-language evidence remain canonical; confidence is separate from review state.
This page 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.
Deterministic source-backed dimensions derived from this record's public claims.
Policy profile rows are machine-candidate derived metadata. They are not final policy conclusions; inspect the linked claim evidence before reuse.
Analysis page-quality metadata is available at /api/public/v1/analysis/page-quality.json.
University of Maryland, Baltimore County has 3 source-backed public claims for policy presence; deterministic analysis status: unclear.
University of Maryland, Baltimore County has 1 source-backed public claim for ai disclosure; deterministic analysis status: required.
University of Maryland, Baltimore County has 3 source-backed public claims for coursework; deterministic analysis status: required.
University of Maryland, Baltimore County has 3 source-backed public claims for exams; deterministic analysis status: required.
University of Maryland, Baltimore County has 2 source-backed public claims for privacy and data entry; deterministic analysis status: restricted.
University of Maryland, Baltimore County has 1 source-backed public claim for academic integrity; deterministic analysis status: allowed.
University of Maryland, Baltimore County has 3 source-backed public claims for approved tools; deterministic analysis status: required.
University of Maryland, Baltimore County has 3 source-backed public claims for named ai services; deterministic analysis status: restricted.
University of Maryland, Baltimore County has 1 source-backed public claim for teaching guidance; deterministic analysis status: recommended.
No source-backed public claim about research AI use is present in this profile.
The current public tracker record does not contain claim evidence about research use, publication ethics, research data, grants, or human-subjects compliance.
No source-backed public claim about AI security review or procurement is present in this profile.
The current public tracker record does not contain claim evidence about security review, procurement, vendor approval, risk assessment, authentication, SSO, or enterprise licensing.
Coverage score measures breadth of public, source-backed coverage only. It is not a policy quality, strictness, legal adequacy, safety, or compliance score.
5 reviewed evidence-backed public claim
Privacy
Normalized value: administrative GenAI use limited to public data unless using UMBC GenAI Tools page tools; proprietary data forbidden in other services
Original evidence
Evidence 1Safeguard data in our use of AI. Please remember, unless you are using a tool from the GenAI Tools web page, you may only use public data with a generative AI service. Using any UMBC proprietary data is forbidden.
Localized display only
For administrative AI, DoIT says users may only use public data with a generative AI service unless using a tool from the GenAI Tools page; use of UMBC proprietary data is forbidden.
Academic Integrity
Normalized value: no institution-licensed AI detection tools at this time; AI detection reliability concerns noted
Original evidence
Evidence 1There are a number of AI detection tools available, some built on older APIs for ChatGPT and therefore they are not accurate just on this factor alone. AI, by its nature, is constantly learning and improving itself and it may never be possible to truly detect whether text is AI-generated. Note: UMBC does not license any AI detection tools at this time.
Localized display only
UMBC notes reliability limitations of AI-detection tools and states that it does not license any AI detection tools at this time.
Privacy
Normalized value: non-public UMBC content requires UMBC-verified safe GenAI service; several tools verified for Level 1 and FERPA data
Original evidence
Evidence 1Unless this information is considered public material, something you would publish on a website for the Internet to see, you should not use content from UMBC on any GenAI service unless you know that UMBC has verified it is safe to use. Luckily, UMBC has access to several GenAI tools that have been verified as safe to use on UMBC Level 1 & FERPA data, which is data intended to be kept internal to UMBC.
Localized display only
Unless UMBC content is public, DoIT says it should not be used with a GenAI service unless UMBC has verified the service is safe; it also says several GenAI tools are verified for Level 1 and FERPA data.
Teaching
Normalized value: teaching guidance recommends clear GenAI expectations and prompt/process documentation where AI is used
Original evidence
Evidence 1Set clear expectations for using generative AI tools including how to cite or reference appropriately, if permitted (Mollick & Mollick, 2023). If students do use AI, they should have prompts readily available to explain how they made use of them and explain their process.
Localized display only
DoIT advises instructors to set clear generative AI expectations, including citation/reference expectations if permitted, and to have students keep prompts available to explain their process.
Ai Tool Treatment
Normalized value: Google Gemini and Microsoft Copilot offered to all campus users; UMBC-account use protects data from future training
Original evidence
Evidence 1UMBC offers three generative AI tools to faculty, staff and students: Google Gemini and Microsoft Copilot to all campus users (faculty, staff, and students) When you sign into any of these UMBC-supported AI tools using your UMBC account, your data is protected and not used for future training.
Localized display only
The Academic and Instructional AI page says Google Gemini and Microsoft Copilot are available to campus users, and UMBC-account use protects data from future training.
0 machine or needs-review claim
Candidate claims are not final policy conclusions. They preserve source URL, source snapshot hash, evidence, confidence, and review state so the record can be audited before review.
3 source attribution
doit.umbc.edu
doit.umbc.edu
doit.umbc.edu
Source-check timeline and diff-style claim/evidence preview.
View the public change record for this university, including source snapshot hashes, claim review states, and a diff-style preview of current source-backed evidence.
Corrections create review tasks and do not directly change this public record.
If an official source is missing, stale, moved, blocked, or incorrectly summarized, submit a source URL, policy change report, or institution correction for review. Corrections must preserve source URLs, source language, original evidence, review state, and audit history.