Where your client data lives.
Confidentiality is not a paragraph in a contract. It is an architecture. Here is ours.
Your obligation to your clients does not transfer to a vendor. So the question is not whether we are trustworthy. It is what we structurally can and cannot touch. This page answers that in plain terms, and you get the full map of your own data before anything runs on a real matter.
It runs in accounts your firm owns
This is the part that matters most and the part most vendors reverse. Your automation does not live inside a Tesray platform that you rent access to. It runs on accounts in your firm’s name, holding your data, that you control and can revoke us from at any time.
- Your AI organization and everything it stores — yours from day one.
- Your billing or practice-management account and its connection — yours.
- Your e-signature account and its templates — yours.
- Your intake forms — yours.
- Any mailbox we create for a project — transfers to you.
There is usually one small connector that has to run somewhere, because forms and payment services announce events by sending a message and something has to be listening. Where that lives is a decision you make, not one we make for you, and it is written down before you sign.
Nothing trains on your clients
The AI platforms we build on are used through their business APIs, which do not train their models on the information you send. Your client matters are not used to improve anyone’s product, including ours.
Each automation touches only what it needs
Access is scoped per job, not granted in bulk. An automation that drafts an engagement letter does not get read access to your whole billing history because it happened to be convenient. Before anything runs on real matters, we walk your firm through the complete data map: what is read, what is written, what is sent, and where it goes.
Credentials never live in documents or in code
API keys, tokens and passwords exist only as environment settings on the running service. They are not in the source code, not in any handover document, and not in email. Project documentation names what has to exist without ever containing the value.
Secret values are handed over once, through a channel you agree to, and rotated on handover as a matter of routine so that no old copy stays valid.
If we stop working together, you keep everything running
No lock-in, and nothing stops working because we are no longer involved.
- The accounts are already in your name, so nothing has to be extracted from us.
- Any hosting we run transfers to your account without downtime or reconfiguration.
- The source code goes to a private repository you are given access to.
- Any automation trigger running under our login is reinstalled under yours.
- Admin tokens and mailbox passwords are rotated at handover.
- You get a written record of everything handed over, and when.
It handles process, not legal judgment
Everything we build automates the administrative chain around your work: capturing details, preparing routine documents from your own templates, tracking what has been signed and paid, and telling the right person when something is ready.
It does not exercise legal judgment, and it is built so it cannot. Anything calling for judgment is routed to your team, and any document it prepares waits for a person to approve before it goes anywhere. Your attorneys stay responsible for the work, which is the only arrangement that is compatible with your obligations.
Conflicts stay a human decision
The system captures and flags what it sees. A person clears every conflict check before an engagement letter is prepared, and nothing goes out until your firm says so.
Common questions
Where does our client data actually live?
In accounts held in your firm's name that you control. Your AI organization, your billing or practice-management account, your e-signature account and your intake forms are yours from the start. We are given access to build, and you can revoke it at any time.
Is our client information used to train AI models?
No. The AI platforms we build on are used through their business APIs, which do not train their models on the information you send. Your client matters are not used to improve anyone's product, including ours.
Who at Tesray can see our matters?
Access is scoped to the job and granted by you on accounts you own. Before anything runs on real matters we walk your firm through the full data map: what is read, what is written, what is sent, and where it goes.
How are our passwords and API keys handled?
They exist only as environment settings on the running service, never in source code, handover documents, or email. Values are handed over once through a channel you agree to, and rotated at handover so no old copy stays valid.
What happens to the system if we stop working with you?
It keeps running and you keep the keys. Accounts are already in your name, any hosting transfers to your account without downtime, the source code goes to a private repository you can access, and everything handed over is recorded in writing.
Can the system give legal advice or decide a conflict?
No, and it is built so it cannot. It automates the administrative chain around your work. Anything calling for legal judgment routes to your team, a person clears every conflict check, and any document it prepares waits for a human to approve before it goes anywhere.