Corelixio is built so that people only get answers from documents they are allowed to see. Here is how it works, and what is in place during the beta.
When Corelixio takes in a document, it records who is allowed to see it, using the access rules of the system it came from.
Searches and questions in Corelixio Hub pass through the Corelixio Core together with the access level of the person asking.
Only documents the user is allowed to open are used to build the answer. Everything else is left out.
Protecting information is not only about the platform. Corelixio's governance and records modules do the work for you.
Detect personal and sensitive information inside documents, wherever it appears.
Produce redacted copies so documents can be shared without exposing what they should not.
Check documents against your policies and compliance rules and flag what needs attention.
Apply retention rules so documents are kept for as long as required.
Declare records and dispose of them on schedule, with approval.
Keep an audit trail of what happened to each document and who did it.
Each customer's administrator manages users and roles in the Corelixio admin area. The Corelixio Core is the single authority for permissions.
Each customer has its own tenant. Customers that need more separation can run on a dedicated cloud deployment or on premises.
The beta environment is being set up to encrypt data in transit and at rest, back up data daily and keep an audit trail of document access.
We tell you where your data will be hosted, and agree on it with you, before any document is uploaded.
Corelixio is in beta and does not yet hold formal certifications. We are building toward SOC 2 and will publish our progress here. Ask us for our security overview, written for IT and security teams.