Your data

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.

Last updated 24 August 2026. We update this page when the facts change, not annually.
Your own instance, structurally

Every client runs a separate, single-tenant instance of Answerlore. There is no shared filesystem and no shared database between clients. Cross-client data contamination isn't prevented by a policy we promise to follow; it's impossible by construction, because there is no shared place for it to happen.

Your instance

  • Your manuals
  • Your knowledge base
  • Your technicians
no bridge

Another client's instance

  • Their manuals
  • Their knowledge base
  • Their technicians

Nothing crosses the gap because there is no bridge.

Readable, not embedded

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.

You can leave, with everything

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.

What we don't do

No model training

We don't train AI models on your documents.

No outside systems

We don't send your documents to any system outside your instance's processing path.

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.

Questions we expect from your IT person

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 documents are processed to answer your team's questions and nothing else. 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 most compliance questions, and we would rather show you than promise you.