What we do with your client’s file.
You are about to put privileged material into a piece of software. Here is what happens to it, and the documents that bind us to that answer.
Data policies.
The three questions, answered in full.
Where does my case file actually go?
Your documents are stored on Google Cloud infrastructure, encrypted in transit and at rest. When you ask Lexa something, the relevant text is sent to a model provider to answer it. Every provider we send work to is named, with what it receives and under which terms, in the subprocessor list, which we keep current rather than general.
Is any of it used to train a model?
No. We do not use your data to train models, and the providers that process work on our behalf operate under no-training terms. Sensitive content is masked in our telemetry by default, so a debugging log is not a second copy of your record. The binding version of all of this is the privacy policy.
Can I get it back, or get rid of it?
Yes, both. You can export or delete your files on request: write to [email protected] and we will handle it. Deleting a case removes its documents and the work product built from them.
We hold no security certifications, and we are not going to put a row of badges here instead of saying so.
What is above is what is true today, and the privacy policy and subprocessor list are the versions of it we are bound by. If your firm needs something we have not addressed - a retention term, a specific processor, a question about a matter under a protective order - write to [email protected] and you will get a straight answer rather than a brochure.