Security
Tools that train on company data, store it, or ignore access permissions do not clear a security review. Referent is designed around the opposite defaults: your data stays in its system of record, the model providers retain nothing, and every answer respects the permissions you already enforce.
Architecture
These are structural, not policy promises layered on afterwards.
Your deployment runs in its own environment with its own storage and its own credentials. There is no shared index and no shared vector store. Another customer's workload cannot reach yours because it does not run in the same place.
Referent runs against providers under zero-retention agreements. Prompts, responses and metadata are not stored after the request completes and are never used to train a model. A question serves the moment it was asked and then it is gone.
Access is inherited from the systems themselves rather than reimplemented in a second place. If someone could not open a record yesterday, they cannot get an answer built from it today. Nothing widens as a side effect of the deployment.
Answers are fetched from the live system at the moment the question is asked. Referent does not build a parallel copy of your database, so there is no second store to secure, to keep in sync, or to delete later.
Governance
You decide which systems Referent can reach and what it may do in each one. Read-only is a valid configuration and a common starting point.
Queries and actions are logged, so the question of what was asked and what was retrieved has a factual answer rather than an estimate.
Each answer points back to the record it came from. Verification does not depend on trusting the assistant.
European data protection requirements are part of the deployment design, including data residency discussions before anything is connected.
Where the deployment runs is a decision made with you, not a default you inherit.
Because there is no migration and no duplicated store, removing Referent does not leave a copy of your data behind.
On certifications
We publish the properties we can substantiate. If your review needs specific certification evidence, ask us directly and we will tell you exactly where we stand rather than putting a badge on a page.