Data, Privacy, and Maintenance
The knowledge base stores hosted copies of imported materials, parsed text, Chunks, and retrieval indexes. Whether data leaves the local machine depends on the services chosen for parsing, OCR, embedding, re-ranking, and chat.
What is saved after import
Copies of files in a file or directory
For the knowledge base to continue processing and displaying
Re-add or replace after the original file is updated
Webpage and note snapshots
Preserve the content as it was when imported
Re-import after the source is updated
Parsed text and Chunks
Preview and retrieval
Re-index after changing the processor or chunking
BM25 keyword index
Exact word search
Rebuilt when re-indexing
Vector index
Semantic retrieval
Generated or rebuilt after configuring or changing the embedding model

What boundaries may a single query cross

Cloud document processor
File content used for parsing
Cloud embedding model
Material chunks and retrieval queries
Cloud re-ranking model
Queries and candidate chunks
Cloud chat model
Questions, conversation context, and retrieved chunks
Local equivalent capability
Perform the corresponding processing on the local machine
Perform a full maintenance check
Full backup vs. slim backup
Full backup
Data files such as chats, settings, and knowledge bases
Device migration, pre-deletion protection, full restore
Large file size, takes longer
Slim backup
Mainly chat logs and settings, skipping data files such as images and knowledge bases
Quickly preserve common settings and chats
Cannot restore a complete knowledge base on its own
How updates and deletions are handled
Source content updated
Re-add the same-named material.
Choose [Replace] when you need to overwrite the old version; choose [Keep all] only when you truly need both to coexist.
Wait for the material to become ready.
Spot-check the text and Chunks.
Run fixed retrieval regression questions.
Processing settings updated
When only the processor, OCR, chunking, or model settings are changed, run [Re-index] on existing entries. Changing the configuration itself does not automatically reprocess old materials.
Delete materials or knowledge base
Deletion removes the content and indexes hosted by the knowledge base, but it does not delete the files in the original path or the original notes. Before proceeding, make sure the original source can still be found, a full backup is available, and check whether any agents are still bound to this knowledge base.
Configuration notes
Material version
Keep only the current version for the same use
Fixed questions still hit the correct version
Mixing old and new rules
Cloud service
Confirm item by item according to sensitivity level
Check the processor and model settings
Documents or chunks are sent to external services
Backup
Create a full backup before major changes
Check entries and retrieval after restoration
Slim backup lacks knowledge base files
Re-index
Process representative materials in batches
Compare the same question set before and after
One-time rebuild loses a usable baseline
User case
Xiaolin wants to migrate the team policy repository to a new computer. First he records the processor and model settings, creates a full backup, then checks the text and Chunks of three materials after restoring on the new computer and repeats the original five retrieval questions. Only after everything passes does he clean up the old environment.
The completion criteria are: the number of materials and titles match, key questions still hit the same source, and the team confirms that all cloud services meet data requirements.
Fully offline checklist
Document parsing and OCR use system, local, or self-hosted capabilities.
The embedding model runs locally.
Do not use cloud re-ranking, or use local re-ranking capabilities.
Conversations and agents use a local chat model.
No MCP, web search, or channels that send content to external systems are enabled.
FAQ
Continue reading
Last updated
Was this helpful?