Skip to main content

Data privacy

Hex takes your data privacy very seriously.

Hex admins can opt-out their entire workspace from Magic from the Settings > Magic settings page. This will disable Magic for all users.

  • Neither Hex nor our third-party model partner (OpenAI) train models using data from Hex customers, eliminating the risk of intellectual property leakage through passed context. This means a model won’t spit out your code to someone else.
  • Hex doesn’t send underlying Customer Datasets to the models. This means that values of specific rows of a table aren’t at risk of leakage through Magic.
  • Hex uses Customer Database Metadata like schemas and Customer Input Data like project code as model context. This means that any sensitive information in your table or column names, or in your code, could be passed to a model.
  • Magic is built on Hex’s secure data platform. These features are protected by secure practices and policies, are included in our SOC 2 Type II and bug bounty program, and safeguarded by the principle of least-privilege. You can learn more on our Data Privacy and Usage FAQ, Trust Center, and read our Hex Magic Terms and Conditions.