01
Your cloud, your keys
Deployed into your own account. No operator access to documents, no third-party training, no copies you did not authorize.
Privilege doesn’t travel.
CounselVeil analyses the matter inside your own account. No copy leaves it, no model trains on it, and no output ships without an attorney’s signature.
Approach
A review layer built for privilege — not a chatbot bolted onto discovery.
02
Nothing is retained
Pages are analysed in-region and discarded. No vendor-side copy, no shadow index, no prompt log holding client text.
03
Attorney of record signs
Findings arrive as citations to the source page. Nothing enters a work product until a supervising attorney approves it.
0%
operator access to client documents — including ours
100%
outputs released only on attorney approval
1:1
one isolated cloud account per firm, never shared
Capabilities
Everything a case team does twice, done once.
- I
Contradiction findings
Flags where the record disagrees with itself, with both citations attached — every finding linked to its source page before anyone relies on it.
- II
Case intake and field extraction
Classifies every document in the matter, lists the ones that should be there but are not, and pulls structured facts into a review queue.
- III
Reviewer queue
Paralegals triage, attorneys approve. Every accept, edit, and rejection is logged for the file.
- IV
Theories and first drafts
Liability theories on the matter, editable by the attorney, and first drafts — memo, bill of particulars, interrogatories — in the firm's own template, exported to Word.
- V
Chronology from raw pagesIn development
A dated timeline out of scanned exhibits, emails, and transcripts — including the gaps nobody entered anywhere.
- VI
Deadline and obligation watchIn development
Every date-bound duty in the file, surfaced when no matching action exists in the record.
- VII
Ask the caseIn development
A question in plain language; answers restricted to the matter, with page-level provenance and no cross-client leakage.
Security
Your account. Your keys. No operator access.
A typical AI vendor
- Where the documents live
- On the vendor’s infrastructure, under the vendor’s account.
- Who can read them
- Vendor staff, under an internal policy you cannot inspect.
- What is retained
- Prompt and output logs, kept for a period stated in their policy.
- What trains the model
- Read the exception clause carefully.
- What you can prove afterwards
- A certificate describing the vendor.
CounselVeil
- Where the documents live
- In your cloud account, encrypted with your KMS key.
- Who can read them
- Your firm. No CounselVeil operator has a path to the file.
- What is retained
- Nothing. Pages are analysed in-region and discarded.
- What trains the model
- Nothing of yours — in-region inference, zero retention, no training.
- What you can prove afterwards
- Your own audit log — every access, in a trail they cannot edit.
Privilege is not waived to a third-party processor, because there is no third-party processor holding the file.
Security questions, architecture review, or a copy of the deployment model: security@counselveil.ai
What we are held to
A tool that touches privileged material earns its place by what it refuses to do.
- We will
- Deploy into an account you own, so the file never changes custody.
- We will
- Show the source page behind every finding, before you rely on it.
- We will
- Leave the decision, and the signature, with the attorney of record.
- We will not
- Train anything on your matters, or keep a copy after the analysis returns.
- We will not
- Hold a key, a session, or a support path that lets us read a client document.
- We will not
- Ship a feature we cannot explain to your malpractice carrier.
Bring a real matter.
Thirty minutes with an engineer and an attorney. We will run it in a sandbox in your own region — nothing you send leaves that sandbox, and it is destroyed when the call ends.
- hello@counselveil.ai
- +1 (201) 815-8673
- Wayne, New Jersey · remote-first
Demo request