How to secure our form brick when embedding forms publicly

art_in_sky

I have created several forms using the Form Brick/App. Some of these forms collect sensitive or personally identifiable information (PII) from users. Since these forms are publicly embedded to collect user information, how can I ensure they are properly secured?

ArborRose

I develop back-end secured applications using Visual Studio, hosted on HTTPS-secured websites with authenticated logins. I then integrate the resulting data into Domo like any other data source.

I avoid public embedding of forms and recommend using Private Embed or SSO Embed via Domo Everywhere to control access. I also limit the collection of personally identifiable information (PII), and never store highly sensitive data—such as Social Security numbers or license numbers—unless it's within a custom, securely designed application.

Domo encrypts data in transit and at rest, but it's critical to ensure your form submissions are transmitted over HTTPS and don't expose raw data. Additionally, it's good practice to implement data retention and deletion policies and to inform users about what data is being collected and how it will be used to support privacy compliance.

Finally, make sure you review your design and plans with your company's security and legal teams to ensure you are aligned with internal policies and regulations.