Audio
All tones are generated locally with your browser's audio engine. We never access your microphone.
Accounts and data
There are no accounts. We do not collect personal information through the tools.
Privacy scope: local audio is not the same as an offline website
FixMySpeaker.now provides browser-based playback tools and written troubleshooting guides. The audio tools create tones on your device using the browser's Web Audio functionality. They do not need a recording of your surroundings to generate a sine wave, change a frequency, pan between channels, or play a sweep. No account is required to use these tools.
Local generation describes the audio signal path, not every technical part of visiting the website. Your browser still requests pages, scripts, styles, images, and other resources. Website hosting and external resource providers can receive information associated with those requests. It would therefore be misleading to interpret local audio as a promise that nothing leaves your device during a visit.
This explanation distinguishes behavior visible in the application's source from matters that depend on the live deployment or a provider's configuration. It does not claim a particular retention period, legal certification, or absence of every possible tracking technology without verification. If a deployment changes, privacy information should be checked against that deployment rather than inferred from a general statement about Web Audio.
Generated tones are created locally in the browser.
The tools do not require an account or microphone input.
Loading the website still involves network requests.
Provider logging and deployed integrations are separate from tone generation.
How generated audio works
The playback engine uses an oscillator to create a signal, a gain control to adjust its level, and a stereo panner to select its position between left and right. It connects that signal to the browser's audio destination. Depending on your device settings, that destination may be built-in speakers, headphones, Bluetooth equipment, a USB interface, or another selected output.
The tool adjusts signal properties such as frequency, waveform, volume, playback mode, and channel position. A sweep changes frequency over time, while a pulse mode changes the output level in repeated intervals. None of those operations requires listening to the room. The tool produces sound for you to assess; it is not a microphone-based measurement system.
Local generation also does not mean that the application can determine everything about the physical result. The browser cannot infer from these controls alone whether a grille is blocked, an earbud fits correctly, or a loudspeaker is damaged. The absence of recording is a privacy-relevant boundary, but it also limits the conclusions the tool can draw.
A generated signal is sent to the output selected by the device.
Frequency and waveform controls change playback rather than analyze recordings.
Left-right selection uses output panning rather than physical speaker detection.
Listening results are observations, not uploaded measurements or automatic diagnoses.
Microphone access and recording permissions
The current tone-generation implementation does not request microphone input. You do not need to grant microphone permission to run a channel test, a frequency comparison, or a cleaning-oriented playback tool. The tools are not designed to record speech, capture ambient sound, or upload a microphone recording for analysis.
If your browser displays a microphone request while you believe you are using only these playback tools, do not approve it merely to make the test work. Check the requesting address and whether another tab, an embedded browser, an extension, or a different application is involved. An unexpected prompt deserves investigation rather than an assumption that audio playback needs recording permission.
You can review microphone permissions in your browser's site settings and revoke permissions you do not want. The exact location varies by browser and operating system. Changing microphone permission should not be necessary for this site's oscillator-based playback. If a prompt appears connected to a specific page, contact hi@fixmyspeaker.now with the route, browser, and permission type, without sending a recording.
Do not grant microphone access for ordinary tone playback.
Check the address associated with any unexpected permission prompt.
Review or revoke permissions through browser site settings.
Report the prompt's context without sharing private audio.
Accounts, tool settings, and what the interface knows
The tools do not require registration, a profile, or a sign-in. You can choose a frequency, waveform, volume, channel, or timer without creating an account. The current playback component manages those working values as interface state. This is different from an account-based service that stores a personal testing history.
The absence of accounts should not be expanded into a promise that no information can be associated with a visit. A browser request can contain network and technical information regardless of whether you have signed in. Likewise, sending an email voluntarily supplies information that is separate from the controls you use on a tool page.
Browser-managed data is another distinct category. A browser may keep history, cached files, site permissions, or other local information as part of ordinary browsing. Clearing those items can remove local traces or force resources to reload, but it does not automatically remove information held in hosting logs, external service records, or email systems.
No account is needed for the playback tools.
Tool controls are not a personal profile or a recorded diagnostic history.
Browser history and cache are managed separately from audio generation.
Deleting local browser data does not necessarily delete remote records.
Website requests and hosting information
When you open a page, your browser communicates with the infrastructure that serves it. Requests can expose an IP address, requested path, request time, browser-related headers, and other connection information to the systems handling delivery. Depending on browser policy and navigation context, referrer information may also be included. This is ordinary website communication, even when the page's sound is generated locally.
Hosting, content delivery, and security systems may maintain operational logs for purposes such as delivering content, investigating errors, handling abusive traffic, or maintaining availability. The application source alone does not establish the exact fields retained by every infrastructure layer, how those fields are processed, or how long a particular deployment keeps them.
For that reason, this page does not give an invented log-retention schedule or claim that request information is never recorded. Questions about a specific visit or deployment should identify the relevant page and context so the applicable infrastructure can be checked. Avoid putting sensitive information into a URL or search text simply because the audio portion of the tool runs locally.
Page loads and resource requests are separate from generated audio.
Request handling can involve technical connection information.
Exact logging practices depend on the serving infrastructure.
No specific retention period is asserted here without verification.
Google Fonts requests
The site's shared document configuration includes a Google Fonts stylesheet for the Inter and Poppins typefaces. It also includes connection hints for fonts.googleapis.com and fonts.gstatic.com. Where those external resources are loaded, the browser communicates with Google's font-serving infrastructure rather than obtaining every resource solely from this website's own origin.
These requests are for typography, not for uploading the generated audio signal. Nonetheless, an external resource request can make technical request information available to the provider. The exact information transmitted depends on the request, browser behavior, referrer policy, and the provider's implementation. It should not be described as having no privacy implications simply because it is a font.
You may use browser controls or an appropriate content blocker to restrict external font requests. The appearance can change if the browser falls back to system fonts. Blocking a font does not turn the whole website into an offline application, and clearing a local font cache does not establish that a provider has deleted any records it may hold.
Google Fonts is an external resource used by the shared page configuration.
Font delivery is distinct from the local Web Audio signal path.
Blocking external fonts may change typography or layout.
Consult the provider's current information for its own handling practices.
Errors, diagnostics, and deployment-specific integrations
The project includes error-reporting hooks that can pass runtime exception details to reporting facilities when those facilities are present. The reporting wrapper can include an error description, stack information, the current route, and related context. Source code that invokes an optional hook is not, by itself, proof that a particular reporting service is active on every public deployment.
Server-side error handling also includes mechanisms for preserving useful error details in logs. Errors can therefore create information flows that are different from normal audio playback. It would be inaccurate to use the local oscillator implementation as evidence that no diagnostic information can ever be processed.
A reliable statement about a live environment requires checking its configuration and actual requests. This privacy text does not assert that all visits are free of analytics, that every optional integration is active, or that a specific diagnostic retention period applies. If you are investigating an unexpected request, identify the destination and the action that preceded it rather than sending a full unreviewed browser export.
Optional runtime reporting hooks exist in the source.
Their presence does not establish every live deployment's configuration.
Error details and route information can be relevant diagnostic data.
Do not include secrets in URLs, error descriptions, or support attachments.
Email, voluntary disclosures, and external links
If you email hi@fixmyspeaker.now, your message contains the information you choose to send and the addressing information needed for email delivery. Attachments, quoted correspondence, and signatures can add personal information you did not intend to include. Review them before sending. A website bug report rarely needs a serial number, home address, payment record, or private recording.
Email handling is separate from the browser's local tone generation. Mail providers and delivery systems have their own processing arrangements, and this page does not assign them an unverified retention period. If you want to ask about earlier correspondence, identify the relevant message without adding unnecessary identity documents.
Guides may direct you to manufacturer documentation or other external resources. Following an external link brings you into that destination's own technical and privacy environment. A recommendation to read a support page does not mean that FixMySpeaker.now controls the destination's cookies, forms, account requirements, or logging practices.
Share only the details needed to explain your question.
Review screenshots, signatures, attachments, and quoted email threads.
Treat external websites as separate services.
Ask about a specific message or request rather than assuming one policy covers every provider.
Practical privacy choices and questions
You can use these playback tools without providing a name or opening an account. Keep microphone permission disabled if you do not want sites to record audio, check the selected site address, and use browser privacy controls that fit your needs. Private-browsing modes can limit some local history, but they do not make network requests invisible to the systems that receive them.
To investigate website communication, a browser's Network panel can show requested domains and resource types. Read results carefully: an external font request, a failed page resource, and an error-reporting request have different purposes. Developer tools can also display sensitive headers or identifiers, so do not publish an entire capture without reviewing it.
For privacy questions, contact hi@fixmyspeaker.now and explain the activity you want clarified. If you are making a request concerning personal information, state the context and the outcome you are seeking. Applicable rights and available processes depend on the circumstances and jurisdiction; this page does not claim universal regulatory compliance or promise an outcome that has not been verified.
Use the tools without registering or sharing identifying details.
Inspect and manage permissions through your browser.
Distinguish local history controls from remote processing.
Ask specific questions about fonts, hosting, diagnostics, or correspondence.
Do not interpret local audio generation as a guarantee of complete anonymity.