Government
Citizen data does not go on someone else’s server.
Government departments and agencies handle information about people who cannot choose to opt out of the relationship. Case files, income data, medical status, immigration status, criminal history. Staff want AI for the same reason everyone else does — the work is faster with it — and the constraints on where that data can be processed are unusually specific.
Request an assessmentYour obligation
Data residency is not a nice-to-have here
PSPF policies, agency-specific handling rules, DTA guidance on generative AI in the Australian Public Service, and IRAP assessments for anything approaching OFFICIAL:Sensitive or above — none of these tolerate ad-hoc offshore processing of citizen data. Where health information, criminal history or vulnerable-population data is involved, the standard is higher again. And where the classification framework applies, unauthorised disclosure is not merely a policy breach — it can be a criminal one.
Where it’s happening
The four places we see it most
None of these are careless people. They are competent staff doing the work faster, using a tool that is genuinely good at it.
Case file summarisation
Citizen files pasted in to speed up review, transmitting personal, health, financial and behavioural information to an offshore recipient in one request.
Briefing note drafting
Ministerial and executive briefings drafted with real content included, occasionally including material that would be classified if written on the correct template.
Correspondence with constituents
Full context supplied so the reply is on point — including the constituent’s original grievance in identifying detail.
Policy analysis with unpublished data
Draft datasets, models and impact assessments submitted for summarisation before publication, sometimes months before public release.
The alternative
Same capability, nothing leaves
A private system does not ask your team to give anything up. It does the same work on the same documents — it simply does it on a machine you own, sitting in your own office.
See how it works →- Summarise long submissions and case files without leaving the government cloud (or in this case, your building)
- Draft briefings and correspondence with real content, not placeholder text
- Search internal policy libraries and prior decisions in plain English
- Work with pre-publication data without third-party disclosure
- Support offline operation for remote and secured facilities
Government & Public Sector: common questions
- How does this interact with IRAP-assessed cloud services?
- IRAP-assessed cloud is the right answer for many workloads — it is a properly reviewed, defined vendor arrangement. On-premise is complementary rather than competitive: it removes exposure from the ad-hoc, off-tenancy usage that IRAP assessment does not cover. Think of it as closing the gap between the sanctioned tools and what actually gets used at 6pm.
- Are you IRAP assessed?
- No — and we will not claim to be. IRAP is a substantial, specific assessment process, and we would rather be honest about what we are than misrepresent it. What we can be is a system properly sized and secured to sit within your existing architecture, with security controls agreed against your obligations rather than a generic checklist.
No obligation
Is this worth it for a firm like yours?
Tell us roughly how many people, what they handle, and what you suspect is already happening. We will give you a straight answer — including if the answer is that you do not need us.