What is stored and what is sent

Which data sits in files, which in the database, and what goes out?

A module's files and database sit on the machine running its instance; data leaves through features people set up or use, and administrators decide which of AIEUS's own AI features are on. Keep in mind: Any account holder can connect their own AI app without an admin; it reads what that person can read, and whatever it takes into its conversation goes to the app's own provider, outside the module's settings. The host who runs that machine can reach the data regardless; the hosting agreement, not AIEUS, limits that.

A module (a separate space within AIEUS) keeps its data on the machine that runs its instance. Its files are kept as ordinary files, which are the real copy. Its accounts, permissions, bot conversations, settings and secrets are kept in a database. Keep in mind: An instance is one running AIEUS system that can hold many modules. All of them live on that machine, in one shared database store. Each module keeps its own separate database in that store. Your instance's host runs that machine.

Not offered: AIEUS does not encrypt stored files or the database as a whole. Whether the disk is encrypted and which country the machine is in are for your instance's host to say. The same goes for how long deleted data and old backups are kept. Keep in mind: Backup copies go to the storage service and region chosen by the administrator who sets up backups. That storage's own encryption settings apply. AIEUS never deletes old backups automatically.

Outside a single machine, AIEUS will not start if its Web App, or the sign-in page it shares with connected apps, is set to a plain, non-HTTPS address. The HTTPS address and its certificate come from the instance's host. Keep in mind: The check applies once the Web App's address is set, which the standard install always does. A setup without that address can let connected apps sign in at a plain address.

Data leaves the machine only through features someone sets up or uses. These include requests to AI providers, AI apps a person connects, publishing files to a Git repository (a versioned file store), public pages and off-site backups. Keep in mind: A connected AI app can read the text of any file its user may read. What is said in that app stays in that app. A public page (one that opens without signing in) shows module data only through an opening the module deliberately makes for outsiders.

When an administrator turns on search by meaning or summaries, AIEUS sends that feature's provider the text of every file of the listed text types. These types include notes and code. Files in private folders are sent too. Search results still respect each person's access. Keep in mind: Folders an administrator excludes are skipped. Very long files are cut short. The words people type into search by meaning are sent too. What the provider does with your text is governed by your agreement with it, not by AIEUS.

Only administrators manage providers. They control what leaves AIEUS by choosing which features to turn on and by excluding folders. They can also shorten the list of file types sent, or lower how much text per file goes out. Keep in mind: A folder exclusion takes effect only after an administrator applies it, which is a step separate from saving. It stops future sends only. Summaries already made stay with their files.

By default, each bot reply sends Anthropic the bot's instructions and descriptions of the bot and module. It also sends the conversation so far, including other participants' messages, and your message. Whatever the bot looks up while answering goes too, and can include private file contents. Keep in mind: A bot with its tools turned off looks nothing up. A bot acting for an administrator can read the module's settings and stored secrets. Whatever it reads goes to Anthropic. The conversation history is capped at 2,000 messages and can be set lower.

Images, PDFs and audio never go out automatically. One of these files reaches a provider only after an administrator chooses a provider for that job and asks to turn the file into text. Without a provider, PDFs and scans can be read inside AIEUS. Keep in mind: Only PDF, PNG, JPEG and WAV files up to about 8 MB are handled. Audio always needs a provider. Scans read inside AIEUS must be in English and 20 pages at most. Conversion by a provider is tested only against stand-in services. Results may be wrong and need review.