[Question] Customizing voice display names for Gemini 2.5 Flash TTS in B2C product

Gemini API
, ,
1

I am currently developing a B2C application using the Gemini 2.5 Flash TTS API.

The current voice identifiers (such as Enceladus, Iapetus, etc.) are a bit difficult for our end-users to remember or pronounce. Therefore, we would like to use custom, more friendly names for these voices in our app’s user interface (e.g., “Sunny,” “Warm Storyteller,” etc.), while keeping the original identifiers for the backend API calls.

I would like to clarify:

  1. Are there any terms of service or branding guidelines that prohibit renaming these voices for the end-user UI?

  2. Do we need to disclose the original Google-provided voice names anywhere in the application?

I want to ensure our implementation is fully compliant with Google’s policies. Any guidance or links to relevant documentation would be greatly appreciated.

Best regards,