Contact
Questions, feedback, or partnership ideas? We’d love to hear from you.
The fastest way to reach us is by email: everydayroyalties@gmail.com
What to include
- Your question or issue (screenshots help)
- Device and browser (e.g., iPhone Safari, Windows Chrome)
- The page or feature where you noticed a problem (URL or section name)
Response time
We typically reply within 1–2 business days.
Optional contact form
Note: This form opens your email client to send the message. If it doesn’t work on your device, email us directly.
What We Can Help With
We cannot offer formal acoustic consulting or legal advice, but we do pay attention to patterns in the questions people send. If many people struggle with the same concept—such as combining sources or understanding exposure tables—we often turn that into a clearer guide or example on the site.
When you reach out, it helps to describe your environment in simple terms: the type of space, distance to the main source, rough reading range, and what you are hoping to decide. That context makes it easier for us to point you toward the most relevant articles on the site.
Response Times and Boundaries
We cannot promise individual replies to every message, especially when volumes are high. When we do respond, replies are meant as general pointers, not personalized engineering advice. If you require detailed analysis or official reports, you may need to work with an acoustics professional in your area.
Even when we cannot respond directly, your feedback still matters. Recurring questions influence which topics we cover next and how we explain complex ideas.
Information We Recommend Leaving Out
To protect your privacy, avoid sending full addresses, detailed schedules, or recordings of other people's conversations when you describe a sound issue. General descriptions—such as the type of building, approximate room size, and time of day—are usually enough to point you toward relevant resources.
Suggesting Topics You Would Like to See Covered
If there is a specific scenario you wish we explained—a type of venue, a home layout, or a work pattern—you can mention it briefly in your message. While we cannot promise individual guidance, we do use these suggestions when choosing which articles or examples to develop next.
Common Questions
Is the microphone audio sent to any server?
No. All audio processing happens locally in your browser using the Web Audio API. No audio data, dB readings, or measurement history is transmitted to any server. The microphone permission is only active while the meter is running — you can revoke it any time in your browser settings.
How accurate is a browser microphone meter vs a dedicated instrument?
Browser-based meters are accurate to approximately ±2–5 dB for relative comparisons — useful for identifying loud sources and before/after comparisons. For OSHA compliance, legal noise disputes, or professional hearing conservation programs, a certified Type 1 or Type 2 sound level meter with calibration records is required.
What browsers and devices support the meter?
The meter works on any modern browser supporting the Web Audio API: Chrome 47+, Firefox 44+, Edge 79+, Safari 14.1+. iOS Safari requires a tap to start the microphone due to Apple's autoplay policy. If the meter doesn't start, check that your browser has microphone permission enabled for this site in your device settings.
How does the calibration offset work?
The calibration offset shifts all readings by a fixed dB value to account for your microphone's sensitivity variance. To find your offset, compare your reading against a known-level source or a reference meter at the same position, then enter the difference. This doesn't make the meter laboratory-accurate but meaningfully improves consistency for repeated comparisons on the same device.
How do I report a bug or request a feature?
Email everydayroyalties@gmail.com with "Bug Report" or "Feature Request" in the subject. For bugs, include your browser, device, OS, and what you expected vs what happened. For feature requests, describe the measurement task you're trying to accomplish. Most current features — calibration offset, CSV export, A/C/Z weighting — came from user requests.