Configure Server URL


“Server URL to record captions” sets the analytics server location that will receive live caption and respond to the extension screen with the analyzed suggestion or results. Set it to your trusted server URL.

Sample server setting

The sample server destination, https://localhost, is proposed as default. However, you will need to update this location value with the one informed by your resource.

Security notice and concerns

Acknowledge the risks and set the your trusted URL when you use the speech recognition and analysis based on the created caption.

Two components of this extension and its associated server appplication send and/or collect your data under the conditions that are outlined in each service. The first component is Speech Recognition part and the second component is analytics part. The first part is fully under the control of online services such as Google Meet、zoom(+ and of browser built-in Speech Recognition. The second part is managed by destination’s proprietary mechanism for the caption data sent from the extension. The machanism can vary based on the service design in terms of its sotrage location and degree of data security.

The first comopnent, Speech Recognition part, will follow the terms and conditions, and privacy statement for the applicable online conferencing services such as Google Meet、zoom(+ It is your discretion and responsibility to consent to the conditions. The second component, analytics part, sends your voice audio data to Google. You will be prompted when you try to turn built-in Speech Recognition. As directed in the prompt, show your consent after you thoroughly read the document in the link. You need to visit the current document, but,as of December 12, 2021, the whitepaper will read:

Privacy whitepaper:
Speech to text
Chrome supports the Web Speech API, a mechanism for converting speech to text on a web page. It uses Google’s servers to perform the conversion. Using the feature sends an audio recording to Google (audio data is not sent directly to the page itself), along with the domain of the website using the API, your default browser language and the language settings of the website. Cookies are not sent along with these requests.

The second component, analytics part, may take different forms and its storage location some of which are listed below as 2-1 to 2-8. Some option may offer comparatively more strict security control. Needless to say, of course, if the location is breached, access restriction to your data can be compromised. You can set server URL and, as a result, change the storage location. (see ”Set URL provided by the service provider” of the URL: This freedom of destination server is intended to protect the right to own learner’s own interaction data.
2-1) send no data and receive no analytics results
2-2) send captions only to  Google spreadsheet
2-3) use public source code and deploy it to your own PC, server, or an Apple
2-4) set a URL that is declared to use public source code
2-5) use proprietary code of your own and deploy it to your environment
2-6) set a URL that is declared to use proprietary code
2-7) deploy an executable file which can be created from the source code for Windows (executable may be created if demand is clearly communicated from many users)
2-8) utilize an educational PDS that offers a strict security (currently not provided, but can be potentially configured if URL destination can be set up)

Storage and associated risks

2-1 is least vulnerable with no benefits. This is a default configuration after the installation. The extension will start to store data only within extension only when you turn on some sort of captions and click “録”. This 2-1 will not send any data to anywhere. However, this option may defeat the purpose of storing and analyzing the interaction and will offer almost no benefits.

2-2 will offer no analytics, but can send caption to Google Spreadsheet. Data will be sent through Google, but the extension will not collect or store. The configuration of this option is highlighted in this page.

2-3 is to deploy to your own PC and captions will be stored only in your PC. GitHub is published at the following repo.

2-4 is to deploy the same code in 2-3 to a server on a VPS or rental server. Data will be stored at the deployed site and will be vulnerable against attacks to the server and can be compromised. Privacy statement for your data has to be confirmed and accepted.

2-5、2-6  is to use proprietary code and the owner may adjust the code to have full access to your caption data.

2-7 is to run executable code on your machine and data may remain within your machine. However, I haven’t provided this option due to the concern over the integrity of the file.

2-8 is to use a private PDS. You need to review the conditions that you have to accept.