Tax preparation generates some of the most sensitive data in any client relationship — SSNs, brokerage account numbers, FBAR-reportable balances, retirement contributions. TraderTax is built to handle it the way a CPA firm IT department would design it themselves.
Every request to TraderTax runs through this stack before it touches a database or a third party. None of it is optional, none of it is a setting a client can turn off, none of it depends on a CPA partner remembering to enable a feature.
Generic SaaS platforms point at SOC 2 and call it done. Tax-specific compliance — IRS Pub 4557, §7216, IRC e-signature rules — is what your state board, your E&O carrier, and a Schedule C audit actually look at. TraderTax is built to those standards.
No single check is the gatekeeper. Every read or write to a sensitive document passes through all six of these in sequence. If any one fails, the operation is denied — silently from the attacker's perspective, observably from our monitoring.
TraderTax is built specifically for traders, which means the threat model has to handle prop firm 1099-NEC structuring, offshore brokerage statements subject to FBAR / FATCA disclosure, §475 mark-to-market elections, and the §1256 60/40 contract split — none of which generic practice-management tools account for. We started with the trader workload and worked the security posture outward, rather than retrofitting controls onto a general-purpose CRM. If your firm's IT department or E&O carrier sends a vendor questionnaire (SIG Lite, CAIQ, or custom), we'll complete it in writing within 5 business days.
Every claim on this page maps to a piece of source code, a deployed config, or a published policy. Verify any of it.
security@tradertax.net. We acknowledge within 2 business days and respond with a remediation timeline within 5. We don't pursue legal action against good-faith researchers.