Mentis8 / Security & control
Mentis8 has no remote backend and no access to your data. Your firm owns the infrastructure where its agents run, remember and learn.
No Mentis8 cloud
There is no Mentis8 remote backend receiving your enterprise knowledge, agent memory or inference. The system runs on your infrastructure.
Your selected communication services, including Slack and email, have their own data paths. Those are distinct from access by Mentis8.
Control inside your firm
Change the illustrative access scope. The result should follow the permission—not the persuasiveness of a prompt.
Retrieve the approved collection within the user’s access boundary.
A separate authorization decision governs consequential actions. Network egress, retention and recovery are also part of qualification.
Establish the user or service initiating the task.
Limit the sources and tools available to that task.
Require approval at the agreed consequence boundary.
Preserve an inspectable account of the action and result.
Identify where inference, retrieval, storage and backups run.
Define allowed outbound traffic, updates and support access.
Scope service access and define rotation and revocation.
Agree what is stored, for how long and how it is removed.
Define restore procedures and test the failure cases.
Agree what records reviewers and operators need to inspect.
Security requirements depend on the deployment and the customer’s obligations. The review should identify implemented controls, remaining work and the evidence required for acceptance. On-premises hardware alone does not establish regulatory compliance or guarantee that no data can leave the network.
Review the architectureNo independent security certification or compliance attestation is claimed on this site.
Continue exploring