Hi Ellie.
For Unity Forms to be shared they are accessed via the OnBase Web Server. Meaning the same security applies to the OnBase Web Client as they do to the Shared Unity Forms access via a URL. Further, any HTTPS bindings associated with the OnBase Web Server would apply and be used to encrypt the transfer of the data from the server to the client.
The only caveat is with respect to the user account used to access the form. The Shared Unity Form can be configured to require a user to authenticate, or user a common user to authenticate (i.e. Use Fixed Credentials).
Since there is personal information on the Unity Form you'll want to make sure the user authenticates in order to access the Unity Form.
The next consideration is around authentication. Any method supported by the OnBase Web Server is available for authenticating the user in order to access the Shared Unity Form. Since the forms are being access externally, you'll need a way to authenticate the users. This could be done through federated authentication (SAML, third party identity provider) or by using an OnBase username and password.
You can also look into the FormPop configuration settings which will allow you to setup a checksum.
Hope this helps.
