Where your manuals live, who can see them, what we do with them.
This page is written in plain language on purpose. If anything here is unclear, that's a defect: tell us.
Every client runs a separate, single-tenant instance of Answerlore. There is no shared filesystem and no shared database between clients. Keeping clients apart is a property of the architecture rather than a policy we promise to follow: there is no shared database or filesystem for data to cross.
Your instance
- Your manuals
- Your knowledge base
- Your technicians
Another client's instance
- Their manuals
- Their knowledge base
- Their technicians
Nothing crosses the gap because there is no bridge.
Your knowledge base is stored as human-readable text files, one topic per file, each carrying its source manual, page range, and the date a human last verified it. Not an opaque vector database. Open any file and read it. Correct a wrong answer by editing the sentence.
Export your entire knowledge base at any time, in the same readable files. If you cancel, we delete your instance and confirm it. Your documented knowledge is an asset you keep, whoever you buy software from next.
No model training
We don't train AI models on your documents.
Two processors, named on request
Your instance runs on a hosting provider, and answering a question sends that question plus the retrieved passages from your knowledge docs to an AI model provider's API. Nothing else receives your documents. We name both providers in writing on request, and this page changes when they change.
No badge we haven't earned
We don't have a SOC 2 report yet. We're early, and we won't print a badge we haven't earned. What we have instead is the architecture above, which you can audit, and this page, which we keep true.
Short answers, kept current with the implementation. If yours isn't here, ask and we'll add it.
Who at Answerlore can access an instance?
The people running your deployment, for the work you've asked for. Access is per-instance, not global.
Is data encrypted?
In transit, yes, over TLS. At rest, your instance's storage is encrypted by the hosting provider. Ask on a walkthrough and we'll name the provider and the region.
What's the model provider and the data-processing path?
Your manuals and knowledge docs stay on your instance's disk. For each question, the question text and the passages retrieved for it go to the model provider's API and come back as the answer; the provider is not given your whole knowledge base. We'll name the current provider and sub-processors on request, in writing, and this page changes when they change.
What are your backup and deletion timelines?
Backups are taken for recovery, not retention. When you cancel, we delete your instance and confirm the deletion to you.
Bring your IT person to the walkthrough.
Single-tenant architecture answers some compliance questions. Bring the rest, and we would rather show you than promise you.