Privacy Policy

1. Audio and microphone access

Your browser requests microphone permission when you choose to record. You can also choose an audio file to upload. Recording and conversion happen in your browser; when you select Search, a short audio sample is sent to our server and a recognition provider. Recognition is not performed entirely on your device.

Audio may contain your voice, background conversations, or other personal information. Please avoid sensitive recordings and obtain permission from others before recording them. You can revoke microphone permission in your browser settings.

2. Information we process and why

• Audio samples and recognition results, to identify music and show possible matches.
• Technical and usage information, such as IP address, browser, device, pages visited, interactions and error information, to operate, secure and improve the service.
• Your email address and message contents when you contact support, to respond to your request.

Our application does not use submitted audio to train a recognition model. Recognition providers process the audio under their own terms and privacy practices.

3. Recognition and hosting providers

When enabled, humming searches are sent to ACRCloud. Original-recording searches use AudioTag and may fall back to AudD when that provider is enabled. A fallback can send the same sample to more than one provider. Our hosting and network providers also process information needed to deliver and protect the website.

We do not create a permanent audio library in our application. Audio is transmitted for recognition, but third-party processing and retention follow each provider’s policies; we cannot promise that providers immediately delete every sample. Their services may process data in countries other than yours.

4. Analytics, advertising and cookies

The site includes Google Analytics, Microsoft Clarity and Google AdSense. These services may use cookies, identifiers and similar technologies to collect device and browsing information. Google Analytics helps measure site usage. Microsoft Clarity provides interaction analytics, heatmaps and session playback. We do not deliberately send audio files to these analytics services.

Google and other advertising vendors may place or read cookies, use web beacons and process IP addresses to deliver and measure ads. Google advertising cookies can enable ads based on visits to this and other websites. Ad personalization depends on your settings and applicable consent requirements.

Read how Google uses information from partner sites and the Microsoft Privacy Statement. Manage personalized Google ads in My Ad Center, or learn about participating vendors’ opt-out choices at YourAdChoices. Browser settings can block or delete cookies; this does not necessarily stop all data processing.

External badges and links may also connect your browser to other websites. Their privacy policies apply when you use their services.

5. Retention and security

Our recognition handler processes audio to fulfill the request without saving it to an application audio archive. Hosting logs, analytics records and support correspondence have separate retention settings and may remain after a request completes. We retain information as needed for the stated purposes, security and applicable legal obligations; provider retention may differ.

We use HTTPS for website and recognition-provider connections and keep API credentials on the server. No transmission or storage system is completely secure.

6. Your choices and privacy requests

You can browse without submitting audio, stop recording, revoke microphone permission, and adjust browser and advertising settings. Depending on applicable law, you may have rights to access, correct, delete or obtain a copy of personal information, restrict or object to processing, or withdraw consent where processing relies on it.

Send requests to support@humtosearch.app. Describe your request without attaching sensitive audio. We may need information to verify and locate relevant records. You may also contact your local data protection authority where applicable.

7. Children and policy updates

The service is not directed to children under 13. If you believe a child has provided personal information, contact us so we can investigate and address it. We will publish policy changes on this page and update the date above.

For service rules, see our Terms of Service.