You Don't Own Your Tax Software. You Rent It. For thirty years, renting the place your clients' data lives was simply how the profession worked. AI and a client's plain question are turning that arrangement into the thing that sorts firms apart.

I want to name something most of us in this profession do every single day without thinking about it. We call it "our software." We say "my system," "our platform," "the cloud we use." And almost none of it is ours.

We rent it. Every bit of it.

When your firm processes a return in a shared-cloud tool, your client's most private information — their name, their address, their Social Security number, the whole shape of their financial life — doesn't live with you. It lives in a building someone else owns. Other firms' data sits on the same floor. The landlord can walk the halls, revise the terms with thirty days' notice, and raise what you pay every year your firm grows. You hold no keys. You signed a lease and called it ownership.

For most of my career I never questioned this, because there was nothing to question. That was just how tax software worked. The architecture was invisible, so the arrangement was invisible. You bought the tool, the data went wherever the tool put it, and the only choice you made was which landlord to rent from.

Two things are ending that quiet.

The question is coming across the desk

The first is that clients have started to ask. Breaches have become common enough that an ordinary taxpayer now knows to wonder aloud where their information goes. I got the question a couple of seasons ago, across a desk, in plain language, from a client who'd just watched me scan her W-2 into something: where does this actually go?

I gave the reassuring answer — it's encrypted, the vendor is certified, it's in the cloud. All true. All beside the point. She didn't ask whether the data was encrypted. She asked where it lives. And the honest answer was that it lives on a server I have never seen, run by a company she's never heard of, under terms that can change next month. I couldn't say that in a way that built trust, so I said the encrypted-cloud thing and we moved on. But I knew I'd dodged it.

The second thing is bigger. AI has entered tax preparation, and AI makes the location question unavoidable. The moment a tool says it uses AI to "read" a return, the next honest question is: read it where? On whose servers, with whose model, and who else can see it? When a document gets processed by AI, it generally has to go somewhere to be processed. So the entire matter of taxpayer privacy in the AI era collapses down to one architectural fact — does the data leave your firm's environment to be processed, or not?

If you're renting, it leaves. That's not a scandal; it's the default. Shared-cloud software was the cheapest, fastest way to build for twenty years, so that's what got built. But the default has a cost that stays invisible right up until a client asks the question, and then you're reaching for a paragraph when what you needed was a sentence.

Renting and owning are different in kind, not degree

Strip away the marketing and there are two arrangements a firm can be in.

When you rent, your protection is a promise. A privacy policy, a terms-of-service, a data-processing agreement — real documents, often carefully written, and every one of them changeable. Your leverage, if the terms shift in a way you don't like, is to stop using the tool. After your clients' data is already inside it.

When you own, your protection is a fact. Your firm's data is processed inside an environment you already control — your own cloud tenant, the same place that already holds your firm's email and documents — and it never leaves. There is no vendor-side copy to govern with a clause, because there is no vendor-side copy. The safety isn't a promise about what someone won't do with the data. It's a property of where the data physically sits.

That difference is not "a more careful landlord." It's the deed instead of the lease. With a promise, you're trusting an entity to keep its word. With ownership, there's no word to keep — the data simply isn't anywhere it could be exposed from.

What owning actually looks like

I'll be concrete, because ownership is specific and slogans are cheap.

It's possible to build tax automation that runs inside the firm's own cloud workspace. The documents get processed there. The results get written back there. The most sensitive field on the whole return — the Social Security number — is held in a dedicated secret store and referenced by a pointer, so a routine export can't spill it. The AI does the mechanical work, every value is checked before it becomes part of a return, and the licensed human keeps the judgment and the signature. And none of it leaves the environment the firm already controls and already trusts.

It even makes the compliance story simpler. §7216 — the rule governing how preparers handle taxpayer information — stops being a policy you maintain and becomes a property of where the data lives. You're not promising to satisfy a disclosure restriction. You're structurally unable to violate it, because the data never went anywhere it could be improperly disclosed from.

That is what it means to get your name on the deed.

The profession is about to sort itself

The next few years are going to divide our profession by the answer to one question, and it won't be "how fast is your software." Every tool will be fast soon; speed is the first thing that gets copied. The question will be "where does my data live" — clients will ask it more, regulators will ask it more, and the firms that thrive will be the ones who can answer in one plain sentence without reaching for a PDF.

So I'll hand you the question the way it was handed to me. If a client asked today where their information sleeps tonight, what would you actually say? And if you don't love the answer, the good news is that it's fixable — not with a better privacy policy, but with a better place to put the data.

You don't have to keep renting. You can own your house.