Values are calculated in the browser and are not placed in the page URL.
Privacy & data handling
Know what the public tools do—and what local processing does not prove.
This notice was last reviewed on July 24, 2026. It describes the current public site and must be revised before DenQAI adds accounts, cloud uploads, server-saved projects, case intake, analytics that receive calculator values, or adviser collaboration.
Current public tools
Inputs stay in the active browser tab unless you create a local file.
No public DenQAI workbench requires an account. The tools do not intentionally send entered form values to a DenQAI database, and DenQAI does not restore a scenario after the page is refreshed or closed.
Supported CSV and project-file imports are read on the user’s device. Selecting a file does not upload it to DenQAI.
Supported workbenches—including Practice Flow—can create local project, CSV, print, or PDF outputs. DenQAI does not retain a server copy.
A local export is not a cloud project or backup. The user controls its storage, sharing, retention, and deletion.
Tools that accept local project files reject unknown or malformed fields, neutralize common spreadsheet-formula prefixes in CSV text, and screen some narrative fields for obvious restricted patterns. These are narrow safeguards. They cannot prove that a file is de-identified, authorized, accurate, complete, or safe to share.
Use coded scenario, payer, and vendor labels; aggregate counts, hours, amounts, and relative periods; and short descriptions of supporting documents. The payer-continuity tool is not designed for claims, EOBs, fee schedules, portal data, patient communications, or credentials. Practice Flow is not designed for patient schedules, charts, images, employee files, credentials, or state-scope records.
The owner case-series builder and Independent Scale interest brief create local planning drafts only. They do not submit, enroll, consent, recruit, create membership, or request service. The Local Project and Policy Evidence files likewise do not create accounts, shared workspaces, or controlled repositories.
“Local” describes where the public tool performs its calculation; it is not a security certification, de-identification method, or permission to use the data. A local file can still contain sensitive information. The browser, device, network, extensions, backup service, external links, and any later tool may apply different logging, retention, access, and privacy rules.
Do not enter
Public tools are not an approved repository for restricted information.
No names, dates of birth, record numbers, images, clinical notes, or other identifiable health information.
No passwords, API keys, bank credentials, access tokens, or security answers.
No tax returns, payroll files, contracts, employee records, or other restricted material unless an authorized environment and process have been established.
Future changes
Cloud persistence, collaboration, or case intake would require a new notice and operating controls.
Today’s local files are not accounts, backups, permission systems, document rooms, marketplaces, credentialing or contracting services, work queues, employee-performance systems, consent records, or research submissions. Before adding any of those capabilities, DenQAI would need explicit legal and research boundaries plus identity, authorization, professional ownership, retention, deletion, access, audit, encryption, incident-response, vendor, and support controls.
The workspace demand-validation page describes the observable need tests and safety checks that must precede persistence. For AI-assisted work, use the data gate and an organization-approved environment described in the field guide.