How Are My Database Credentials Handled?

DBEverywhere is designed to hold your credentials for as short a time as possible, and only store them permanently if you explicitly ask.

Default Behavior: Session-Only

When you connect to a database without saving the connection, your credentials (host, username, password) are:

Encrypted with AES-256-GCM and stored temporarily for the duration of your session.
Used to authenticate with your database through phpMyAdmin or Adminer.
Wiped automatically when your session expires or when you end it manually.

Credentials are not written to disk in plaintext at any point. They are encrypted in the session store and blanked by the cleanup process as soon as the session ends.

Saved Connections (Paid, Opt-In)

If you're on the paid plan and check "Save this connection," your connection details are encrypted with AES-256-GCM and stored in our database. Even within saved connections, password saving is a separate opt-in — you can save the host, port, and username without saving the password.

Encrypted fields: - Host - Username - Password (only if you opt in) - Database name

The encryption key is stored separately from the database. Decryption only happens in memory when you reconnect.

What We Don't Do

We don't log your queries.
We don't inspect or store your query results.
We don't share credentials with third parties.
We don't retain credentials after a session ends (unless you saved the connection).

Revoking Access

You can cut off DBEverywhere's access to your database instantly by removing our IP address from your database firewall. No credentials need to be rotated on our side — once the IP is removed, we can no longer reach your database regardless of what's stored.

You can also delete any saved connections from your dashboard at any time, which removes the encrypted credentials from our database immediately.

For more details, see the Security page.