Security and control
Your client file
is not training data.
AI TaxBench is designed around local work files, explicit review and visible sources. AI can assist, but the CA accepts the fact.
Local-first work files
Core client and practice data is designed to live in the desktop workspace, not in an unexplained remote account.
Evidence stays visible
Extracted facts, portal artifacts and AI-assisted output keep their source and review state attached.
Review before portal handoff
Filing transitions, evidence acceptance and portal handoff remain explicit CA actions.
Boundaries are part of trust
No hidden OTP capture, CAPTCHA handling, payment action or unattended government-portal login.
Today's boundary
Local-first first. Remote later, only when reviewed.
The current product direction is a local workbench. Firm login, client portals and sync should ship only after authentication, authorization, consent and audit boundaries are reviewed end to end.
Ask a security questionSecurity answers
Boundaries in plain words.
Where does AI TaxBench keep client work files?
AI TaxBench is designed around local-first desktop work files. The website is not promising a hosted client portal or remote account storage.
Does AI TaxBench use client files as AI training data?
No. The product direction is evidence-first and CA-controlled. AI assistance must stay tied to visible sources and CA review.
Does AI TaxBench handle OTP, CAPTCHA or unattended portal login?
No. The stated boundary excludes OTP capture, CAPTCHA handling, payment action and unattended government-portal login.