The Privacy Policy Landing Page
Users see a dedicated privacy policy page at the appropriate point in the flow, before document or face capture. This replaces any inline or modal presentation of the policy. Company name is inserted into the agreement text wherever the template refers to the requesting entity, so the user can see who is asking for their data. Use the legal name of your entity, not a trading name.Drafting the Policy
Privacy policy text is a rich text editor rather than a plain field, and there is one per language you add. It can carry the structure a compliance team expects:- Formatting — bold, italic, underline and strikethrough for key terms
- Structure — headings, bullet points and numbered lists
- Media and links — hyperlinks to external documents, and embedded images or video
Multiple Languages
Each language is a separate card. Add privacy policy creates a card for a new language, English being the usual default. Expand or collapse a card with its chevron, and remove a translation with its trash icon. A user is shown the policy matching the language they are verifying in. Provide one for every locale you have enabled, or users in a locale you have not translated fall back to your default. See Supported Languages for the locales available, and Localization for how the language is chosen.Requiring Consent
Request Privacy Policy confirmation decides whether acceptance is explicit:
Leave it on where you need a record that consent was given. Which of the two satisfies your obligation is a question for your compliance team, not a technical one — see GDPR for the wider data-protection picture.