Contact
Corrections, bug reports and technical questions are all welcome. Here is what to include so the first reply is a useful one.
Before reporting a recording problem
Most reports turn out to be permission issues, which the guides resolve faster than an email exchange can:
- Microphone not working — ordered checks by symptom.
- Microphone permissions — per-browser and per-operating-system detail.
- Microphone test — confirm whether audio reaches the browser at all.
- Browser support — version and feature requirements.
If it is still broken
Include these and the problem is usually identifiable straight away:
- Browser and version
- Found in the About page of your browser's menu
- Operating system
- Windows 11, macOS 15, iOS 18, Android 15 and so on
- Which page
- The URL where it happened
- What you did
- The exact sequence, including which format was selected
- What happened
- Any message shown, and the exact wording
- Console errors
- Open developer tools, Console tab, and copy anything in red
Please do not send audio files. We do not want them, cannot use them, and asking for a recording would undermine the entire premise of the site.
Corrections
Technical documentation goes stale. Browsers change behaviour, permission interfaces get redesigned, and the products described on the comparison pages get updated. If something here is inaccurate, please say so — a pointer to what changed is more valuable than a general note that something is wrong.
Feature requests
Worth hearing, with one standing exception: anything requiring audio to be uploaded will be declined. That includes shareable links, cloud storage, server-side conversion and account sync. Those are not missing features but deliberate absences, and adding any of them would make this a different site.
Security
If you have found a security issue, please report it privately rather than publicly, and give a reasonable window for a fix before disclosure. Reports about the recording pipeline specifically — anything suggesting audio could leave the device — will be treated as the highest priority, since that is the one claim everything else rests on.
Getting in touch
Email is the way. The address is contact@audio-recorder-voice.com.
This is a small project rather than a company with a support desk, so replies are not instant — but technical questions, corrections and bug reports all get read.
- Microphone not workingSolves most reported problems.
- How it worksAnswers most technical questions.
- PrivacyAnswers most data questions.
- AboutWhy the site works the way it does.
Questions
How do I report a bug?
Email contact@audio-recorder-voice.com with your browser and version, operating system, the page URL, what you did, what happened, and any console errors.
Should I send my recording so you can look at it?
Please do not. We do not want your audio, and asking for it would contradict the premise of the site. The details above are enough to diagnose almost anything.
Can you recover a recording I lost?
No. Nothing is stored, so there is nothing to recover. That is the unavoidable cost of never having your audio in the first place.
Will you add cloud storage or sharing links?
No. Both require storing recordings on a server, which is the one thing this site is built not to do.
How do I report a security issue?
Email privately rather than posting publicly, and allow a reasonable window for a fix. Anything suggesting audio could leave the device is treated as highest priority.
How quickly do you reply?
This is a small project rather than a support organisation, so not instantly. Bug reports, corrections and technical questions are all read.