Security
Nothing is more important than your customer and business data.
Security FAQs
Can I connect to a database in a VPC or behind a firewall?
Yes, you can connect through a server or bastion host via SSH, or deploy Basedash on-premises for full control.
My business is in a space with very high privacy requirements like Medical or Fintech. How can I make this secure?
For those types of businesses, Basedash offers a self-hosted solution. Details of that can be found here. If you'd like a demo, you can reach out to use or in the meantime, you can still try Basedash out and join our demo workspace to understand how it is used, or connect non-production data sources if you have them.
Does everyone have the ability to edit everything?
Not unless that's what you want! By default, all data is editable when it's connected, but only admins who make the connections have access to that data. Changing entire data sources or tables to be read-only just takes a single click in the configuration panel. You can be global if you want, or you can be granular and disconnect or restrict edits by the attribute if you want.
Do you have a way of tracking who made a specific edit or an audit trail?
Yes! We track edits made in your workspace in the Activity panel. We're working on ways to make this better and require more oversight, so let us know if you'd like to be an early pilot of those features.
What data do you collect?
We monitor application performance, load times, and use Fullstory to analyze how Basedash is used. All of your data is hard-coded to be masked and not recorded or captured.
See our Privacy Policy for more details.
What data is cached on the client-side?
We cache some information on the client side to improve performance, such as table names and view definitions, but these are not accessible to our servers directly. Beyond that, we do not cache or store any data from your databases on our servers.
What database details are stored by Basedash?
We only store the data needed to connect to your database, not the actual data itself. This includes your database name, credentials (fully encrypted), configuration, schema, and type.
What workspace info and configuration data are collected?
Details about your workspace including billing, name, type, and info about other members of your workspace. We also capture the configuration of SQL or basic views created in your workspace.
What account details are collected?
We capture your name, email, role, and user preferences such as avatar. We believe that user data shouldn't be captured unless it's necessary for building you a better product. Reach out to us at any time and we'll delete your account.
