{"resourceId":"wheatland-county-ai-privacy-amendments-20261001","versions":[{"version":"external-5963d67abb0024193dd336b633c3d88294d3d1269ad550a80278b7b60082a239","resource":{"id":"wheatland-county-ai-privacy-amendments-20261001","title":"Wheatland County tightens AI policy with human-final decisions and ban on AI scraping/profiling residents","organization":"Wheatland County / the1news (Local Journalism Initiative)","sector":"County AI governance / privacy","geography":"Wheatland County, Alberta, Canada","publishedAt":"October 1, 2026","publicationDate":"2026-10-01","eventDate":"2026-09-22","sourceName":"the1news","sourceLabel":"Independent local reporting","sourceUrl":"https://www.the1news.com/article/wheatland-county-tightens-privacy-rules-for-municipal-use-of-artificial-intellig","evidenceClass":"independent-reporting","outcomeClass":"cautionary","topics":["governance-procurement","data-security","operating-model","accessibility-workforce"],"finding":"On Oct. 1, 2026, the1news reported Wheatland County Council approved Sept. 22 amendments strengthening the county’s existing AI policy. Tools for county business require Information Services review and approval; personal/confidential/sensitive information may only be processed on approved tools/configurations; approval of a platform does not automatically cover plugins, connectors, or integrations. AI cannot be the final basis for decisions that materially affect an individual without review by a qualified county employee, with added scrutiny for uses affecting services, employment, safety, legal, or financial interests. After councillor concern about collection practices, administration added a clause that the county will not use AI to monitor, scrape, compile, profile, score, or infer personal information about identifiable people from social media, websites, or other publicly available sources except where specifically authorized by law and subject to privacy approval. Policy incorporates Alberta Access to Information Act and Protection of Privacy Act requirements.","sledRelevance":"Clear county-level control pattern transferable to U.S. locals drafting staff AI rules: centralized IT approval, human-final for material individual impacts, separate review of integrations, and an explicit anti-OSINT-profiling prohibition—useful contrast to automation-heavy 311/permitting news.","evidence":"On-record quotes from Information Services Manager Harry Kim and Coun. Donna Biggar; describes council debate and amendment text themes. Corroborated by Strathmore Times Sept. 30 mirror of the same LJI story. No deployment outcome metrics.","architectureImplications":"Implies allowlisted AI platforms with per-integration review; configurations for sensitive data; logging/approval workflow before plugins that widen data access; no autonomous decisioning path for material individual outcomes.","governanceImplications":"Shows councils will rewrite AI policies when resident-profiling risks are raised in public debate. U.S. peers should map analogous bans to state privacy, public-records, and law-enforcement exceptions explicitly rather than relying on vague acceptable-use language.","securityPrivacyImplications":"Separates platform approval from connector approval; ties AI processing of sensitive data to approved configurations; forbids broad AI surveillance/OSINT profiling without legal authority plus privacy approval; aligns handling with Alberta ATIA/POPA.","caveats":"Canadian provincial privacy framework differs from U.S. municipal law; article is policy reporting without audit of prior AI use. Predictive policing is not the focus—keep stream boundary on county administration/privacy, not public-safety tooling detail.","streamIds":["local-government"],"roles":{"sales":"County managers and counsel need AI policies that unlock productivity tools without authorizing resident scraping or automated material decisions. Wheatland’s Sept. 22 amendments—reported Oct. 1—add IS approval, human-final review, plugin-level scrutiny, and an explicit ban on AI monitoring/profiling from public sources absent legal and privacy approval. Frame engagements as policy-and-controls enablement for approved copilots, not open-ended OSINT products. Do not claim this evidence supports selling surveillance analytics to county leadership.","engineering":"Fit is allowlisted generative/productivity AI with configuration controls and no autonomous material decisions. Architecture should gate new connectors, isolate sensitive-data tenants, and enforce human approval workflows before impacts on services or finances. Prerequisites: AI inventory, IS review process, and privacy-impact path under local law. Constraints: Alberta statutes here; U.S. ports need state-law mapping. Prove value by showing shadow-AI reduction and zero unapproved connectors in quarterly audits—not by model benchmarks.","delivery":"Delivery work is to update policy text, stand up an Information Services intake for tool and plugin requests, train staff on human-final and sensitive-data rules, and publish the scrape/profile prohibition to every department. Dependencies include Information Services, county attorney/privacy, HR for accountability, and council. Ownership: IS for approvals; privacy/legal for exceptions; departments for compliant daily use. Risks include over-broad bans that drive shadow IT, slow approvals that encourage workarounds, or quiet exceptions that re-enable profiling without another public debate."},"roleDetails":{"sales":{"customerProblem":"Counties want staff AI efficiency while residents and councillors fear scraping, profiling, and automated decisions about individuals.","stakeholders":["CAO/county manager","Information Services manager","County council","Privacy/legal counsel","Department directors"],"discoveryQuestions":["Which AI tools and plugins are already in use without IS approval?","Where could AI outputs affect access to services, employment, or finances?","What legal exceptions exist for investigation or statutory duties?","How are privacy approvals documented for any public-source collection?"],"valueHypothesis":"Tightened AI policy with human-final and anti-profiling clauses can enable approved productivity tools while drawing a bright line against resident OSINT misuse.","potentialEngagement":"Four-week AI policy refresh: inventory, gap analysis vs Wheatland-style controls, draft amendment language, and council briefing.","unsupportedClaims":["That Wheatland measured efficiency gains from the amendment","Fitness of vendor surveillance/OSINT products under this policy","Direct enforceability of Alberta statutes in U.S. cities"]},"engineering":{"fit":"Allowlisted staff AI assistants with human-final decisions; incompatible with automated material individual determinations or bulk public-source profiling.","architectureIntegration":"IS approval registry → approved tenant configurations → optional connector reviews → audit logs; block unapproved plugins.","prerequisites":["AI tool inventory","Sensitive-data classification","Privacy impact assessment process","Staff acceptable-use training"],"constraints":["Provincial/state privacy law differences","Councillor expectations for minimal collection","Integration sprawl from SaaS AI features"],"security":"Approved configurations only for sensitive data; separate review for connectors; prohibit unapproved public-source scraping pipelines.","proofOfValue":["Percent of AI use on approved tools","Zero material decisions without human sign-off in sample audit","Documented privacy approvals for any legal exception","Decline in unapproved plugin incidents"]},"delivery":{"work":"Draft/adopt amendments, implement IS request workflow, train staff, configure technical allowlists, schedule annual policy review.","dependencies":["Council adoption","IS capacity for reviews","Legal/privacy counsel","HR disciplinary alignment"],"ownership":"Information Services owns tool approvals; privacy/legal owns exception interpretations; departments own compliant use.","skillsAdoption":"Staff learn what may not be pasted into AI tools; managers learn human-final sign-off norms.","governanceCheckpoints":["Council policy approval","Quarterly inventory attestation","Privacy review of any exception request","Annual policy refresh"],"acceptanceCriteria":["Written human-final rule in force","Plugin/connector review checklist live","Public-source profiling prohibition published to staff","Exception log exists"],"risks":["Shadow AI if approvals are slow","Vague exceptions undermining the ban","Copy-paste of Alberta clauses without U.S. legal review"]}},"retrievedAt":"2026-10-01T22:18:34-05:00","enrichedAt":"2026-10-01T22:22:00-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Human-final requirements protect individuals from automated denial of services but add staff review load; training must reach all departments using AI copilots, not only IT.","procurementImplications":"Vendor AI features and marketplace plugins need contractual disclosure and separate approval—platform purchase alone is insufficient under this model.","operatingModelImplications":"Centralizes AI enablement in IS with privacy co-control; treats connectors as first-class risk objects alongside primary applications.","sourceVerification":{"openedUrl":"https://www.the1news.com/article/wheatland-county-tightens-privacy-rules-for-municipal-use-of-artificial-intellig","referenceExcerpt":"AI cannot be the final basis for decisions that materially affect an individual without review by a qualified county employee","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}