Why I Built CVoice
I once saw a game-related talent marketplace recruiting people with different types of voices, which made me wonder how my own voice would be described. I looked for existing tests, only to find that some returned nearly identical results for different recordings, some took a long time, some required payment, and others required downloading an app first.
So I decided to start with a small tool that runs directly in the browser and returns a result within seconds. At first I shared the link in only two small groups, but the unexpected growth in traffic pushed me to seriously address recording compatibility, queues, algorithm explanations, privacy notices, and server capacity. CVoice gradually grew from a single page into the family it is today.
Who Maintains This Project
The CVoice family is independently designed and developed by Chione. Content, frontend, server-side systems, audio algorithms, and deployment records are maintained within the same project. Some reports may use AI to help organize wording, but core values, label selection, and permission boundaries are controlled by deterministic code.
I am not using some mysterious model to “understand” users by listening to them. I am continuously solving real engineering problems: different Android recording formats, browser microphone quality, whistle misclassification, borderline timbres, task queues, cross-network access, static deployment, and user feedback. The articles on this portal are public write-ups of those experiences.
Principles We Follow
- Entertainment labels must not be presented as identity, medical, or professional assessments.
- For real-time features that can run locally in the browser, continuous audio streaming is avoided whenever possible.
- Recording processing and anonymous statistics must be explained separately.
- Complex algorithms are no excuse for overstating accuracy.
- Ads, sponsorships, and paid benefits must not affect analysis results.
- Material changes go into the development log, and known limitations are not hidden.
How We Keep the Site Running
The site has costs for domains, networking, storage, compute nodes, and maintenance time. Support through Afdian is entirely voluntary; some apps may offer a clearly stated number of priority uses or additional experiences, but they will never sell “better-looking” test results.
Google ads are intended to help cover the cost of public content and free tools. Ads should be clearly separated from navigation, test buttons, and download links, and they do not determine what the portal publishes or what the algorithms output.
Feedback & Contact
You can report feature issues, browser compatibility problems, incorrect labels, and content suggestions through in-app feedback, or join QQ group 1087037352. To protect your privacy, do not send full recordings, administrator tokens, task credentials, or other sensitive information in public group chats.