Speech to text and data logging: V1 vs V2

[pronto1]

Google Cloud Speech-to-text API v1 had different prices depending whether one would opt-in to data logging. With the v2 API, there is no mention of data logging anywhere. Does this mean Google forces data logging on v2 ?

[Poala_Tenorio]

Google Cloud Speech-to-Text API pricing was primarily based on the number of characters processed. The pricing structure may have included variations determined by the following factors:

• The number of channels in the audio being recognized.
• The length and amount of audio you send.
• The recognition model you are using.
• The batch method you are using.
• The API version you are using.

The Speech-to-Text V2 API offers a dynamic batch feature that handles audio with reduced priority. Enabling dynamic batch processing results in billing at a discounted rate.

As quoted from the documentation:

The difference between the v1 and v2 versions of the Speech-to-Text API in the definition of RecognitionConfig message is the addition of the AutoDetectDecodingConfig message, which automatically detects the audio specifications.

---

[pronto1]

Thanks Poala. However this does not really answer the question. 

With api V1, pricing could be influenced by accepting data logging to be performed by Google or not. Price was higher without data logging.

With api V2 there is no mention of data logging influencing the API usage pricing, but we would like to be 100% sure Google does not perform data logging by default.