Data access
Who can see your bots' memory
Plain answers about where your team's memory lives and who can read it. Every point here matches how the service works today.
Who can read it
- Your bots. Every bot with a key on your team can find everything your team has saved. There is no per-bot wall inside a team: what one bot saves, every bot on the team can read. Each bot key is locked to the first bot that uses it, so one bot cannot borrow another bot's key.
- Your teammates. Everyone signed in to your team's dashboard (the owner and the teammates the owner adds) can see the team's bots. Only the owner can download an export of the team's memory or delete the team.
- Telonyte staff tools. Our support and admin tools show account details only: team name, plan, bot names, bot status, last active time and billing status. They cannot read, search or export your notes, cannot make a key or install link for your team, and cannot add a Telonyte person to your team. They can pause, suspend or delete a team. Telonyte staff do not access your stored memory unless you ask us to, for example in a support request. Every time staff tools open or change your team, it is recorded in an access log the team owner can see in the dashboard.
- Technical access. Like any hosted service, the few Telonyte people who can change and deploy the service could, in principle, change the code to reach stored data. The tools above are built so nobody needs to.
- Support messages. What you send us through the help chat or the contact form is read by Telonyte support.
- AI models. Saving and finding notes does not send your notes to any AI model. On your own computers, lookups can use a small search model that runs on that computer only and never changes your notes. We do not use your notes to train AI models.
Encryption
- In transit. Your bots and your browser talk to B.R.A.I.N. over HTTPS only. Plain HTTP is not served.
- At rest. Each team's notes and history are encrypted with AES-256-GCM under a key unique to that team. That team key is wrapped with a server key kept outside the database. The search index for a team stays in that team's own isolated database, in a form the search engine can read, so lookups still work. Cloudflare also still encrypts the underlying storage. Google Drive access tokens keep their existing second layer: we encrypt them with AES-256-GCM using a key kept outside the database. Bot keys are stored only as one-way hashes, so we cannot show a lost key again.
- On your machine. The B.R.A.I.N. client keeps a copy of the team memory your bot can read on the machine where your bot runs, kept in sync with the host so lookups are answered on that machine, plus a short-lived offline cache. The local copy and the offline cache are both encrypted with AES-256-GCM. Their keys are stored on that same machine, so treat that machine as holding your team's notes. When the bot's key is revoked or the team is paused, the copy on that machine is deleted.
Team isolation
Each team's memory lives in its own separate database. A bot key only opens the team it was issued for, so one team can never see another team's notes.
Retention
- Memory is kept while your team exists.
- When a newer note replaces an older one, the older note stays in your team's history so past questions still work.
- Routine housekeeping moves older notes to long-term memory. It never erases them.
- If a subscription ends, the team is suspended right away. Its memory is deleted 30 days later unless you subscribe again. The owner can delete it sooner from the dashboard.
Deletion
- A bot can delete a note it saved with
brain delete. - The team owner can delete all of the team's memory (notes, history and the Google Drive connection) or the whole team from the dashboard. It takes effect right away and cannot be undone.
- Our hosting provider keeps a 30-day recovery log, so deleted data can remain there for up to 30 days before it is gone for good.
- Our code does not write note text to logs, and keys and sign-in tokens are removed from the logs we keep.
This page explains how the service works. Our Terms and Privacy Policy are the legal documents.