- Product Introduction
- Purchase Guide
- Integration Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Liveness Detection and Face Comparison (Pure API) APIs
- DetectAIFakeFaces (Pure API) APIs
- Liveness Detection and Face Comparison (App SDK) APIs
- eKYC and Liveness Detection and Face Comparison (Mobile HTML5) APIs
- eKYC (App SDK) APIs
- ID Verification (Pure API) APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Contact Us
- Glossary
- eKYC Policy
- Product Introduction
- Purchase Guide
- Integration Guide
- API Documentation
- History
- Introduction
- API Category
- Making API Requests
- Liveness Detection and Face Comparison (Pure API) APIs
- DetectAIFakeFaces (Pure API) APIs
- Liveness Detection and Face Comparison (App SDK) APIs
- eKYC and Liveness Detection and Face Comparison (Mobile HTML5) APIs
- eKYC (App SDK) APIs
- ID Verification (Pure API) APIs
- Other APIs
- Data Types
- Error Codes
- FAQs
- Contact Us
- Glossary
- eKYC Policy
1.Background
This Module applies if you use the eKYC Solution Feature (“Feature”). This Module is incorporated into the Data Privacy and Security Agreement located at “DPSA”. Terms used but not defined in this Module shall have the meaning given to them in the DPSA. In the event of any conflict between the DPSA and this Module, this Module shall apply to the extent of the inconsistency.
2.PROCESSING
We will process the following data in connection with the Feature:
Personal Information | Use |
Reflective Liveness Compare (RLC) feature | |
Face images and videos of your end users, and returned results (such as results of liveness compare, liveness compare (SAAS) optimal screenshot of end users, original video, algorithm packet with preliminary processing results, description, sim, bestFrameBase64, RequestId, ChargeCount, CardVerifyResults, CompareResults, Extra) | We only process this data for the purposes of providing the Feature to you, including user registration and account security verification.
Please note that this data is integrated with the Cloud Object Storage feature for this purpose.
The Feature will not further process the face images and videos once the liveness detection and identity verification is complete. |
ID OCR feature | |
Images and videos of your end users’ official identity (ID) documents, and returned results (such as original photo or video of ID, face image of ID, information extracted from the ID requested by you (including the end user’s ID number, name, gender, valid duration) | We only process this data for the purposes of providing the Feature to you, including user registration and account security verification.
Please note that this data is integrated with the Cloud Object Storage feature for this purpose.
The Feature will not further process the images and videos of the official identity documents once the identity verification is complete. |
ID verification/ document authentication feature | |
Surname, facial images, determination/ outcome (success/ failure), assessment completion results, identification documentation number, birthday, gender, contact details (including address), card issue date, expiry date, region | We use this information for the purpose of providing the Feature to you, including identity verification and document authentication.
Please note that this data is stored and backed up in the TencentDB for Redis service (Redis), save for facial images which will be stored and backed up in the Tencent Cloud Object Storage service (COS). |
AML/ KYC feature | |
AML & KYC Data (where applicable): version, information input by you for compliance with your local regulatory requirements (region, country, first name, last name, date of birth, middle name, identification number) ,operation and maintenance logs , risk type and info (upon inputting first and last name, DOB), outputs from AML API (name source, value) | We use this information for the purpose of providing the Feature to you, including assisting you in complying with local regulatory requirements (eg. improving the monitoring of customer transactions, improving risk management capabilities, watch list screening, transaction monitoring and customer risk ratings).
Please note that this data is stored and backed up using Redis and COS feature. |
3.service region
As specified in the DPSA.
4.SUB-Processors
As specified in the DPSA.
5.data retention
We will store personal data processed in connection with the Feature as follows:
Personal Information | Retention Policy |
Face images and videos of your end users, and returned results | eKYC API Interface: Not stored. eKYC SDK Interface: Stored in COS for up to 7 days. eKYC H5 Interface: Stored in Redis for 10 days, and stored in COS for up to 7 days. |
Images and videos of your end users’ official identity (ID) documents, and returned results | eKYC API Interface: Not stored.
eKYC SDK Interface: Stored in COS for up to 7 days.
eKYC H5 Interface: Stored in Redis for 10 days, and stored in COS for up to 7 days. |
ID Verification Data | Automatically deletion in Redis and/or COS after 30 days. |
AML & KYC Data | Stored in Redis and/or COS: For up to 14 days. Operation and maintenance logs will be stored up for 2 years. |
6.special conditions
You must ensure that this Feature is only used by end users who are of at least the minimum age at which an individual can consent to the processing of their personal data or that parental consent is obtained for individuals under the minimum age. This may be different depending on the jurisdiction in which an end user is located.
You represent, warrant and undertake that you shall obtain and maintain all necessary consents from end users in respect of the processing of their personal data (such as their face images and videos) in respect of the Feature, in accordance with applicable laws and so as to enable us to comply with applicable laws. To the extent your end users do not consent to such processing, please do not continue with your use of the Feature. You also agree that you will indemnify and hold Tencent harmless from and against all claims, liabilities, costs, expenses, loss or damage (including consequential losses, loss of profit and loss of reputation and all interest, penalties and legal and other professional costs and expenses) incurred by Tencent arising directly or indirectly from a breach of this requirement.
You acknowledge, understand and agree that (i) we do not make any representation or warranty or give any undertaking that this Feature will be in compliance with any applicable laws or regulations, and (ii) any reliance on or use of this Feature is at your sole risk.
Yes
No
Was this page helpful?