Your private material
- Chats and project history
- Approved memories
- Knowledge Vault documents
- Embeddings and indexes
- Dataset contents
- Repository previews
- Generated artifacts
- Private evaluation answers
RangabotThe assistant runs on your computer, rejects remote model configuration and keeps every sensitive collection outside the public website and source history.
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.
Non-loopback Ollama URLs are rejected so configuration mistakes do not silently transmit prompts.
Databases, vault material, approvals and artifacts are ignored by Git and omitted from website builds.
Unavailable live data and unsupported actions must be stated rather than fabricated.
The release adds stronger local state handling without expanding external access.
A failed turn may retain the exact local request, response mode and reply receipt for review. Failed partial output is not reused, and nothing is sent automatically.
Dataset descriptions, aliases and confirmed joins are saved locally against the exact dataset identity. They cannot grant file access or add a requested operation.
Profiles separate application-managed workspaces. They do not isolate the wider filesystem, add encryption or promise secure deletion.