Security
What happens to your documents, who can see them, and what your IT team needs to know.
Files are never stored
The Catalog Server reads documents where they are and keeps only their text, in memory. Nothing is written to its disk; remove a folder and its text is gone.
Only text leaves your network
The ProLaw Connector reads documents inside your network and sends just their text, over HTTPS, signed with a key that belongs to your firm alone.
Every client kept apart
Each firm has its own catalog, its own connection to the server and its own index. One firm's question can never reach another firm's documents.
Your sign-in rules apply
Two-factor sign-in for every account, or Sign in with Microsoft so your own MFA and Conditional Access apply and leavers lose access when IT disables them.
Signed, encrypted requests
Requests between your catalog and the server are signed and used once, over HTTPS. Keys and sign-ins are stored encrypted.
Read only
Access to Microsoft 365, Google, Dropbox, Clio and the ProLaw database is read only, and used only for the folders and matters you choose.
How a question is answered
Following one question from Copilot and back.
Copilot asks your catalog
Microsoft's servers send the question to your firm's catalog, signed in as your firm.
Your catalog checks who is asking
It applies your plan and your matter access rules, then sends the Catalog Server only the question and the matters this person may not see.
The Catalog Server finds the passages
It searches the text it holds in memory for your firm alone, and returns the matching passages with their document and page.
Copilot writes the answer
Your catalog passes the passages back, without keeping them, and Copilot answers with the sources named.
For your IT team
Microsoft 365
Sign-in uses an Entra app your administrator approves once. Assigning the app to groups limits who can sign in; group membership drives matter access.
The ProLaw Connector
Installs as a Windows service on Windows Server 2016 or later. It needs read access to the ProLaw database (Windows sign-in, or a read-only SQL login) and the document share, and outbound HTTPS to the Catalog Server. Its key and any database password are stored encrypted.
Endpoint protection
Allow the connector by its path (C:\Program Files\KnowledgeCatalogProLaw) so your endpoint protection doesn't quarantine it, and leave its text cache out of real-time scanning.
Questions
Where do the answers come from?
From your catalog and the folders you connect, and nothing else unless you turn on web answers. Each answer lists its sources, down to the page.
Do our documents get copied to your servers?
No files are stored. The Catalog Server keeps the text of the folders you choose in memory, to search it. For ProLaw on your own servers, only the text is sent; the files stay inside your network.
Which AI writes the answers?
In Copilot, ChatGPT, Claude and other AI apps, the app you are using writes the answer from the passages your catalog returns. On your website and in Slack and Teams, written answers use your own Anthropic or OpenAI key; without one, people get the matching passages.
Can some people be kept away from some matters?
Yes. On Enterprise, matter access rules say which Microsoft 365 groups or people may see each matter or folder. Everyone else never sees it, in any app.
We run ProLaw on our own servers. What does IT need to do?
Install the ProLaw Connector on the ProLaw server and give it read access to the ProLaw database and document folder. It only makes outbound HTTPS calls, so there are no firewall openings or DNS records to add.
Can we try it first?
Ask for a walkthrough on the contact page. We will show a catalog answering real questions, with its sources, before you choose a plan.