On your own computer
Documents stay on your own computer; it organises them and finds them by keyword. Works out of the box — no server needed.
Your company knowledge base runs on your own server; its memory stays on the computer doing the work, and your files and code are handled there too. The platform only handles sign-in, relays requests to the model and keeps usage and activity logs — it doesn’t store your files, knowledge base or memory. The table below lists exactly what lives on the platform.
You choose where the knowledge base lives; memory always stays on the computer doing the work.
Documents stay on your own computer; it organises them and finds them by keyword. Works out of the box — no server needed.
One shared library for everyone. Set it up in DooAny with one click — confirmed in person on the computer. Use an existing server, or have it buy one for you. The platform only authenticates and relays; it doesn’t store knowledge data.
System addresses, ways of working, each person’s habits — everything it remembers is stored on that computer: never uploaded to the platform, never synced between computers. What it learns in a direct chat is used only for that person, and in a group only in that group; if it can’t tell who said something, it doesn’t store it. Open anyone in Contacts to see what it remembers about them.
The files and documents it works with stay with you. Two things to be upfront about: to generate answers, the relevant content is relayed through the platform to the model service; and the mobile app’s chats, meeting records and voiceprints are stored on the platform, so you can see your history on the phone and it can tell who’s speaking.
Research, reading files, drafting, and replying to whoever asked happen directly. Before changing your files, running commands or messaging others for you, it stops and shows you a confirmation card.
Who asked, what was done, to what, whether it worked, why it failed, from which IP and when — all in the audit log.
Each company has exactly three roles — owner, admin, member — and they can’t be customised, so no one ends up with permissions nobody can explain.
Model keys are the most valuable thing we hold: server-only, stored separately, ciphertext only. Passwords are stored only as one-way hashes.
AES-256-GCM . If ciphertext is tampered with, decryption fails outright instead of producing a wrong key.argon2 .For policy and business questions it only uses documents marked “Active”. Drafts, pending, expired or superseded documents are never used. Every answer cites its source.
No. We don’t store your files or knowledge base, and we don’t train models on your files, knowledge base or conversations. To answer a question, the relevant content is relayed through the platform to the model service.
Work already happens on your own computers, and the knowledge base can run on your own server today. If you need a full deployment, mention it when you book a demo and we’ll assess it together.
No. For spending, publishing, approvals and HR, it gathers information and evidence; a person takes the final step. The documents, sheets, code and conclusions it hands back note which sources it used and what it’s unsure of, so you can review them before use.
Calls stop — no overspending — and resume as soon as a top-up arrives. The admin console shows who used how much, and on which models.
No. One person in different companies has separate identities; departments, permissions and tasks never mix.
Files and the knowledge base are already with you. Platform accounts, usage and logs are handled in order: stop running tasks, export data, confirm keep or delete, revoke connection credentials, then archive records.
Want the full terms?