Home › Claude Security & Privacy Center for Business Owners › Security questions › We want zero data retention for workpaper prep from PDFs and first review of returns. Is that Claude Enterprise with Claude Code, or Claude in our own AWS account, and what does each cost to run?

CPA and tax firms

We want zero data retention for workpaper prep from PDFs and first review of returns. Is that Claude Enterprise with Claude Code, or Claude in our own AWS account, and what does each cost to run?

Short answer

Both routes can work, but neither is “zero retention for the whole office.” Anthropic’s zero data retention covers only its API and Claude Code, including Claude Code on Enterprise, and only after Anthropic approves the organization. Chat and Cowork are not covered. The other route is Claude on Amazon Bedrock inside your own AWS account and region, where you set retention per Region. Enterprise bills seats plus usage at API rates, with a 20-seat minimum. Bedrock bills per token through AWS. Our Claude security guide for CPA firms covers the rest of the plan decision.

We want zero data retention for workpaper prep from PDFs and first review of returns. Is that Claude Enterprise with Claude Code, or Claude in our own AWS account, and what does each cost to run?

What the rules and Anthropic actually publish

Anthropic Privacy Center, zero data retention article: ZDR applies only to “eligible Anthropic APIs,” to products that use your commercial organization API key, and to Claude Code for Enterprise plans. It is “subject to Anthropic’s approval” and applied per organization. Claude chat, Team and Cowork are not on the list.
claude.com/pricing: Enterprise is $20 per seat per month, billed annually, with a 20-seat minimum, and usage is charged on top. Anthropic’s Enterprise billing article says usage is billed “at standard API rates,” self-serve plans prepay usage as shared credits, and seats cannot be removed mid-term on self-serve plans.
Claude Platform docs, Claude in Amazon Bedrock: it “runs on AWS-managed infrastructure with zero operator access (Anthropic personnel have no access to the inference infrastructure),” and data handling is governed by Amazon Bedrock.
AWS Bedrock data retention docs: retention is set per Region. In “none” mode, no request or response data is written to durable storage or shared with the model provider. Some newer Claude models (the docs name Claude Fable 5 and 5.1) require an AWS review mode that keeps prompts and completions inside AWS for up to 30 days, where AWS may review them.
AWS Bedrock pricing: Claude is billed per input and output token. Rates vary by model and Region. Batch runs cost less for select models, and provisioned capacity is billed hourly.
Treas. Reg. 301.7216-3: written taxpayer consent has to come before a preparer discloses return information. Zero retention changes how long data is kept. It does not change whether you disclosed it.

The follow-up questions owners ask

Can staff use Claude Enterprise chat with zero data retention turned on?

No. ZDR does not apply to chat or Cowork. Enterprise chat gets custom retention controls, which shorten how long chats are kept. That is short retention, not zero. On Enterprise, the zero-retention workflow has to run in Claude Code under an approved organization.

How does tax workpaper prep and first review work with Claude zero data retention on Enterprise vs Amazon Bedrock?

In both routes it is a defined workflow, not an open chat window. A staff member points Claude Code at a client folder of PDFs, a saved set of instructions builds the workpaper and a first-review checklist, and the results land in that folder for a CPA to review. Claude Code can run against an approved Enterprise organization, or against Bedrock in your AWS account using Anthropic’s documented Bedrock setup.

What does zero-retention Claude cost a small CPA firm to run?

There is no flat number. Enterprise: at least 20 seats at the published seat price for the year, plus token usage, plus the build. Bedrock: token charges for the model you choose, a small amount of AWS logging and storage, plus the build and someone to maintain the AWS account. No seat fees. Usage depends on pages per return, returns per season and which model you use. The honest way to estimate it is a short pilot on consented returns, with token counts measured and multiplied out.

Does Claude zero data retention satisfy IRC 7216?

No. Treat entering return information into a third-party AI service as a disclosure that generally needs written consent naming the provider, the data and the purpose. On Bedrock, that provider is AWS. Have counsel confirm how your setup is classified.

What this means for your rollout

Pick the route by headcount first. Under 20 people, the Enterprise seat minimum usually decides it, and Bedrock plus Team for everyday non-return work is the common fit.
Limit the zero-retention workflow to the two or three people who do workpaper prep. Everyone else stays on the regular business plan with clear rules on what return data may go in.
On Bedrock, set the Region retention mode to “none” and choose a model that does not require AWS review. Write the setting and the model into your WISP.
On Enterprise, apply for ZDR before you build, and get the approval in writing for your vendor file.
Get 7216 consents signed before the first real return goes through.
Michael’s two cents

For most owner-led tax practices I set these up for, the deciding factor is the 20-seat Enterprise minimum, not the technology. Claude in your own AWS account is the cleaner zero-retention story for a small firm, but somebody has to own that AWS account. If no one inside the firm can do that, budget for it. Run a pilot on a handful of consented returns before you sign anything annual.

Related services and tools

Claude security for CPA and tax firms7216, the WISP and the plan decision on one page.
Secure Claude implementationconfiguration, vendor file and training as one project.
Claude Team vs Enterprisewhat changes between the plans, feature by feature.
Claude data privacy and retentionretention, training and deletion on each plan.

Get the plan before you buy the seats

The plan choice is the easy part. Configuration, governance and training are where firms get it wrong. The Claude Build Plan is two working sessions with Michael Robichaud, then a written plan: architecture, plan choice with the reasons, your firm’s custom Claude plugin scoped, rollout timeline and cost. A fixed , and the plan is yours to keep.

Get the Claude Build Plan or book a 20-minute intro call.

Related questions

Sources

Michael Robichaud

About the author

Michael Robichaud, Founder of Strategized.ai, sets up Claude for small firms that handle client data: CPA and tax firms, law firms, RIAs, insurance agencies and medical practices. Nearly 30 years in enterprise software sales (RSA Security), digital marketing and technical SEO, and two companies built and sold. Every source on this page was checked against Anthropic’s published documentation and the regulator’s own text.

Book a short call about your firm How a secure setup works

Not legal advice. Confirm regulatory items with your counsel. Anthropic pages change; every source above shows the date we checked it.
Strategized.ai is independent and not affiliated with or endorsed by Anthropic. Claude is a trademark of Anthropic, PBC.