- Product Introduction
- Purchase Guide
- Getting Started
- Server APIs
- History
- Introduction
- API Category
- Making API Requests
- Industry-Specific Document OCR APIs
- Invoice and Ticket OCR APIs
- Vehicle Scene OCR APIs
- Smart Structured Information OCR APIs
- Card and Document OCR APIs
- MainlandIDCardOCR
- HmtPermitOCR
- MainlandPermitOCR
- HmtResidentPermitOCR
- ThaiIDCardOCR
- BankCardOCR
- TableOCR
- HKIDCardOCR
- InternationalDPassportOCR
- MLIDCardOCR
- PhilippinesDrivingLicenseOCR
- PhilippinesSssIDOCR
- PhilippinesTinIDOCR
- PhilippinesVoteIDOCR
- PhilippinesUMIDOCR
- KoreanIDCardOCR
- KoreanDrivingLicenseOCR
- IndonesiaIDCardOCR
- Data Types
- Error Codes
- Service Agreement
- OCR Policy
- Product Introduction
- Purchase Guide
- Getting Started
- Server APIs
- History
- Introduction
- API Category
- Making API Requests
- Industry-Specific Document OCR APIs
- Invoice and Ticket OCR APIs
- Vehicle Scene OCR APIs
- Smart Structured Information OCR APIs
- Card and Document OCR APIs
- MainlandIDCardOCR
- HmtPermitOCR
- MainlandPermitOCR
- HmtResidentPermitOCR
- ThaiIDCardOCR
- BankCardOCR
- TableOCR
- HKIDCardOCR
- InternationalDPassportOCR
- MLIDCardOCR
- PhilippinesDrivingLicenseOCR
- PhilippinesSssIDOCR
- PhilippinesTinIDOCR
- PhilippinesVoteIDOCR
- PhilippinesUMIDOCR
- KoreanIDCardOCR
- KoreanDrivingLicenseOCR
- IndonesiaIDCardOCR
- Data Types
- Error Codes
- Service Agreement
- OCR Policy
1.Introduction
This Module applies if you use the Optical Character Recognition Ffeature (“Feature”). This Module is incorporated into the privacy policy located at “Privacy Policy”. Terms used but not defined in this Module shall have the meaning given to them in the Privacy Policy. In the event of any conflict between the Privacy Policy and this Module, this Module shall apply to the extent of the inconsistency.
2.Controllership
The controller of the personal information described in this Module is as specified in the Privacy Policy.
3.Availability
This Feature is available to users globally but primarily intended for users located in the same country/region as the selected service region for optimal performance.
4.How We Use Personal Information
We will use the information in the following ways and in accordance with the following legal bases:
| Personal Information | Use | Legal Basis |
|---|---|---|
| Monitoring Data: AppID, interface name, result, callID, start and end call time, region, fee, interface call volume | We use this information for billing and metering purposes. Please note that this data is stored and backed up in the TencentDB for MySQL feature. |
We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
| Operation and Maintenance Log: APPID, Call ID, timestamp, single step debugging information, desensitization request and response | We use this information to ensure the Service functions as required and to analyze the reasons for errors or failures and troubleshoot such problems. Please note that this data is stored and backed up in the Elasticsearch Service feature. |
We process this information as it is necessary for us to perform our contract with you to provide the Feature. |
5.How We Store and Share Personal Information
As specified in the Privacy Policy.
6.Data Retention
We will retain personal information in accordance with the following:
| Personal Information | Retention Policy |
|---|---|
| Monitoring Data | Stored for 2 years. |
| Operation and Maintenance Log | Stored for 3 months. |
Yes
No
Was this page helpful?