> For the complete documentation index, see [llms.txt](https://legacy-docs.usesmileid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legacy-docs.usesmileid.com/further-reading/faqs/guide-to-the-user-consent-screen.md).

# Guide to the user consent screen

## What is user consent?

Consent is fundamental to user trust in the internet economy and for compliance with data protection laws around the world that are strongly influenced by the EU’s General Data Protection Regulation (GDPR). This requires that data controllers and processors obtain explicit consent from end users before collecting and processing of personal data can take place.

## What is a consent screen?

To foster trust and ensure compliance, Smile ID has built a consent screen: a step in your onboarding UX that is embedded in our mobile and hosted web SDKs. The screen lays out the data that will be processed, explains for what purpose, and explicitly asks the user if she consents to sharing that data.

Specifically, Smile ID gathers consent through these five steps:

![](/files/VtaHJP2cNbN5YfZDLuKt)

1. States upfront that you want to access the user’s personal information
2. Explains the purpose for processing that data
3. Provides a link to your privacy policy should the user want to learn more
4. For the avoidance of doubt, restates explicitly what the user is consent to by clicking “allow”
5. Offers an “allow” button: by calling to action, this button enables the user to give her consent and sends her to the next step of her onboarding journey

## How do I get started?

Smile ID builds the consent screen for you: all you must do is integrate any of our mobile SDKs or hosted web integration to have it available, comply with data privacy, and strengthen trust!

That said, there is some information we require to ensure the screen is tailor-made for you.

Specifically:

![](/files/3oU3BEG1gOrTKN11YzdD)

1. **Your logo,** so it’s immediately clear to the user who they are consenting to
2. **Your name:** either your product name or company name
3. **The identity type** that returns the information the user consents for you to access. For example, the passport, BVN, driver’s license or voter ID
4. **A link to your privacy policy** should the user want to learn more


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://legacy-docs.usesmileid.com/further-reading/faqs/guide-to-the-user-consent-screen.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.