Trust Center
Security evidence you can verify.
TaxSwarm is built around controlled taxpayer-data handling: deployment-flexible architecture, firm-scoped tenancy, evidence-logged AI use, and CPA review gates. Every claim on this page is backed by code, controls, or executed agreements.
Deployment posture
The strongest security claim is the one your firm controls.
TaxSwarm can run entirely inside your infrastructure. For firms with strict data-residency, fiduciary, or audit requirements, private deployment removes the third-party data path entirely.
Private deployment
TaxSwarm runs entirely inside customer-controlled infrastructure. Taxpayer data and document storage are hosted on the firm's servers, and models run locally. This is the strongest available posture for regulated firms with strict data-residency or fiduciary requirements.
Most defensible for RIAs, broker-dealers, and audit firms.
Cloud (pilot default)
Documents and analyses run on TaxSwarm-hosted infrastructure, with each firm's data scoped to that firm on every request. Inference runs on commercial AI services under executed processing agreements, with no training on customer data.
Standard SaaS pilot path.
Hybrid
Sensitive workloads route to private inference, lower-sensitivity workloads use cloud. A routing layer chooses path per task with full evidence logging.
Available for engagements with mixed sensitivity.
Current posture
Pilot-ready controls with enterprise discipline.
The statements below are evidence-precise. An automated check keeps every TaxSwarm page to compliance, encryption, audit-log, and retention claims the platform can show.
Encryption (in transit + at rest)
Uploaded documents are encrypted at rest with AES-256, with a key derived per firm, and data in transit is encrypted. Encryption is fail-closed: the platform refuses to store a document without a configured key.
SOC 2 posture
TaxSwarm maintains SOC 2-aligned control evidence for diligence. The deletion certificates, audit logs, access events, and consent records produced by the system constitute the underlying evidence.
Auditability
Tamper-evident evidence logs for access, AI use, decisions, exports, and compliance events. Every entry carries a checksum that reveals any alteration.
Model training
Customer tax data is never used to train AI models. Cloud AI calls run under contractual no-training terms, and every AI use event is logged with provider, model, purpose, and consent reference.
Controls
What the platform enforces.
These controls are part of the product and its evidence layer. Each is grounded in code we can show to your security counsel.
Secure document intake
Every uploaded file is validated, scanned for malware, encrypted, and fingerprinted before a document record is created. A receipt is issued for every upload.
Firm isolation
All workspace users are firm-scoped, and each firm's data is scoped to that firm on every request. Internal administration is separated from firm workflows and restricted to TaxSwarm administrators.
Rate limiting
Per-address and per-route rate limits. Guest-upload links carry a hard cap on usage count and an expiry.
AI evidence trail
Every AI-assisted action records provider, model, purpose, input fingerprints, consent reference, taxpayer-data categories, and Circular 230 disclosure context.
Privacy screen
Inputs to AI models are run through a privacy screen that identifies and tags sensitive taxpayer data categories before submission.
Review gates
Client-facing reports are gated by consent, CPA review, attestation, compliance checks, and export evidence. AI cannot finalize professional work without human attestation.
Support access workflow
TaxSwarm support access to customer data requires a documented purpose, scope, approval window, and expiry. Every event in the access window is logged in a tamper-evident chain.
Deletion certificates
Deletion requests run legal-hold and retention checks, then generate destruction certificates with deleted-object counts, retained-exception reasons, and a certificate hash for customer attestation.
Certification bundles
Each engagement can export an auditor-ready evidence bundle containing the analysis payload, strategies, audit trail, agent runs, and compliance certificates, which can be verified outside our platform.
Subprocessors & infrastructure
Disclosed dependencies, by deployment.
The applicable subprocessor list depends on the selected deployment model. Private and hybrid deployments use customer-controlled infrastructure for sensitive workloads.
Requests
DPA, security packet, and diligence review.
Pilot and enterprise customers can request the current security packet, data processing addendum, subprocessor list, and evidence summary under the applicable engagement process.
Contact
Security questions.
Contact [email protected] for diligence materials, security questions, or vulnerability reports. Engagement-specific evidence requests are handled through the assigned engagement lead.
Ready for review
Review security before first production taxpayer data.
We'll walk through deployment options, data handling, support access, AI evidence, and deletion certificates.