---
title: "User Consent for PII Data"
url: "https://developer.incode.com/concepts-and-architecture/user-consent-considerations/"
section: "concepts-and-architecture"
version: "v1.1"
status: "live"
---
# User Consent for PII Data

Businesses must collect customer consent and comply with all regional laws and regulations. Incode gives you the tools to collect and manage consent for customers in all regions, including GDPR-regulated countries. This is a general guide. For the full requirements on which types of consent you must collect and how to collect them, review your Master Service Agreement (MSA). Then contact customer support.

## Types of Consent

There are two primary types of consent that Incode requires: 

* **Privacy Consent**: This is also commonly referred to as User Consent. Collection is required for all customers.
* **Machine Learning Consent**: This consent stipulates that Incode has gathered the informed consent necessary to anonymize collected user data for the purpose of improving our machine learning models.

## Collecting Consent

There are two primary methods for gathering the necessary consent and submitting it to Incode so that it can be stored with a user's identity. Please see your MSA for additional details.

* **Dashboard**: Customers can select the `User Consent` module. 
  * If you have your own custom consent, you can append Incode's privacy consent to your custom consent so that they are collected simultaneously. In the details of the `User Consent` module, input the title and the content of the privacy consent in the appropriate text boxes and save the flow.
* **API**: If consent is collected prior to performing an onboarding, the collected consent (which must include the required Incode consent) can be uploaded to a session via the API. To upload a consent object to an onboarding session, see the <Anchor label="Add User Consent endpoint" target="_blank" href="https://developer.incode.com/reference/adduserconsent">Add User Consent endpoint</Anchor>.

For custom integrations using our SDKs or a completely whitelabeled app that only uses our API, the above consent policies need to be collected and sent to Incode. Most of our SDKs contain built-in modules; however, if an SDK does not have a built-in module, you can collect the consent via a custom screen and use our API to send the consent to Incode.

## Local Laws and Regulations

While Incode provides tools to assist with compliance of local laws and regulations, it is the responsibility of every business to seek legal council and ensure that all local, state, and federal laws are upheld.