Privacy

The short version

• We store your measured vocal range and Vocal ID. That is the product; without it there is nothing to match against.
• We do not store recordings of your voice. Pitch detection runs in your browser and sends up notes and numbers, not audio. Where a feature does upload audio, that feature says so at the point of upload.
• We do not sell your personal information, and we do not share it with advertisers.
• The Partner API and MCP server hold no account data at all. See below.

What we collect

Account. Email address and display name, handled by our authentication provider. A locale so we know whether to speak English or Spanish to you.

Voice data. Your detected lowest and highest notes, derived Vocal ID, voice type, and session results. Pitch analysis happens in your browser; what reaches our servers is the resulting notes and confidence values.

Usage. Songs you save, searches you run, matches you were shown, and outcomes you report. This is what makes recommendations improve rather than repeat.

Technical. Product events recorded with a page or action name, a one-way hash of your IP address, your browser user agent, and a coarse location (city, region, country) derived from your IP. We do not store your IP address itself. It is used in memory to compute that hash and to look up the coarse location, then discarded. The location lookup runs against a database on our own servers, so your IP is never sent to a geolocation vendor either. Event metadata is limited to an allowlist of fields rather than arbitrary capture.

Payment. Handled entirely by Stripe. We receive subscription status and identifiers. We never see or store your card number.

Who processes it

Clerk (authentication), Stripe (payments and subscriptions), Resend (transactional and digest email), Sentry (error monitoring), and Render (hosting). Each receives only what its job requires. Push notifications, if you turn them on, go through your browser’s own push service using a subscription you can revoke at any time.

Partner API and MCP server

Our Partner API (/api/v1/*) and MCP server (/api/mcp) are stateless. Every call is a computation over the vocal range you send plus a read-only lookup against our song catalog. They create no HumMatch account, no hum session, and no saved result, and they write nothing to our database about the request or its contents.

The only thing we retain on that path is the API key record itself: a one-way hash of the key (never the key in plaintext), its visible prefix, and the email and company name supplied when it was issued, so we can contact a partner and enforce rate limits. Requests without an API key are rate limited by IP address held in memory for the length of the limit window and never written to disk.

If you reach HumMatch through an AI assistant, the vocal range you gave that assistant is passed to us to perform the match. We do not receive your conversation, your identity, or anything else from it.

Retention and your choices

Account and voice data are kept while your account is open. Ask us to delete your account and we remove it along with your Vocal ID, saved songs, and session history; aggregate counts that identify nobody may remain. You can unsubscribe from email from any message we send, turn off push notifications in your browser, and re-baseline or replace your Vocal ID at any time from your account.

To request access to or deletion of your data, contact us.

Children

HumMatch is not directed at children under 13, and we do not knowingly collect their personal information.

Changes

If we change what we collect or who processes it, we will update this page. Material changes will be announced in the product rather than made quietly.