{"slug":"on-device-llm-private-qualitative-coding-2026","title":"Can On-Device LLMs Do Private Qualitative Coding?","description":"A 2026 CHI study tested ChatQDA, an on-device open-source LLM for qualitative coding. Researchers trusted it to extract, not interpret — and wanted verifiable privacy.","keywords":"on-device LLM qualitative coding, privacy-preserving AI coding, open-source LLM research, ChatQDA, AI qualitative analysis, local LLM interview data, qualitative coding privacy, AI inductive coding","date":"2026-06-01","author":"Qualitati Research Team","category":"Methodology","readTime":"6 min read","content":"<p><strong>Can open-source LLMs running on your own device code qualitative data privately?</strong> A 2026 CHI study testing ChatQDA — an open-source, on-device coding tool — found researchers will use local LLMs for basic extraction, but \"conditional trust\" and a privacy-perception gap mean technical security alone does not convince them their interview data is safe.</p>\n\n<h2>What the study tested</h2>\n<p>The study evaluated whether a privacy-preserving, on-device large language model can support qualitative open coding without sending sensitive transcripts to commercial cloud services. According to Ngo, Nguyen Van, Nguyen, Do, and Nguyen-Quoc (2026), the team built <em>ChatQDA</em>, a framework powered by the open-source <strong>gpt-oss-20b</strong> model (a 20.9-billion-parameter mixture-of-experts model chosen for a compact, on-device hardware footprint), and ran a mixed-methods user study comparing manual open coding against ChatQDA-assisted coding on a five-page semi-structured interview transcript.</p>\n<p>The sample was small and deliberately mixed: four participants, split between two novice qualitative researchers (fewer than two years of experience) and two experienced researchers (two or more years). This is an early-stage, formative study — its value is in the patterns it surfaces, not in generalizable effect sizes.</p>\n\n<h2>Why on-device LLMs matter for qualitative research</h2>\n<p>Most AI coding tools send transcripts to external servers. For interview data that may contain health details, identifiable quotes, or IRB-restricted material, that transfer raises real concerns: data sovereignty, re-identification risk, and institutional-review-board compliance. An on-device model keeps the data on the researcher's own machine — in principle removing the transfer entirely. The study's contribution is testing whether researchers actually <em>believe</em> that, and whether the coding output is good enough to rely on.</p>\n\n<h2>What did researchers think of AI-assisted coding?</h2>\n<p>Participants found the tool easy to learn but were cautious about trusting its interpretations. On a 5-point Likert scale reported by the authors, the system scored well on usability and speed but only moderately on trust and depth of interpretation.</p>\n\n<table border=\"1\" cellpadding=\"6\" cellspacing=\"0\">\n  <thead>\n    <tr><th>Dimension (5-point scale)</th><th>Mean rating</th><th>Read</th></tr>\n  </thead>\n  <tbody>\n    <tr><td>Ease of learning &amp; clarity</td><td>4.0</td><td>Strong — quick to pick up</td></tr>\n    <tr><td>Task completion speed</td><td>3.75 (50% rated 5)</td><td>Fast for extraction</td></tr>\n    <tr><td>Overall usefulness</td><td>3.00</td><td>Moderate</td></tr>\n    <tr><td>Overall trustworthiness</td><td>3.00</td><td>Conditional</td></tr>\n    <tr><td>Reliability</td><td>3.00</td><td>Doubted for interpretation</td></tr>\n    <tr><td>General security measures (perceived)</td><td>2.75</td><td>Weakest score</td></tr>\n  </tbody>\n</table>\n\n<p>According to the authors, participants showed <strong>\"conditional trust\"</strong>: they valued ChatQDA for basic extraction tasks — pulling out candidate codes and segments — but doubted its interpretive accuracy and reliability for the parts of coding that require human judgment.</p>\n\n<h2>The privacy-perception gap: secure but not trusted</h2>\n<p>The most striking finding is what the authors call a privacy-perception gap. Even though the model ran locally — technically keeping data off external servers — perceived security was the lowest-rated dimension (M=2.75 for general security measures, M=3.0 for protection against third-party interception). Participants reported \"epistemic uncertainty regarding data protection\": because the security is invisible, it did not translate into confidence.</p>\n<p>The authors' core recommendation follows directly: privacy-preserving analysis tools must prioritize <em>verifiable</em> privacy and methodological rigor, not just technical infrastructure. Telling researchers \"it runs locally\" is not enough; they need to be able to see and confirm where their data goes.</p>\n\n<h2>What this means for researchers</h2>\n<p>Three practical takeaways:</p>\n<ol>\n  <li><strong>Use AI for extraction, keep interpretation human.</strong> The conditional-trust pattern matches a broader theme in 2026 AI-coding research: LLMs are useful for first-pass code generation and surfacing missed segments, but theme interpretation stays with the researcher. A <a href=\"https://qualitati.com/themelens\">human-in-the-loop thematic analysis workflow</a> reflects exactly this division of labor.</li>\n  <li><strong>Privacy claims need to be auditable.</strong> If a tool handles sensitive transcripts, \"trust us, it's local/encrypted\" will not satisfy careful researchers or IRBs. Look for verifiable data-handling documentation.</li>\n  <li><strong>Treat small studies as signals, not proof.</strong> With n=4, these results are directional. They flag a real design problem — the gap between actual and perceived security — rather than measuring how big it is.</li>\n</ol>\n<p>For teams weighing where AI fits in their coding pipeline, the lesson is to scope it to mechanical, reviewable steps and route interpretation through a transparent <a href=\"https://qualitati.com/qda-workspace\">QDA workspace</a> where every AI-suggested code can be checked against the source.</p>\n\n<h2>FAQ</h2>\n<h3>Can open-source LLMs run qualitative coding offline?</h3>\n<p>Yes. The ChatQDA study used gpt-oss-20b on-device, with no cloud transfer of transcripts, to perform open coding on interview data.</p>\n\n<h3>Are on-device LLMs more private than cloud AI for research data?</h3>\n<p>Technically yes — local models keep data off external servers. But the 2026 study found researchers still felt uncertain about data protection, so verifiable privacy matters as much as the architecture itself.</p>\n\n<h3>Should I trust AI to interpret my qualitative data?</h3>\n<p>Not unsupervised. Participants in the study trusted AI for basic extraction but doubted its interpretive reliability. Keep theme interpretation and final coding decisions with a human researcher.</p>\n\n<h3>How big was the study?</h3>\n<p>Four participants — two novice and two experienced qualitative researchers — coding a five-page transcript. It is a formative user study, so treat findings as design signals rather than generalizable benchmarks.</p>\n\n<h2>The bottom line</h2>\n<p>On-device, open-source LLMs make private qualitative coding technically feasible today. But the 2026 ChatQDA study shows the harder problem is trust: researchers will let AI extract, not interpret, and they need privacy they can verify, not just privacy they are promised.</p>\n\n<p><strong>Primary source:</strong> Ngo, T. T., Nguyen Van, D., Nguyen, A.-M., Do, P.-A., &amp; Nguyen-Quoc, A. (2026). <em>Qualitative Coding Analysis through Open-Source Large Language Models: A User Study and Design Recommendations.</em> Extended Abstracts of the 2026 CHI Conference on Human Factors in Computing Systems. <a href=\"https://arxiv.org/abs/2602.18352\">arxiv.org/abs/2602.18352</a></p>\n\n<p><em>Last updated: June 1, 2026.</em></p>\n<p><em>This is an independent editorial summary of third-party research, written to help researchers understand the study. It is not affiliated with or endorsed by the original authors.</em></p>\n","related":[{"slug":"batching-synthetic-respondents-inflates-correlations-2026","title":"Batching Synthetic Respondents Inflates Correlations (2026)","description":"Generating many synthetic respondents in one LLM request inflates correlations, a 2026 LSE study finds. What it means for synthetic survey data validity.","category":"Methodology","date":"2026-10-13","readTime":"7 min read","author":"Qualitati Research Team"},{"slug":"ai-chatbot-qualitative-interviews-lessons-2026","title":"AI Chatbot Interviews at €0.04: Lessons From a 2026 Study","description":"Can AI chatbot interviews replace qualitative interviewers? A 2026 study of 74 chatbot-led interviews found cheap, engaging data collection but limited depth.","category":"Methodology","date":"2026-10-06","readTime":"7 min read","author":"Qualitati Research Team"},{"slug":"llm-inductive-content-analysis-survey-responses-2026","title":"Can GPT-5 Do Inductive Content Analysis of Survey Text?","description":"Can GPT-5 do inductive content analysis? A 2026 study of 903 survey answers found moderate human-AI agreement (ARI 0.61 codes, 0.54 themes), varying by question.","category":"Methodology","date":"2026-10-05","readTime":"7 min read","author":"Qualitati Research Team"}]}