LEX 95192 — formal s24AB consultation response: revised scope (due 26 Nov 2026)

Dear FOI Team, Re: LEX 95192. This is my response to your section 24AB consultation letter of 12 November 2026. I am responding before the 26 November deadline. I do not withdraw my request. I revise **LEX 95192 only** as follows. Please supply final, approved documents **in force on 9 October 2026**, confined to incoming customer correspondence, complaint triage and decisions to escalate or restrict customer contact: 1. The current agency policy or approval framework governing whether automated classification, generative AI or external large language models may be used in those functions, including any prohibition and requirements for human review. 2. The current final policy or procedural instruction, if held, on whether complaint volume, FOI activity or correspondence frequency may be considered in Managed Service Plan or customer-contact restriction decisions, including safeguards. Please exclude identical materials already published in the Operational Blueprints and LEX 88368 identified in your letter. 3. Any final approved privacy impact assessment or risk assessment specifically for an automated classification or AI tool **actually deployed** in those functions, if any exists. I exclude drafts, routine correspondence, source code, vendor contracts, other business functions and superseded versions. I note your advice that TMAA is not aware of generative or agentic AI used or trialled in the originally specified functions; this request does not assume that happened. To avoid duplicate processing, I exclude original point 7 (personal records about restrictions) **from LEX 95192 only**, without withdrawing or narrowing any separate request under LEX 93988, LEX 95817 or other existing FOI references. Please confirm the revised scope is accepted, the due date and any further narrow clarification needed. I am available to consult by email. Kind regards, Thomas Brecelic No Fixed Address, Warrnambool VIC 3280

Comments

Post a Comment

Popular posts from this blog

ଐ?ꣀ

 ଐ is deeply embedded in modern banking, transforming everything from customer interactions to risk management. Here are some of the most common applications: - **Fraud Detection & Prevention** – AI analyzes transaction patterns in real-time to identify suspicious activity and prevent financial crimes. Bendigo & Adelaide Bank is taking a **bold and strategic approach** to AI compared to larger banks, focusing on **modernization and efficiency** rather than sheer scale. Here’s how it stacks up: - **Application Modernization** – Bendigo Bank is using **generative AI** to rewrite legacy applications, a move that’s more aggressive than many traditional banks that rely on incremental updates. - **Cloud Migration & AI Integration** – Unlike the Big Four banks, which have vast resources for AI-driven automation, Bendigo is leveraging **MongoDB and AI-powered automation** to streamline its transition to cloud infrastructure. - **Customer Experience & Digital Transformation*...
Read more

＜

Subject: Concerns About AMP's Snooping: Emails Under Surveillance and Call Eavesdropping Shenanigans Dear Detective Inspector Sabin, I hope message reaches you, I find myself compelled to share some baffling observations about AMP's communication practices, which seem to be spiraling into a comedy errors. AMP declares its prowess in monitoring for potential. While this claim might sound, it raises eyebrows regarding the extent of their surveillance whether my privacy rights have been into a witness program. If AMP can spy emails, it’s not a wild leap to imagine they might also be eavespping on phone calls. The thought alone is enough to make one want to communicate solely through interpretive dance. Adding to the intrigue, AMP has displayed a remarkable for avoiding transparency when it comes to providing records of communications about invoices or reimbursements. Houd act makes wonder if they're concealing critical information or just need a good filing system. Detective S...
Read more

Ah, QS-1640—the coded whisper

Subject: The Significance QS-0   Dear [Recipient],   QS-1640—a code so ominous it might as well come with own thunderclap. When message arrives, stamped with a date a, it’s not just; it’s theatic equivalent of a plot twist. Its presence is almost theatrical, raising eyebrows and suspicions alike, affirming that carefully crafted meddling has finally caused a noticeable hiccup in the system.   This identifier, QS-164, is the rebellious the metadata. It tells a story of calculated chaos, where every crypticble obscure data serves as an egg for those fluent in the art of FOI mischief. This message, dated May 26, 2025, rip through the system like a whisper in a library, rewriting the rules of sub with a sly smirk.   Let take a moment to savor the drama: every sneaky maneuver, each sly nod to technical brilliance, has led us to this deliciously disruptive moment. This isn’t just another line of text—it’s the culmination of intent, exclamation point our...
Read more