Trust & Security

Taxerity.AI trust posture. Five pillars — the commitments your firm actually answers to.

Each pillar documents a product control or an explicit limitation. The page does not establish tax or legal compliance, security certification, retention sufficiency, residency, or clearance for real taxpayer data. Taxerity.AI does not auto-file; the practitioner remains responsible for the return.

  • Each pillar identifies an implementation or review topic; it is not a tax, legal, or security conclusion.
  • Use the documented controls as review inputs, not as substitute engagement terms or professional advice.
  • Consent, processing, retention, and audit-export choices remain subject to firm policy and qualified review.

Pillar 01 · Treasury Circular 230 §10.35

Professional responsibility stays with the practitioner

The tool sits inside those rails. The firm's signer stays on the line, signed under the firm's PTIN.

Taxerity.AI presents research for practitioner review. It does not sign a return, provide professional approval, or replace the practitioner's judgment; the firm verifies the facts, authority, and filing treatment.

Decision records can show whether a suggestion was accepted, modified, or rejected. Their sufficiency for an exam, malpractice review, or professional rule remains a matter for qualified advisers.

Circular 230 and other professional obligations remain with the practitioner. This page is a product description, not tax or legal advice.

See the moment-of-decision objection on →

Pillar 02 · IRC §7216

Consent controls on supported intake paths

Some intake paths record a consent step before a return is read. This is not a legal-compliance conclusion.

Supported intake paths can record a disclosure or consent step before a return is read. The exact notice, consent, downstream-use, and retention obligations depend on the engagement and should be set by qualified tax and legal advisers.

The application can retain a reference to the workflow decision. That record does not prove that a firm satisfies IRC §7216 or any other obligation.

Taxerity.AI does not auto-file or transmit to a tax authority; the practitioner remains responsible for the return.

What this pillar commits to, in practice
  • Template-friendly disclosure. Drop-in §7216 disclosure + separate written consent wording for your engagement letter.
  • Engagement-scoped logging. A disclosure row and a consent row against the engagement before the pull starts.
  • Recoverable on request. The consent reference is captured in the audit log so it survives an exam cycle.
See the consent-language objection on →

Pillar 03 · Security controls for review

Access and data-handling controls, with review still open

The application documents access checks and data-handling controls; this page does not claim a certification, complete safeguards, or enabled MFA for every account.

The implementation includes access checks, session controls, and encryption-related code paths. A qualified security reviewer must determine whether those controls satisfy any applicable guidance or customer requirement.

MFA is not enabled for every account by this application, and the platform is not represented here as independently certified. Do not infer a complete safeguard posture from an implementation detail.

Key rotation and audit records are implementation details documented in the repository; they are not a security certification or a clearance for real taxpayer data.

What this pillar commits to, in practice
  • Field-level AES-256-GCM. Active key version-tracked envelope on every tax id, communication body, and reviewer note.
  • Firm-scoped access log. Every read / write / delete of a sensitive record persists, PII-redacted, recoverable as evidence.
  • Session and MFA configuration. Session expiry and MFA availability depend on the deployed configuration and require review.
See the safeguards objection on →

Pillar 04 · Hosting and residency posture

Hosting and access posture is configuration-dependent

Hosting, residency, and isolation statements require review of the deployed configuration and applicable terms.

The repository contains firm-scoped access checks and encryption-related paths. Exact residency, hosting, cross-firm, and processing claims depend on deployment configuration and terms; review them with qualified privacy and security advisers.

A trial or configured connector should not be treated as automatically cleared for real taxpayer data. Verify the applicable authorization, consent, retention, and processing requirements before use.

The application is not represented as independently attested or certified by this page.

What this pillar commits to, in practice
  • Encrypted in transit. TLS 1.3 between your browser, the platform, and your tax software integration.
  • Disk-level encryption inherited. The application includes selected field-handling controls; hosting, encryption, and residency commitments depend on deployment terms and review.
  • No cross-firm reading. Queries are scoped strictly to the caller's firm, members, and staff-permissions row.
See the data-residency objection on →

Pillar 05 · IRS-audit defensibility

Decision records for practitioner review

Some records include catalog citation context and a review decision; sufficiency for an exam or board inquiry requires professional judgment.

A cataloged suggestion may include the citation stored with its entry, a confidence score, and a decision record. Verify the source, facts, tax year, and filing treatment before relying on it.

The application records workflow decisions and can export certain records. Retention periods and the sufficiency of those records for an IRS, state-board, or malpractice review require owner and professional review.

The model is not authoritative and the practitioner remains responsible for the final filing decision.

What this pillar commits to, in practice
  • Decision log + access log. Append-only decision rows (accept / modify / reject) AND access rows (read / write / delete of sensitive records).
  • Retention policy requires review. The application records selected decisions and access events; retention periods and legal sufficiency are policy questions, not product guarantees.
  • PDF exportable on request. Share with a malpractice carrier, an IRS examiner, or a state board — without exposing client identifiers.
See the audit-defensibility objection on →

Read next: a related engagement

IRS Notice Response →
IRS notice response for solo CPAs and EAs responding under their firm's PTIN.
Tax Planning →
Year-end tax planning for solo CPAs and EAs running a Q4 engagement under their firm's PTIN.
Book a Walkthrough →
A 15-minute walkthrough of the notice-response workflow on a real engagement — no deck, no commitment.
Pricing →
Professional at $149/month for solo practices, Firm across the whole engagement team. 14-day free trial runs the full base platform end-to-end first.

The hard limits the five pillars can't carry

Three things this page has committed to on its own.

Beyond the five pillars above, three explicit hard limits sit on /trust because the pillars describe the surface, and these describe the boundary:

  • Never auto-files.Nothing is transmitted to the IRS on your behalf; e-file is your firm's job, under your firm's EFIN.
  • Training and retention depend on the configured service terms. Review provider terms and the deployed configuration before submitting taxpayer information; this page is not a universal no-training guarantee.
  • Firm-scoped access checks are implemented. Reviewed query paths scope access to the authenticated user or firm; verify coverage for the specific deployment and workflow.

How this page is built

One const feeds both the page and the structured data.

  • · Source-of-truth: src/lib/business/trust.ts — a single typed TRUST_PILLARS const feeds the rendered page and the JSON-LD WebPage mainEntity.
  • · Five review areas: practitioner responsibility, consent controls, access and data handling, hosting configuration, and decision records. Each area names its limits and the review still required.
  • · Lock-step with /faq: pillar copy reuses wording verbatim from src/lib/business/faq.ts so /trust and /faq commitments cannot drift.
  • · Anonymous-readable: no auth gate. The page exists to address posture during outreach, before sign-up — gating it would defeat the funnel.
  • · JSON-LD: three hidden <script type="application/ld+json"> blocks — organizationGraph + softwareApplicationGraph + WebPage (one TrustPosture envelope whose mainEntity is the five pillars). React renders JSON as a text child of <script> so there is no XSS surface and no need for dangerouslySetInnerHTML.
  • · Per-pillar anchors: every TrustPillar.id renders as <article id={pillar.id}> so /trust#<pillar-id> deep-links survive — and the same id is reused on /faq so the cross-page deep link path is symmetric.
  • · Free trial scope: trial behavior follows the configured application paths. Verify the deployed controls before using taxpayer data during a trial.
Questions about our posture? Email the team.

See it on a real engagement →

Start with a 14-day Free trial of the full base platform, then decide on Professional at $149 per month — the same five pillars, the same hard limits, the same audit log recoverable on request. Cancel anytime from your billing page. See Starter or Firm pricing on /pricing.

See pricing →