Service Specifications
This section summarizes the service specifications of AmiVoice API.
Security and Compliance
Data Center Location and Data Processing
In this service, speech recognition processing and data storage are performed in AWS data centers within Japan. Data will not be transferred, processed, or stored on servers outside of Japan.
Standard Specifications and Third-Party Certifications
This service is operated under a management system based on the following standard specifications and third-party certifications:
- Information Security Management System (ISMS): ISO/IEC 27001 certified (Certification number: IS 816102)
- PrivacyMark: Certified (Registration number: 10820562(11))
- AWS Certified: AWS Certified Software (Passed AWS Foundational Technical Review)
Handling of Voice and Speech Recognition Result Data by Interface
Voice data received for processing speech recognition requests and speech recognition result data are handled differently for each interface as follows. Please also see "Logging Options and Data Provision".
| Interface | Data Location and Processing in Speech Recognition | Retention Period (*1) |
|---|---|---|
| Synchronous HTTP / WebSocket | Processed only in server memory | Immediately deleted upon completion of speech recognition processing |
| Asynchronous HTTP | Temporarily stored on encrypted disk and processed in a distributed manner | Deleted after speech recognition processing is completed (*2) |
- *1 In case of "No logging". For "Logging", please see "In case of logging" in the next section.
- *2 In the case of Asynchronous HTTP, the recognition results (text) are retained in an encrypted DB for 7 days and then automatically deleted. The recognition results stored in the DB can only be retrieved by the authenticated user.
Handling of User Dictionary Data
There are two methods for registering user dictionaries, and the data is handled as follows for each method. Please also see "Logging Options and Data Provision".
| Method | Request Parameter | Overview | Storage Location |
|---|---|---|---|
| Specified for each request | profileWords | Directly specify word data with the profileWords parameter at the time of request and perform speech recognition processing. | Not saved |
| Specifying a pre-registered profile | profileId | Save to a profile in advance using the user dictionary registration API or MyPage. Specify the profile with the profileId parameter at the time of request and perform speech recognition processing. | Encrypted storage |
Note that user dictionary data is not used for learning at all.
Logging Options and Data Provision
You can choose whether to provide data by setting the logging option when making a speech recognition request.
In case of no logging
It is not used for learning at all, and voice data and speech recognition result text are not recorded on the speech recognition server. Also, speech recognition results and user dictionary information set in the request parameter profileWords are not recorded in the operation log of the speech recognition server.
In case of logging
A discounted price will be applied if you agree to provide data.
- If logging is specified, after the speech recognition processing is completed, the voice data and speech recognition result data are copied to a dedicated encrypted storage.
- We may use the voice data and speech recognition result data for research and development of our products and services, and for quality improvement. In principle, data used for learning for quality improvement will not be deleted, while data not used for learning will be retained for a maximum of 3 years and then appropriately deleted according to our regulations.
- Speech recognition result information and user dictionary information set in
profileWordsare recorded in the operation log of the speech recognition server. These may be checked for troubleshooting and operation purposes.
Please also see Article 7 (Speech Recognition) of the Terms of Service.
Related Resources
For detailed regulations and related information, please also see the following pages: