Data Sharing Consent

The Data Sharing Consent module allows organizations to request and record the user's consent before collecting, processing, or sharing personal information as part of the verification process.

This module typically appears before identity verification begins or whenever explicit user authorization is required to comply with privacy, regulatory, or business requirements. It helps ensure users understand how their data will be used and provides a clear opportunity to accept consent.

---

Where it fits in the flow

Data Sharing Consent typically appears before identity verification begins or whenever explicit user authorization is required.

Once the user reviews and accepts the consent terms, the flow continues to the next verification step, such as document capture, face capture, or another configured verification process.

---

User Flow

The Data Sharing Consent experience presents users with the information required to understand and authorize how their personal data will be collected, processed, shared, and protected throughout the verification process.

Users must review the consent terms and actively acknowledge them by selecting the consent checkbox. The Continue button remains disabled until consent is provided, ensuring explicit authorization before proceeding. Once consent is granted, the system records the user's agreement and advances to the next configured verification step, such as document capture, face capture, or another verification process.

---

Full Flow Map

This diagram presents the full sequence of screens involved in Face Capture, from tutorial and permission handling, to auto/manual capture, uploading, and final feedback.

---

Happy Path (Light & Dark)

The ideal user journey when consent is provided successfully with no interruptions.

The happy path represents the smoothest version of the experience, where the user reviews the consent information, understands how their data will be collected and used, provides explicit authorization by selecting the consent checkbox, and continues to the next verification step without encountering errors or additional prompts. Both light and dark mode previews are included so teams can validate visual consistency across themes.

---

Best Practices

Recommended guidelines for designing and implementing the Data Sharing Consent experience.

✅ Do

• Clearly explain what data will be collected, processed, or shared.
• Use concise, easy-to-understand language that avoids legal jargon whenever possible.
• Make consent actions explicit and intentional.
• Ensure users can review the full consent information before making a decision.
• Clearly indicate when consent is required to continue the verification process.
• Provide accessible links to privacy policies or additional information when applicable.
• Ensure consent records are captured and stored accurately.

❌ Don’t

• Don’t pre-select consent checkboxes or assume user agreement.
• Don’t hide important information behind unclear links or expandable sections.
• Don’t use confusing, ambiguous, or overly technical language.
• Don’t make acceptance appear mandatory unless required by the verification flow.
• Don’t rely solely on color to communicate consent status or validation.
• Don’t allow users to continue before providing the required authorization.
• Don’t omit information about how user data will be used, shared, or protected.