Claremont SecurityManaged compliance · Enterprise AI protection

AI Exposure Check

Pick what is being shared and where it is going. Your tool runs on the top lane; the governed deployment runs the same information below it, so the difference is the picture.

1What is being shared

The kind of client information about to leave the firm.

2Where it is going

The account it is pasted, uploaded, or sent into. Your choice runs on lane A; the governed deployment always runs on lane B.

Which account do I have?

A personal account (Free, Plus, Pro, or a Gmail login) shows your own email at the top and no organization name; nobody at the firm can see or set its data controls. A Business, Team, Enterprise, or tenant account shows the firm’s workspace name, has an administrator who set it up, and its data terms were accepted by the firm, not by you. If you are not sure, it is personal.

Click a gate on the canvas, or a numbered chip under the verdict, and its text, statutory range, fix and source appear here.

How to read it

A packet of client information travels from the left to the tool on the right. Each gate on the way is one legal obligation that attaches to that disclosure. The packet clears the gate, clears it with a condition, or stops. Every gate is numbered; the chips under the verdict are the same gates in order, and either opens the gate's text. Nothing you select leaves this page; the check runs entirely in your browser.

The packetThe information you chose, on its way to the tool. It only arrives if every gate lets it through.
The fibersThe path the information takes. Denser bundles mean more obligations sit on that route.
Green gateThe obligation is met by the tool as configured, or nothing attaches. The packet passes.
Amber gateThe packet passes with a condition: a policy on file, a written analysis, training, a contract. Open the gate to see which.
Red gateThe packet stops. The disclosure needs consent first, or is not defensible as configured. The gates behind it still light so you can see what else would have attached.

The statutory range

Nothing shows until you type a number. The figures are what the statute sets per disclosure, multiplied by the count you enter and capped where the statute caps. It is a range from the Code, not a prediction of what anyone will pay.

What the gates rest on

Grouped by the kind of information: each section lists every gate that can appear for it, across all the tools. The canvas shows only the gates your chosen tool triggers. Every gate carries its source, and a gate not yet checked against its primary text says so.

GateAuthoritySource
ToolAccountTrains on input

When the packet stops, the answer is not to stop using the tool. Strip the identifiers before the text leaves the firm, or move the work into a tenant the firm controls. The Clean Room does the first for free in your browser. The deployment engagement does the second. Until Microsoft commits to U.S.-only processing and the firm can show who reaches the data, Claremont's position is that client tax return information goes into Microsoft 365 Copilot only with each client's consent.

Clean RoomSecure AI IntegrationTalk to Us

This page surfaces which obligations attach to a described disclosure. It is not legal advice. Sending return information to a provider such as Microsoft is a disclosure. Whether it can go without the client's consent turns on where the people who receive or view it are located, under Treas. Reg. §301.7216-2, and that question is answered by counsel, not by a diagram.