Web Form FAQ

Yes, the setting Mask Entry in Web Form in the Web Form Customization screen will allow you to mask personal information and prevent unauthorized users from viewing that data. This setting also masks sensitive data on request details and in the Privacy Portal.

It is open to all user input type fields.

This action is restricted by design until email verification is complete. It is not recommended to send or share personal info with an unverified data subject until they have confirmed ownership of the email submitted on the request. If OneTrust customers elect to bypass this default security design, they can do so by manually moving the request to the next stage.

OneTrust supports a number of common attachment types as part of request fulfillment. For more information, see Accepted File Types for Privacy Rights Automation.

OneTrust does not externally index web forms, so customers must provide links themselves. Customers that don't want their web form to be indexed should use rel="nofollow" when linking to the form from their site.

OneTrust currently uses Google reCAPTCHA 2.0 for web forms.

Yes, with some exception. The web form does not support < or > characters to protect against possible malicious content.

Yes, you can delete web forms. However, if at least 1 request has been submitted through that web form, and that request still exists, then deleting the web form will not be allowed at that time.

No, deleting a web form is permanent. This action cannot be undone.

Yes, this ability is available to enterprise customers only. Contact support@onetrust.com to enable this feature for your account.

No, OneTrust does not currently support version reverting for web forms. You can however view version histories with supporting metadata. For more information, see Using Web Form Versioning.

Yes, you can export existing web form configurations as JSON files to import into different organizations and accounts. For more information, see Migrating Web Form and Workflow Templates.

While the disable redirect URL feature can redirect users to newer published versions of a web form, it is recommended replacing the older web form link with the newest link for the best experience. For more information, see Disabling Web Form URLs.

Yes, OneTrust web forms allow for custom validation with regular expression (ReGex) that can limit the acceptance criteria for input fields. For more information, see Custom Validation for Web Form Fields.

Yes, you can customize the web form URL to reflect your custom subdomain. This customization can also extended to the Privacy Portal URL. Please contact your OneTrust Team with more details to make a request for a fully qualified domain.

For more information, see Customizing OneTrust with a Custom Domain.

Each OneTrust web form template is pre-configured with a set number of supported languages. However, OneTrust does not support machine or auto-translation of the templates to meet custom translations. For more information, see Providing Translations on Web Forms.

Yes, in order to provide specific or ad hoc translations, you will need to provide them when configuring the web form. For more information, see Providing Translations on Web Forms.

Check if the Request Details field contains unsupported characters or HTML.

It is ultimately up to your organization to choose where to make your shareable link accessible to requestors. However, organizations commonly publish their web form via a hyperlink in their privacy policy or the footer of their public-facing website.

No, you cannot change form field IDs.