What “no external AI” actually means
Many tools quietly send your documents to a model provider for AI features. Rempart does not. Here is exactly what that commitment covers.
“No external AI” is an easy phrase to write and an easy one to empty of meaning. At Rempart it has a precise definition, and it is binding.
The definition
No document, excerpt, page, OCR output, chunk, embedding vector or prompt containing deal data is sent to a model provider. Not to index, not to summarise, not to “improve the service”. The processing that touches content, such as full-text search or PDF reading, runs inside the instance's infrastructure.
Why it is a commitment, not a setting
A “do not share my data” setting can be toggled on and off, and it depends on a third party to be honoured. Here, the architecture has no path out to an external AI. If an AI feature were offered one day, it would have to run inside isolated internal infrastructure, with a contractual guarantee for the client, never through a silent call to an outside service.
What it changes for a deal
In a sale or a raise, the most sensitive files go through the data room. Knowing that they will not, without your knowledge, train or feed a third-party model is a baseline condition, not a premium option. The rest of the security posture is described on the security & connectivity page.