Privacy Policy
Last updated: September 19, 2026
1. Information we collect
We collect user account information (such as name, email address, role, and organisation) when you register. We process the contracts, playbooks, and templates you upload solely to execute your requested AI analysis.
2. How we use your data
Your uploaded documents are processed on isolated container threads to run automated reviews and generate tracked changes. We enforce a no-training policy for public LLM API calls, and we never use your files to train public AI models.
3. Data retention & deletion
You retain control over your data. You can delete matter files, documents and review logs from the workspace at any time, or purge your organisation's entire account. Deleted content is removed from our live databases straight away.
Deleted content can persist in backup copies until those backups are rotated out. The backup copies we hold away from our main server are encrypted. Our audit log keeps a record that a deletion happened, but not the content that was deleted, because that record is how a deletion is proven.
4. Third-party processing
Which infrastructure and service providers process your data depends on how LexCore is deployed for you. On a sovereign deployment, processing happens entirely inside your own boundary and no document content leaves it. Every provider that applies to your deployment is engaged under a data-processing agreement, and is listed in our published sub-processor register.
5. Google Workspace data we access
If you connect a Google account, LexCore requests only the permissions the features you enable actually need. This is the complete list, what each one is used for, and what happens to the data.
| Permission | What we do with it | What we keep |
|---|---|---|
| See your primary email address | Identifies which Google account is connected, so you can see it in settings and disconnect it. | The address, on the connection record. Nothing else. |
| See and edit events on your calendars | Writes court dates, filing deadlines and matter events you create in LexCore into your calendar, and reads them back so the two stay in step. | Event id, title, time and the matter it belongs to. Not the contents of unrelated events. |
| Manage your tasks | Creates a task when a matter deadline is assigned to you, and marks it done when the deadline is met. | Task id and completion state, linked to the matter. |
| See, edit, create and delete only the files you open with LexCore | Imports a document you pick, and writes an agreed redline back to that same file. It cannot see any other file in your Drive. | The document text, in your workspace, until you delete it. |
| See and download all your Drive files | Only where your organisation switches on Drive browsing, so LexCore can list folders instead of asking you to pick each file. Requested for the listing itself; a document is read only when you choose it. | Folder and file names while browsing. File contents only for documents you select. |
| Read Google Meet conference records | Attaches a meeting recording to the matter it belongs to, for organisations using the governance module. | The meeting id and its link to the matter. |
| Send email on your behalf | Off unless your organisation enables it. Sends a document for signature or a client update from your own address rather than ours. | That the message was sent, and to which matter. We do not read your mailbox, and this permission cannot. |
We never read your Gmail inbox. No permission we request allows it.
How it is stored. Google data is encrypted in transit, held in the workspace of the organisation that connected the account, and reachable only by members of that organisation who have access to the matter it belongs to. The access tokens that let LexCore reach your Google account are encrypted at rest. Access is written to a tamper-evident audit record.
How to stop it. Disconnect the account in LexCore settings, or revoke access directly at myaccount.google.com/permissions. We delete the stored tokens immediately. Documents already imported into a matter remain until you delete them, because they have become part of the firm's file. Delete them the same way you delete any other document.
What we never do. We do not sell Google user data, use it for advertising, use it to train any AI model, or transfer it to anyone except as needed to run the feature you connected or where the law requires it.
6. Google API Services: Limited Use
LexCore's use and transfer of information received from Google APIs to any other app will adhere to Google API Services User Data Policy, including the Limited Use requirements.
In practice that means we do not use Google Workspace data to train any AI model, we do not sell it, we do not transfer it to others except as needed to provide the feature you connected or where the law requires it, and no person reads it except with your explicit permission or for security and legal reasons.
7. LexCore for Word (Microsoft Word add-in)
LexCore for Word is our add-in for Microsoft Word. This section covers what it does with your data. Everything else in this policy applies to it too.
What it sends. The add-in sends the text of the open document, or of your selection, to your organisation's LexCore workspace only when you start an action, such as a review, a redline, a draft or a question. Opening the add-in or signing in sends no document text. Some checks run inside Word on your device and send no document text at all.
What it writes. Changes arrive in your document as tracked changes and comments, so you can accept or reject each one. The add-in does not rewrite your document silently.
Sign-in. You sign in with your LexCore account through our identity service. The add-in never sees your password. Your session token is kept in memory only and is gone when you close the add-in. The add-in stores only display preferences on your device.
Microsoft. The add-in does not read your Microsoft account, mailbox or files, and it does not use Microsoft Graph. Microsoft's own handling of Word is covered by Microsoft's privacy statement, not this one.