Security without big words

Personal: projects, chats, files and memory are stored on the device in a local SQLite database.

A model provider receives only a request's context: the message, selected memory and excerpts you added.

Team and Business: shared project content is stored as encrypted objects in the chosen S3 through a sync gateway (TLS and AES-256-GCM).

The central account database holds accounts, licences, roles and service pointers. Chat text, files and memory never go there.

A key is typed into a masked field and goes straight to the system vault. On macOS that is the Keychain.

The interface only learns that a key is saved, never the key itself. Keys never reach logs or exports.

Backups carry no keys or connection addresses: on a new device you add them again.

Windows: storage in Windows Credential Manager is not yet verified on a device.

Hermes gets a one-time session token instead of an API key. It reaches the model only through the ORYVIO proxy, with permission checks.

Before launch ORYVIO checks every file of the embedded Hermes against pinned hashes and rejects altered ones.

On macOS the agent runs in a sandbox: outside network closed, home folder reads denied, writes only to granted folders.

If the sandbox is unavailable, and on Windows and Linux, the agent does not start until verified isolation exists.

Terminal, file writes and browser: only with approval of each action. Off until security checks pass.

Sign-in by email and a password of 12+ characters. Passwords are stored as salted hashes; device sessions can be revoked.

Sign-up and email confirmation were checked by the owner on a Mac in the pilot.

We never collect passwords or cookies of other services, ChatGPT included.

The plan belongs to the organisation's licence. The server checks each member's role on every action.

Invited Team members work with team projects only in the cloud and do not save them to a local database.

Removing a member closes access on the server. The app's cache cannot grant new rights.