Skip to main content

Security and Privacy

rudol directly connects to your datasources and delegate query execution to your underlying technology (i.e. databases like MySQL and PostgreSQL or warehouses like Snowflake or Google BigQuery) and only consumes metadata results. This way your actual data never leaves your premises.

Also all metadata changes (such as additions, modifications or removal) done in rudol don't have actual impact on your original datasource because metadata sync is one-way only from your datasource to our infrastructure, see the next section for more information.

Catalog items metadataโ€‹

All catalog items metadata is stored in:

  • Amazon S3, static assets
  • MySQL, database for persistence
  • OpenSearch, to show you better search results

User dataโ€‹

rudol stores data on users in its own MySQL database. It also stores all sensitive fields like passwords hashed to keep them secure.

Any user data transmitted over the internet is SSL-encrypted over HTTPS. ๐Ÿ”’


rudol is deployed using Kubernetes in a managed VPC (virtual private cloud).

Only administrators have remote access to either the Control Plane or individual Nodes.


rudol secures all communication using Hypertext Transfer Protocol Secure (HTTPS).

This protocol is encrypted using Transport Layer Security (TLS).

Incoming connectionsโ€‹

rudol will always perform any connection to your datasources using the public internet-facing IP so you can safely add it to your firewall whitelist to secure your incoming connections.

Privacy policyโ€‹

You can read rudol's Privacy Policy here.