GURUWhat the product controls
- collections are selected separately
- retrieved sources appear beside the answer
- API keys can be limited by collections and request quotas
- operational actions can be recorded in an audit log
Janus.Guru
Security starts with data boundaries and responsibility
Before a pilot, a team must know where documents live, which fragments reach a model, who has access, how long logs remain, and who approves the final answer.
What each deployment fixes
- document and index storage
- cloud, local, or hybrid model routing
- data allowed into model context
- retention and deletion rules
- roles, access, and personal-data processing
What remains human
- legal assessment
- editorial publication
- an official response
- access and retention policy approval
- primary-source review
Frequently asked questions
- Does Janus.Guru send every document to an external model?
Not necessarily. Retrieval selects relevant fragments; the model route and context policy are deployment decisions. - Does this page guarantee storage in Kazakhstan?
No. That requires a chosen infrastructure, providers, and a written deployment agreement. - Can restricted documents go into the public demo?
No. Sensitive material needs a separate private workspace, access rules, and an agreed processing policy.