PitchDetector.com uses browser-based audio features that may require access to your microphone or an audio file. Because audio input can feel sensitive, we believe users should be able to understand when access is requested, how the tool uses the input, what information is separate from audio analysis, and what controls remain in the user’s hands.
This page explains the technical handling of audio-related features on PitchDetector.com in plain language.
For broader information about cookies, analytics, contact information, legal privacy rights, and other website data, please read our Privacy Policy.
How Microphone Access Works
PitchDetector.com does not receive microphone access automatically when you visit the site.
When you start a feature that requires live audio, your browser asks you to grant microphone permission. You can allow or deny that request.
Modern browsers control this permission system. PitchDetector.com cannot bypass the browser’s permission prompt.
The official MDN documentation for getUserMedia() explains how websites request access to microphone and camera devices and how browsers require user permission before providing the media stream.
Depending on your browser and settings, your decision may apply only to the current session or may be remembered for future visits.
If you previously allowed microphone access, you can usually review or change that permission through your browser’s site settings.
How Audio Is Used for Pitch Analysis
The purpose of microphone access on our pitch-related tools is to provide audio samples that can be analyzed to estimate information such as:
- detected pitch;
- musical note;
- frequency in hertz;
- tuning deviation;
- signal stability or confidence where supported.
For browser-based pitch analysis, audio can be processed using web audio technologies running on the user’s device.
The Web Audio API provides browser capabilities for processing, analyzing, and working with audio in real time.
Using browser audio technology does not, by itself, prove how a particular website handles every type of data. For that reason, we aim to describe PitchDetector.com’s own implementation separately rather than treating the technology itself as a privacy guarantee.
For information about the mathematical and signal-processing side of pitch analysis, see our Methodology page.
Microphone Audio and Website Data Are Different Things
It is important to separate audio used for pitch analysis from the ordinary technical data involved in operating a website.
Even when pitch-related audio is processed within the browser, normal website operation may still involve network requests associated with things such as:
- loading page resources;
- security and hosting infrastructure;
- analytics;
- advertising;
- consent tools;
- error logging;
- affiliate links;
- contact forms;
- other third-party services.
For that reason, we do not describe PitchDetector.com with blanket statements such as “no data ever leaves your browser” or “zero data collection.”
Those statements can incorrectly combine several unrelated types of data.
Our goal is to describe each category accurately.
Audio Files
Some PitchDetector.com tools may allow users to select an audio file for analysis.
File-based workflows are different from live microphone input, and exact behavior can vary between tools.
A tool may use browser capabilities to decode or analyze a selected file, while another type of feature may require different handling.
Because of that, users should rely on the instructions and privacy information provided for the specific tool they are using rather than assuming that every audio feature works identically.
We do not use this page to make universal claims about every possible audio-file format or browser combination.
For more information about file-based pitch analysis, see our guide on detecting pitch in MP3, WAV, and M4A files.
What We Mean by “Local Processing”
When we describe a supported audio-analysis function as local or browser-based, we mean the relevant analysis is performed by code running in the browser rather than requiring a remote server to calculate the pitch.
That does not mean the browser stops all network activity while the page is open.
It also does not mean that unrelated website systems such as analytics, advertisements, hosting infrastructure, or contact services cease to operate.
This distinction matters because:
local pitch analysis and overall website privacy are not the same claim.
Broader website data practices are documented in our Privacy Policy.
Stopping Microphone Use
When a tool provides a Stop control, users should use it when they have finished a microphone-based session.
Closing the page or browser tab also ends the page’s active use of the microphone stream.
However, ending an active microphone session is not necessarily the same as removing a previously saved browser permission.
Some browsers remember that you previously allowed microphone access.
If you want to change or revoke that permission, use your browser’s site-permission controls.
Browsers and operating systems may also show a microphone indicator while the device is actively being used.
The appearance and location of these indicators vary between platforms.
What We Do Not Mean by “Secure”
Security is not an absolute state.
No website can responsibly promise that online systems are completely risk-free, impossible to attack, or guaranteed never to experience a security problem.
When we discuss security, we mean that PitchDetector.com aims to use reasonable technical measures appropriate to the website and its browser-based tools.
These measures may include technologies such as HTTPS and security protections provided by our hosting or infrastructure providers.
HTTPS helps protect information transmitted between your browser and the website from being read or altered in transit.
It should not be confused with a guarantee that every type of information is stored locally or that no third-party services exist.
Contact Information Is Separate From Pitch Audio
If you voluntarily email us or submit information through a contact mechanism, that information is different from audio used by the pitch detector.
For example, an email may contain:
- your email address;
- your name, if provided;
- the contents of your message;
- screenshots or technical details you choose to send.
That information may need to be transmitted and retained so we can respond to your request.
It should therefore never be described by a sitewide statement such as “we store no personal information.”
Our Privacy Policy explains broader data practices in more detail.
Tool Preferences and Browser Storage
Some web tools may use browser-based storage for non-audio preferences or settings.
Examples could include:
- tuning reference;
- notation preference;
- sensitivity;
- interface choices.
Where such storage is used, it should not be confused with raw microphone recording.
Browser storage, cookies, analytics data, microphone audio, and submitted contact information are separate categories and may have different handling.
The exact website technologies in use can change over time, so our Privacy Policy should be treated as the primary source for broader data disclosures.
Third-Party Services
PitchDetector.com may use third-party services that help us operate, secure, analyze, or support the site.
Depending on the current website configuration, these services may include:
- hosting or CDN providers;
- analytics platforms;
- advertising services;
- consent-management tools;
- affiliate systems;
- email providers.
Their operation is separate from the mathematical process used to estimate pitch from audio.
Where third-party services process personal or device-related information, those practices should be addressed through our Privacy Policy and relevant disclosures.
We avoid claiming that PitchDetector.com has “no tracking” or “no third-party processing” unless the live site’s configuration actually supports that claim.
Privacy and Security by Scope
A useful way to understand PitchDetector.com is to separate the site into three layers:
Audio analysis
This covers the audio signal used to estimate pitch, notes, frequency, or related results.
Website operation
This covers ordinary website activity such as page delivery, analytics, advertising, cookies, and server requests.
Information you provide voluntarily
This includes information you send through email, feedback, support requests, or other contact channels.
These layers should not be described as though they are the same thing.
That distinction helps us provide clearer and more accurate privacy information.
Our Approach to Security Claims
We avoid claims such as:
- “100% private”;
- “completely secure”;
- “zero data exposure”;
- “nothing ever leaves your device”;
- “no tracking of any kind.”
Absolute statements can be misleading when they combine multiple technologies and data categories.
Instead, we prefer specific statements that can be checked against the site’s current implementation.
That approach is consistent with the transparency standards described in our Authors & Editorial Standards and About PitchDetector.com pages.
If Your Microphone Is Not Working
Security and permission settings are common causes of microphone problems.
If the detector cannot access your microphone, check:
- whether microphone permission was denied;
- whether another application is using the microphone;
- whether the correct input device is selected;
- browser site-permission settings;
- operating-system microphone permissions;
- whether the page is running in a supported browser environment.
Our Troubleshooting guide provides additional help for microphone access, noisy signals, unstable readings, and other common issues.
Questions, Corrections, or Privacy Concerns
If you believe something on this page does not match the actual behavior of a PitchDetector.com tool, we want to know.
You can contact us about:
- microphone behavior;
- unexpected network activity;
- audio handling;
- privacy concerns;
- security concerns;
- inaccurate documentation;
- outdated information.
Email us at support@pitchdetector.com or visit our Contact Us page.
For broader information about personal data, cookies, analytics, and privacy rights, see our Privacy Policy.
Last reviewed: August 19, 2026