Your private material
- Chats and project history
- Approved memories
- Knowledge Vault documents
- Embeddings and indexes
- Dataset contents
- Repository previews
- Generated artifacts
- Private evaluation answers
Local by design. Permission by exception.
The assistant runs on your computer, rejects remote model configuration and keeps every sensitive collection outside the public website and source history.
Local access boundaries
- Repository allowlisting
- Dataset allowlisting
- Per-chat attachments
- On-demand file previews
- Memory approval
- Reversible access
- Visible calculation receipts
- Local backup and deletion
External paths
- Cloud model handoff
- Automatic web browsing
- Email access
- Calendar access
- Telemetry
- Remote Ollama servers
- Silent uploads
- Public model fallback
Honest threat model
Local does not mean invulnerable.
Malware or another user with host access may read local files. Models can still produce incorrect content. Approved repositories and datasets may contain sensitive information. Rangabot reduces network exposure; it cannot replace operating-system security or human review.
Loopback model
Non-loopback Ollama URLs are rejected so configuration mistakes do not silently transmit prompts.
Private storage
Databases, vault material, approvals and artifacts are ignored by Git and omitted from website builds.
Visible uncertainty
Unavailable live data and unsupported actions must be stated rather than fabricated.