No cloud AI Live
The assistant and its models run on your server. No cloud model, API, connector or telemetry receives your mail, notes, files, chats or memories.
Security and privacy
Ghalixy AI runs on a server you own. This page says what that means, one item at a time. Items that work in a release you can install are marked Live; items built but not yet in one are marked Coming, with no dates.
What never leaves the box
The assistant and its models run on your server. No cloud model, API, connector or telemetry receives your mail, notes, files, chats or memories.
The exceptions are things a person does on purpose: an email sent from an account they connected, a message on a chat network they linked, a file copied to their own cloud drive after their approval tap.
Anything the server itself sends out is written in the egress log, in Settings, then Privacy: what, to where, and when. Anything the product might send is on a short list, and what is not on it is refused.
Everything is kept per person. A person's mail, notes and chats are visible to that person, and to others only by a share they chose.
Control
Sending an email, deleting a file, sharing and other changes wait for an approval. In the apps it is a tap with your fingerprint or face, on a key that stays in the phone.
Everyone signs in with a passkey or a security key. There is no password to steal.
A sealed folder in Files or Notes is hidden from the assistant's search, and can't be shared. Encrypting it with a key made from your passkey Coming.
The sign-in server signs a short-lived pass for each request, valid for seconds and for one app, and the server takes who you are from that pass.
The computer shows a code, your phone scans it, and you approve with your fingerprint. The computer gets one browser session, never linked to you, which ends when you close the tab (after 30 minutes idle, 8 hours at most) or when you end it from your phone. It receives nothing before you approve.
One identity for each person, made on their devices and never issued by a server, wrapped by each device's own hardware key. Nothing signs in with it yet.
Backups and recovery
Backups are encrypted before they leave the machine's disk, and checked as part of your Care plan.
The password that opens the backups stays on the server and on a recovery card or sheet you keep. It stops travelling inside the backups, or beside the copy a computer at home keeps. The card is shown once, to keep or print, and is never sent anywhere.
The models and speech run on a network of their own with no way out and no way into the rest of the server. A separate downloader, which never sees what you ask, fetches only the models a release names.
Updates
A release is signed by Ghalixy, and a server checks the signature before it installs. A server keeps two versions and can roll back.
Every release names the key that signed it, and a server takes an update only from a key of Ghalixy's that hasn't been retired. A stolen key can be shut out without reinstalling.
Each release's fingerprint, and nothing of yours, is written into an open log anyone can read, kept on Ghalixy's public server and stamped into Bitcoin once a day. No one could slip one server a different update unseen. Nothing checks the log yet; checking comes in a later release.
Support sessions
When you ask for help, an administrator opens a support session, picks what it reaches and for how long (an hour by default, four at most), and approves it with one tap. The server calls out to us only after that tap, and the session ends on time or when you end it.
Support sees health, services and logs with names, addresses and content removed. Never people's data: nothing in the product can change that. When something inside your data needs fixing, your administrator does it while we guide.
Each page opened and each command run, with the names of who opened the session and who supports it, is in a record your administrator can read.
Questions about any of this: contact us. For an office, see For offices.