Screens: AI, MCP and security

Zero-knowledge encryption

Zero-knowledge encryption locks the connection credentials of an account project once more with a secret key chosen by the owner. Once it is on, nobody without the secret key — NeoSQL operators included — can unlock the credentials, and if the secret key is lost nobody can recover them. This page explains the screens for turning it on, unlocking, changing and turning it off. What it protects from whom, and how it differs from standard encryption, is in Security and where your data goes.

Where you can use itWebDesktopWithout signing inSigned inLocal projectsAccount projects

What's on the screen

Clicking the Secret Key Lock button at the right end of the explorer toolbar on the left of the project screen opens this window. The title and notice differ slightly between a project without connections and one with connections; what it does is the same.

No.NameDescription
1NoticeTells you what gets locked. In a project with connections, the credentials saved before turning it on were protected only by standard encryption, so it recommends changing the password on the database side afterwards if the credentials are very sensitive.
2Auto-generate a secure key (recommended)Generates a random 32-character string to use as the secret key. This option is selected at first.
3Enter manuallyYou enter a sentence that is easy to remember. Choosing it shows the secret key field, a strength indicator and a hint field. The strength must be Fair or better to continue.
4Next buttonGoes to the second step, which shows the secret key. Nothing is saved yet.
  • The button exists only in account projects. Local projects do not have this feature; their credentials are protected by the OS secure storage of this device (Security and where your data goes).
  • Only the project owner can turn it on. Other team members see the button disabled, and hovering over it shows Only the project owner can configure this.

Turning it on

  1. Open the account project with the owner's account.
  2. Click the Secret Key Lock button in the explorer toolbar.
  3. Choose how to make the secret key and click the Next button. If you choose Enter manually, 12 or more characters are recommended, and leading or trailing spaces are warned about. The hint is optional; never write the secret key itself.
  4. In the second step, take the secret key out with the Copy button or the Download .txt button and keep it in a password manager or company vault. Once this screen is closed, the secret key cannot be shown again.
  5. The last button works only when both the I have saved the key in a safe place and the I understand that recovery is impossible if lost checkboxes are checked. In the desktop app the Save securely on this computer (auto-unlock next time) checkbox is checked from the start; uncheck it if you do not want the key saved on this device.
  6. Click the Finish setup button. At this step the existing credentials are re-encrypted with the new key.
  • The warning (1) is ⚠️ This key will not be shown again. The secret key (2) is shown only once, at this step.
  • The Download .txt button (3) downloads a text file containing the secret key and the warning. That file is the secret key itself, so keep it somewhere safe.
  • Until both confirmation checkboxes (4) are checked, the Finish setup button (5) cannot be clicked.
  • In a browser the keychain checkbox is disabled and marked — Desktop only.

Unlocking

When you enter a project with it turned on, the Secret-Key Unlock window appears first unless you have unlocked it on that device. It is the same for the owner and team members.

  1. Enter the secret key in the secret key field (2). If a hint was written when it was turned on, the hint (1) is shown above.
  2. To not be asked again in the desktop app, check Save securely on this computer (3).
  3. Click the Unlock button (4).
  • A wrong secret key shows Incorrect passphrase. From the third wrong attempt on, you must wait before trying again; the wait grows by 5 seconds with each failure, up to 60 seconds.
  • The Cancel button goes back to the dashboard without opening the project. Clicking outside the window or pressing Esc does not close it.
  • The unlocked state lasts only while the app on that device is running. Restarting the app, reloading the page on the web, or signing in or out locks it again. A desktop app with the key saved in the keychain unlocks automatically on entry.
  • If the secret key saved in the keychain no longer matches because it was changed, NeoSQL removes it and shows the Cannot unlock with the saved secret key notification. Enter the new secret key.

The menu after turning it on

After it is turned on and unlocked, the toolbar button becomes the Lock button. The owner gets a menu; for other team members, clicking it locks immediately.

No.MenuWhat it does
1Lock session nowErases the unlocked key from this device's memory and shows the Secret-Key Unlock window. Disabled in a desktop app that saved the key in the keychain, because it would unlock again right away.
2Save to this computerDesktop app only. Locks and shows the Secret-Key Unlock window; the window opens with Save securely on this computer already checked, so entering the secret key and unlocking saves it. After saving, the Remove saved secret key from this computer item appears in this place.
3Change secret key...Sets a new secret key in the same window as when turning it on. The last button is Finish change. The credentials stay the same, and old keys that team members saved in their keychains no longer unlock it.
4Disable secret-key lock (permanent)...Clicking the Disable button in the Disable Secret-Key Lock confirmation returns to standard encryption. From then on, operators with the server code and key management permissions can unlock the credentials.

The Change secret key... and Disable secret-key lock (permanent)... items work only while unlocked. Without knowing the secret key you cannot turn it off either. The Help item at the bottom of the menu opens the help screen below.

What changes after turning it on

WhatWhat changes
Team membersThey must enter the secret key each time they enter the project (per device). NeoSQL does not pass the secret key to team members, so the owner tells them through a safe channel
Other devicesEven with the same account, each device asks for the secret key the first time. Browsers cannot save it in the keychain, so it is asked each time the project is opened anew
External MCPTool calls targeting a locked project are not run; they return a message asking you to unlock it in the desktop app

Setting the auto-lock time

In the My pageSecurity screen, choose in Auto-lock secret key when unlocked projects are locked again, and click the Save button.

  • The values are Off (prefer convenience), 1 minute, 5 minutes, 30 minutes and 8 hours (1). Off (prefer convenience) is selected at first.
  • The value is saved to your account and applies to every project with zero-knowledge encryption turned on. When the time comes and it locks, the Secret-Key Unlock window appears.
  • The time is measured from your last click or key press in the project you are viewing. A saved value takes effect on this device right away, and on other devices the next time the app starts or you sign in.

Help screen

The app has a ScreenZero-knowledge help screen summarizing the alternatives when the secret key is lost, how to keep the secret key, and how to use it on another computer. Its content matches this page. Open it from the owner's secret key lock menu or from the Help link at the top of the first step of the window that turns it on.

Things to keep in mind

  • If the secret key is lost, there is no way to recover the credentials. NeoSQL keeps no backup of the secret key. The database and its data are not affected, so get the credentials again from your database administrator and register them as a new connection.
  • The hint is shown in the Secret-Key Unlock window to every team member who enters this project. Do not write anything that hints at the secret key.
  • This feature protects the credentials while locked. While you work unlocked, the server decrypts the credentials at the moment it handles a request. Credentials saved before turning it on were protected only by standard encryption until then.
  • On shared devices, do not rely on auto-lock; when you are done, lock with the Lock session now menu or sign out.
  • Data inside the database is not encrypted. To hide values from team members, use Column masking.
  • Security and where your data goes: What standard encryption, zero-knowledge encryption, OS secure storage and masking protect, and their limits.
  • Column masking: Shows sensitive column values masked to team members.
  • My page: The page that explains the My pageSecurity screen.
  • MCP client setup: A locked project must be unlocked in the desktop app before MCP tool calls.