Original client documents
Original client documents are stored on infrastructure dedicated to the firm. Merit does not upload the original file to a model provider.
Merit separates the original client document from the text used for a task. This page explains that path and the current access controls.




The signed-in attorney chooses the matter and task.
The product does not upload the original file to a model provider.
Original fileText extraction, OCR, and optional local embeddings run on the assigned machine. Embeddings are off by default and are not persisted.
Local processingThe task may include selected text, document titles, and document-type labels. The file itself is not sent.
Selected text, not the fileThe attorney checks the facts, sources, analysis, dates, and document.
Sending, filing, serving, and submitting remain manual.
Attorney controlledOriginal client documents are stored on infrastructure dedicated to the firm. Merit does not upload the original file to a model provider.
Text extraction and OCR run locally on the assigned machine. Optional embeddings also run locally. Embeddings are not persisted, and the feature is off by default.
A configured cloud model may receive text selected for the task. Today, that text may also include document titles and document-type labels.
The provider receives text, not the original file. A title can contain identifying information, so firms should treat titles as part of the information that may leave the assigned environment.
Access uses the firm’s Microsoft Entra tenant sign-in and a seat second factor. Connections use TLS through a single Cloudflare hostname.
Matter data is stored in per-seat, per-matter scopes. This describes the current storage structure and is not an absolute isolation guarantee.
Consequential external actions remain manual and require attorney review.
Merit returns work for review. The attorney decides whether to send, file, serve, or submit it and completes that action outside the preparation step.