Commitment
What we commit to —
and what we don't claim.
Sovereign by construction. Checked by an independent model. Specific about scope.
Security pages are easy to write and hard to stand behind. This one is written to be read next to our architecture, and to be defensible line by line in a vendor review.
The Citorum Commitment
Citorum is built for organizations that operate under constraints — Sarbanes-Oxley (SOX), the Health Insurance Portability and Accountability Act (HIPAA), the General Data Protection Regulation (GDPR), state privacy statutes, professional privilege. Those constraints are the design input, not something accommodated later. Four commitments follow from that, and they hold in every deployment topology we offer.
- Your corpus and your inference stay in your environment. As deployed, Citorum makes no outbound AI calls. Retrieval, embedding, document conversion, inference, answer-checking and transcription all run on hardware you control.
- Access is enforced where it cannot be bypassed. Tenant, Lens, corpus, tag, group and document scope are applied inside the retrieval query itself, so a passage the user may not see never reaches the model. It is not filtered out afterwards.
- The model that checks the answer is not the model that wrote it. Every answer is scored by independent models against its own cited sources and carries one of three labels: Verified — Cite Source, Review Recommended, or Do Not Rely — Consult Expert.
- We are specific about what we do and do not do. Where a control is not in the product yet, we say so in writing — before your procurement team has to ask twice.
What we don't do
The defaults that protect you
No third-party model API calls as deployed
The models that touch your content run inside your deployment. A default install calls no external model service. Wiring one in later would be an explicit, configurable change your own team makes.
No model training on your data
Citorum does not train or fine-tune on your documents, your queries or your responses. Model weights are loaded read-only and shared across requests; no request modifies them.
No corpus or query data to Citorum
The Citorum control plane carries license state and, only with your opt-in, aggregate operational telemetry — query counts, latency percentiles, error rates. It does not receive your documents, your questions, your answers or your users' identities.
No over-the-air model swaps
New model versions arrive through a rollout your team approves. We do not push model changes into your deployment, and the record for every answer names the model version that produced it.
Reviewing us against a questionnaire?
Send it over. We will answer it against our own capability audit rather than against a brochure, and we will flag the rows where the answer is no.