Keychain credential storage
Keychain credential storage means that broker logins and API keys are saved in the operating system's own secret store, such as Windows Credential Manager or the macOS Keychain, rather than in an application file, a log or a remote server. The application reads them at connection time and never writes them elsewhere.
Senzoukria · Glossary · Updated September 2026
Why an OS keychain rather than a config file
- The secret is encrypted at rest by the operating system and tied to the logged-in user account.
- A copied configuration folder or a shared screenshot of settings does not carry the password.
- Crash reports and logs can be expurgated more reliably when the secret never enters application memory in plain text longer than needed.
- Rotating a key means replacing one keychain entry, not searching files.
What it does not protect against
A keychain protects the stored copy of a secret. It does not make a weak password strong, it does not stop credentials typed into a phishing form, and it does not hide the secret from software running under the same user session with the right permissions. Broker credentials for a platform are often different from the ones used on the broker's website; the keychain stores whatever was entered, correct or not.
In Senzoukria
On the Broker connection card, the connection form states that credentials go straight into the operating system's keychain and are never written to a file, a log or a screen. The Rithmic guide repeats the instruction: enter the account's username, password and system name in the desktop connection flow, and do not enter broker credentials into a public website form.
Vendor API keys follow the same path. The connection manager hint says vendor API keys are stored in the OS keychain and never leave the backend. The AI provider screen shows Key stored in the keychain once a Claude key is saved, and the assistant panels repeat that the key is stored in the operating system's keychain, never on Senzoukria's servers. The desktop installer from the download page is the only build that has this keychain access; the website itself stores no broker credentials.
Common mistakes
- Pasting a broker password into a website or a chat window because the desktop asked for it once.
- Assuming a stored key was verified; the connection manager distinguishes Key verified with Anthropic and saved from Saved, but Anthropic could not be reached.
- Sharing a machine account with someone else and expecting the keychain to separate their secrets.
- Forgetting that a preflight diagnostic reports Not run for authentication when no password is saved on the connection.
Related
This page in other languages
Frequently asked questions
- Where exactly is my Rithmic password stored?
- In the operating system's secret store for the logged-in user: Credential Manager on Windows, Keychain on macOS, the secret service on Linux. The desktop reads it when a connection starts. It is not written to a settings file, a log or Senzoukria's servers, and the website never asks for it.
- Does the keychain send my API key to Senzoukria?
- No. The key is used from the machine where it is stored, and requests go directly from the desktop to the provider, such as Anthropic, who bills the key. The connection manager can verify the key with the provider at save time, which is a direct check, not a relay.
- What happens to stored credentials when I uninstall?
- The keychain entry belongs to the operating system, so it may remain after the application is removed. Delete the connection profile inside the desktop first, or remove the entry from the OS secret store, if the machine changes hands.