How we use AI — draft

Drafting note

Not legal advice. Not reviewed by counsel. Draft v0.1 · 2026-09-24 · not yet published. Public page at https://sidesheet.co/legal/ai (/legal/ai). Drafting notes are in blockquotes; strip them before publishing. {{…}} = fill before publishing.

Honesty rules: no zero-data-retention claim, no certification claim. The product is not built yet; "⚠️" marks a statement that must be true in production before publishing.

How Sidesheet uses AI

Last updated: {{EFFECTIVE_DATE}}

This page is not legal advice.

What the AI does

Sidesheet uses AI to read the pages of the tax returns you upload and pull out the line items for your spread. It does not give tax, valuation, or accounting advice (Terms §3.4).

Which model, and where

• Provider: Google Cloud, through Vertex AI, using Google's Gemini models.
• Location: Google's us-central1 region (United States). Our code is pinned to this region and refuses Google's "global" setting, which could route requests outside the US.
• We use Google's paid enterprise service, under the Google Cloud terms, not a free consumer tool.

What we send to the model

The content of the pages of the returns you upload: the text and numbers on them, including any names or taxpayer ID numbers that appear there. We do not remove numbers the spread needs, because that would make the spread wrong. We send nothing else about you or your firm.

No training on your data

• Us: we do not use your data to train or fine-tune any AI model (Terms §2.3).
• Google: Google's terms say: "Google will not use Customer Data to train or fine-tune any AI/ML models without Customer's prior permission or instruction." (Google Cloud Service Specific Terms, §18 "Training Restriction"). We have not given that permission and will not.

What Google keeps, and for how long

We have turned off Google's request and response logging. Separately, Google may keep prompts for a limited time to detect abuse of its service, unless Google grants an exemption. We have applied for that exemption. It has not been granted yet. We will not process real customer data until it is.

Drafting note

Drafting note: this paragraph must be accurate on the publish date. When Google grants the exemption, replace it with: "Google has granted our exemption from abuse-monitoring prompt retention (granted {{DATE}})." Even then, do not write "zero data retention" — describe exactly what is and isn't kept. Do not publish while real customer data is being processed without it.

Drafting note

⚠️ Must be true in production before publishing. (Request/response logging off; no grounding or File API storage in the client; us-central1 pin enforced — already in code and CI.)

You check every number

AI can make mistakes. So:

• Every extracted number links to the page of the return it came from.
• Values the system is unsure about are flagged for your review.
• You, the professional, are responsible for checking the spread before relying on it (Terms §3.4).

Drafting note

⚠️ Must be true in production before publishing. (Source-page link on every value; uncertainty flags.)

Quality improvement is opt-in

Off by default. If you turn on Help improve extraction, named UNTAP LLC staff may review copies of your uploads, with names, addresses and taxpayer ID numbers removed automatically, to check accuracy. It never covers returns your firm prepared, is never used to train AI, and you can turn it off any time (Terms §2.4).

Drafting note

⚠️ Must be true in production before publishing. (Toggle, automatic removal of identifiers, access logging, 30-day deletion of review copies.)

A note for firms on AI disclosure laws

Some states regulate how professionals use AI with clients. For example, Utah's SB 226 (2025) requires a licensed professional to disclose AI use when a person receiving their services interacts with conversational generative AI in a "high-risk" interaction. In our service, only your firm's staff use the software. The business being valued never interacts with our AI, and our AI is not a chat tool. We think that makes such rules unlikely to apply, but your obligations depend on your state and your engagement. Please check your own.

Questions

privacy@sidesheet.co · security@sidesheet.co · See also our Security page and Subprocessors.

Drafting note

Sources (checked 2026-09-24): Google Cloud Service Specific Terms §18 — https://cloud.google.com/terms/service-terms ; Utah SB 226 (2025) enrolled, Utah Code 13-75-101, -103 — https://le.utah.gov/Session/2025/bills/enrolled/SB0226.pdf