Data Security at Enhanza

In this article, we delve into the robust measures we employ to ensure the confidentiality, integrity and availability of your sensitive and valuable data. From authentication protocols to compliance with EU regulations, join us as we navigate through our commitment to safeguarding your information.

  1. Authentication and Authorization:
  • Enhanza utilizes Google authentication and authorization mechanisms to grant access to data.
  • Users can only access data within their respective workspace.
  1. Data Storage:
  • Workspace data is stored in separate shared-nothing BigQuery datasets.
  • Permissions to datasets are managed by the workspace owner or admin within the enhanza application.
  1. User Permissions:
  • There are two types of users in enhanza: Viewer and Member.
  • Team members are actual users who can log in to the Enhanza.
  • Viewers function, similar to service accounts, do not require registration in our app.
  1. Compliance with Regulations:
  • To comply with EU regulations (GDPR), all data is stored in EU datacenters.
  1. User Control:
  • Users have full control over their data and can physically delete it from Enhanza storage at any time.
  • Data is also automatically deleted if the user/connection remains inactive for some time.
  • No additional backups or snapshots of user data are stored.
  1. Data Removal:
  • Data is completely deleted when a data source is removed from our app.
  1. BI Tool Integration:
  • Users are free to use any BI tool that supports BigQuery as a datasource.
  • The same Google authentication mechanisms and permissions set in Enhanza are enforced.
  • This includes Enhanza’s pre-built Microsoft PowerBI template and Google Looker Studio connectors.
  • For tools that do not support the default Google authentication flow, workspace owners can create a Google Service Accounts from within Enhanza.
  • Service accounts are handled as regular workspace data viewers in this case.
  1. Additional Resources:
  • Read about Bonnier’s BigQuery use case here.
  • Watch a video on Spotify’s BigQuery use case here.
  • Refer to Google’s own documentations regarding data security in BigQuery here.

Any questions on how we safeguard your sensitive data? Please post you comment below or reach out to us directly.