{"id":159514,"date":"2026-08-05T02:06:00","date_gmt":"2026-08-05T10:06:00","guid":{"rendered":"https:\/\/xira.com\/p\/2026\/08\/05\/ai-for-your-documents-without-the-confidentiality-problem-what-on-device-actually-means\/"},"modified":"2026-08-05T02:06:00","modified_gmt":"2026-08-05T10:06:00","slug":"ai-for-your-documents-without-the-confidentiality-problem-what-on-device-actually-means","status":"publish","type":"post","link":"https:\/\/xira.com\/p\/2026\/08\/05\/ai-for-your-documents-without-the-confidentiality-problem-what-on-device-actually-means\/","title":{"rendered":"AI for Your Documents Without the Confidentiality Problem: What \u2018On-Device\u2019 Actually Means"},"content":{"rendered":"

Every piece of software on your devices is growing an \u201cAI\u201d button. Some send client materials to a server; some never leave your machine \u2014 and the buttons look identical. Here’s how to tell the difference, and why it matters.
\nThe post AI for Your Documents Without the Confidentiality Problem: What \u2018On-Device\u2019 Actually Means appeared first on Articles, Tips and Tech for Law Firms and Lawyers.<\/p>\n

The first wave of on-device AI tools is arriving in app stores now. The question \u2014 after why, exactly, on-device AI for lawyers is a big deal \u2014 is how to recognize the real thing. Here\u2019s developer Josh Langberg\u2019s five-question, on-device AI checklist.<\/em><\/strong><\/p>\n

\"mobile
<\/figcaption><\/figure>\n

You already know not to paste a client\u2019s documents into ChatGPT<\/a>. That advice is everywhere, and it\u2019s correct as far as it goes. The problem is that it stops there, while every piece of software on your machine grows an \u201cAI\u201d button. Your PDF reader wants to summarize. Your notes app wants to draft. Your practice management suite has a copilot. Some of these send client material to a server on every keystroke; some never let a byte leave your machine. From the outside, the buttons look identical.<\/p>\n

The good news: You don\u2019t need to trust marketing copy to tell them apart. The difference is architectural, and architecture can be checked.<\/p>\n

On-Device AI for Lawyers vs. the Cloud: The Spectrum, in Plain Terms<\/h2>\n

Every AI feature runs a model somewhere. There are only three places it can be:<\/p>\n

    \n
  1. In the vendor\u2019s cloud.<\/strong> Your document is uploaded, processed on someone else\u2019s computer, and the answer comes back. This is how most AI tools work, including the famous ones. Your confidentiality now depends on the vendor\u2019s retention policy, their security, their subpoena posture, and whatever their terms of service say about training, all of which can change after you\u2019ve signed up.<\/li>\n
  2. In a private cloud.<\/strong> Same upload, but to infrastructure the vendor promises is isolated. Sometimes your cloud, usually their cloud. Better on paper, but still a transmission of client material to a third party \u2014 the exact scenario the ABA addressed directly in Formal Opinion 512<\/a> (July 2024), its first ethics guidance on generative AI, which walks through the Model Rule 1.6 duty of confidentiality as applied to these tools. (Note: Rule numbering and comment language vary by state, so check your jurisdiction\u2019s version before relying on this framing.)<\/li>\n
  3. On the device.<\/strong> The model itself, the actual AI, is installed on your Mac or PC and runs there, the way your word processor does. The document is processed where it already sits. There is no upload, which means there is no retention policy to read, because there is nothing retained anywhere to worry about.<\/li>\n<\/ol>\n

    That third category used to be exotic. It isn\u2019t anymore: Current laptops can run capable language models locally, and a first wave of on-device AI tools is arriving in app stores now. The question is how to recognize the real thing.<\/p>\n

    Privacy Policies Change, Architecture Doesn\u2019t<\/h2>\n

    Here\u2019s the shift in thinking that matters: A privacy policy is a promise, and promises have exceptions, updates and breaches. Architecture is a fact. <\/strong>The right question about any AI tool is not \u201cDoes the vendor promise not to keep my data?\u201d It is \u201cCan my data leave this machine at all?\u201d<\/p>\n

    For a meaningful class of software, that question has a verifiable answer \u2014 the operating system itself will tell you.<\/p>\n

    The On-Device AI Checklist: Five Questions You Can Actually Run<\/h2>\n
      \n
    1. Does it require an account?<\/strong> An account means a server relationship. Even if the documents stay local, your usage may not, and a tool that makes you sign in has, at minimum, a channel out. Genuinely on-device tools have no reason to know who you are.<\/li>\n
    2. Does it ask for an API key?<\/strong> An API key (from OpenAI, Anthropic, Google, or anyone else) is a cloud dependency wearing a disguise. If a tool asks you to paste one in, your documents go to whoever issued that key. That\u2019s not necessarily disqualifying \u2014 but it means the \u201clocal app\u201d is a remote control for someone else\u2019s computer.<\/li>\n
    3. Does it work in airplane mode?<\/strong> The simplest real-world test, and you can run it in thirty seconds: turn off Wi-Fi, then use the AI feature on a scrap document. If it works identically offline, the model is on your machine \u2014 physics doesn\u2019t allow an alternative explanation. If it errors or hangs, your documents need a network connection to be processed. Ask the vendor why.<\/li>\n
    4. On a Mac: Does the app even have network permission?<\/strong> This is the granular one, and it\u2019s worth understanding because it turns confidentiality from policy into physics. Every Mac App Store app runs in Apple\u2019s \u201csandbox\u201d and must declare its capabilities up front, including whether it may open network connections at all. An app that ships without the network entitlement cannot transmit anything, ever; macOS refuses the connection at the operating-system level. The developer couldn\u2019t leak your documents if they wanted to. You can check this yourself in Terminal:<\/li>\n<\/ol>\n
         codesign -d --entitlements - \/Applications\/AppName.app 2>&1 | grep -i network<\/code><\/pre>\n
      No network entitlement in the output means no network, period. (A caveat: This guarantee comes with App Store distribution, where the sandbox is mandatory. Software downloaded directly from a website may not be sandboxed at all \u2014 there, you\u2019re back to trusting the vendor.)<\/p>\n
        \n
      1. What does the App Store privacy label say?<\/strong> Look for \u201cData Not Collected\u201d \u2014 the strictest label Apple offers. It\u2019s a formal declaration the developer is accountable for, not ad copy. Anything else (\u201cData Not Linked to You,\u201d \u201cData Linked to You,\u201d \u201cData Used to Track You\u201d) is telling you something is being gathered; read on before feeding it client files.<\/li>\n<\/ol>\n
        One follow-up worth asking about any sync feature: Whose cloud? Syncing through your own iCloud or OneDrive account keeps documents inside an account you control and a vendor relationship you\u2019ve already evaluated. Syncing through the tool-maker\u2019s servers is a new disclosure decision.<\/p>\n
        What You Give Up, and Why It\u2019s Still Worth It<\/h2>\n
        Honesty requires saying this: an on-device AI model is smaller than a frontier cloud model. It won\u2019t write your brief. What local models do well today is the unglamorous work that happens to involve your most sensitive files: filing and organizing documents by subject, OCR on scanned discovery, searching by meaning rather than exact words, summarizing and answering questions with citations to the page, and flagging personal information \u2014 Social Security numbers, account numbers, addresses \u2014 before a redaction pass. <\/p>\n
        Match the tool to the sensitivity: Public research can go to the cloud model; the client\u2019s documents can get the local one.<\/p>\n
        Related reading: \u201cHow Lawyers Can Ethically Integrate AI Into The<\/a>i<\/a>r Practice<\/a>,\u201d and \u201c5 Essential Questions Every Lawyer Should Ask Before Using AI Tools<\/a>.\u201d<\/em><\/p>\n
        Where This Is Heading<\/h2>\n
        I\u2019ll disclose my interest: I\u2019m a software developer, and I built one of the tools in this new category \u2014 Bibliome, a Mac PDF library manager<\/a> whose language model ships inside the app, with the network entitlement removed. But the checklist above is deliberately not about my app. It works on any tool with an AI button, including the ones that don\u2019t exist yet, because it tests the only thing that doesn\u2019t change with the marketing: where the model runs, and whether your client\u2019s documents can leave the building.<\/p>\n
        Five questions to verify on-device AI for lawyers and legal professionals. Two of them you can run in Terminal and airplane mode before lunch.<\/p>\n
        \n
        Image \u00a9 iStockPhoto.com. <\/p>\n
        \n
        \"\"
        \n<\/a><\/figure>\n
        \n
        Sign up for Attorney at Work\u2019s daily practice tips newsletter here<\/a> and subscribe to our podcast<\/a>, Attorney at Work Today.<\/strong><\/p>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
        Every piece of software on your devices is growing an \u201cAI\u201d button. Some send client materials to a server; some never leave your machine \u2014 and the buttons look identical. Here’s how to tell the difference, and why it matters. The post AI for Your Documents Without the Confidentiality Problem: What \u2018On-Device\u2019 Actually Means appeared […]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[17],"tags":[],"class_list":["post-159514","post","type-post","status-publish","format-standard","hentry","category-legal_matters"],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/159514","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/comments?post=159514"}],"version-history":[{"count":0,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/posts\/159514\/revisions"}],"wp:attachment":[{"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/media?parent=159514"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/categories?post=159514"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/xira.com\/p\/wp-json\/wp\/v2\/tags?post=159514"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}