Smile Identity
Search…
Welcome!
GETTING STARTED
Signing Up
Choose a Product
Choose an Integration Option
Run Your First Test Job
Complete Your KYC
Fund Your Wallet
Go Live!
Pricing
SUPPORTED ID TYPES & DOCUMENTS
For Individuals (KYC)
For Businesses (KYB)
PRODUCTS
Basic KYC
Enhanced KYC
Biometric KYC
SmartSelfie™ Authentication
Document Verification
Integration Options
Mobile
Web / Mobile Web
Server to Server
Rest API
FURTHER READING
Job Status
KYC Receipts
Compare User Information
Securing Your Account with Two-Factor Authentication (2FA)
Troubleshooting
FAQs
How do I setup a Callback?
What are the image types I can upload to Smile ID?
What are Top-Level Keys?
How to re-enroll, deactivate or block a user?
Is there an API I can query to check the status of an ID authority?
How can I look up a specific user's data?
Why is my Web API job taking so long?
What Happens Under The Hood?
Is there an API I can use to monitor my wallet balance?
Why aren't Kenyan ID's returning images for some IDs queried?
What are partner_params?
How do Job Types map to the new Product Names?
What are our support hours?
Selfie Best Practices
What are Confidence Values?
How do I integrate Smile ID in other countries or query other id types?
Why are some of my bank verification requests returning ID authority unavailable?
Guide to the User Consent Screen
What is code 2302?
Add or Remove Team Members
Powered By GitBook
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 Identity 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 Identity gathers consent through these five steps:
  1. 1.
    States upfront that you want to access the user’s personal information
  2. 2.
    Explains the purpose for processing that data
  3. 3.
    Provides a link to your privacy policy should the user want to learn more
  4. 4.
    For the avoidance of doubt, restates explicitly what the user is consent to by clicking “allow”
  5. 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 Identity 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:
  1. 1.
    Your logo, so it’s immediately clear to the user who they are consenting to
  2. 2.
    Your name: either your product name or company name
  3. 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. 4.
    A link to your privacy policy should the user want to learn more
Previous
Why are some of my bank verification requests returning ID authority unavailable?
Next
What is code 2302?
Last modified 4mo ago
Copy link
On this page
What is user consent?
What is a consent screen?
How do I get started?