Data Security

How do you protect database credentials?

Database credentials are encrypted before being stored. Visual DB will never display your password even if you are an authorized user. For example, after you create a connection, if you re-open the connection dialog, the password will not be displayed.

When Visual DB is self-hosted, the decryption key is only available on your server, and never leaves your server.

Do you cache data retrieved from the database?

We do not cache data retrieved from the database. Data is merely passed through to the client without being stored anywhere.

When Visual DB is self-hosted, data never leaves your infrastructure.

Where is the physical location of your data center?

Our data center is located in the US, specifically in Microsoft Azure cloud.

What security best practices do you recommend?

Self-host Visual DB when working with sensitive or regulated data. This ensures that your data never leaves your infrastructure and remains under your complete control.

Periodically rotate your database passwords and encryption key. Code to generate your own encryption key is available here.

Also, configure your database to only accept connections from specific IP addresses. This creates an additional layer of protection by preventing unauthorized access attempts from unknown locations.

These practices provide layered security that significantly reduces your risk exposure.