We aim to reply within a few business days. DecibelPro is a small operation, so please allow a little patience — but a message about a failed purchase or a billing problem gets looked at first.
What to include
A reading looks wrong
Tell us the device model, operating system version, and browser, what the meter showed, and what you expected. Device-specific behaviour is the most useful bug report we can get, because the one thing we cannot see from here is your hardware.
A correction to the content
If a figure, a citation, or a noise ordinance detail is wrong, we want to know and we will fix it. A link to the primary source makes it fast. Corrections are recorded in the changelog.
Pro, billing, or a refund
Include the email address you used at checkout so the purchase can be found. Refunds are considered case by case — if Pro did not work as described for you, say so and expect a refund.
Calibration comparison data
If you have access to a calibrated sound level meter and are willing to run a side-by-side comparison, this is the single most valuable thing anyone can send us. The accuracy page describes the protocol that would be most useful.
Before you write
Two questions come up often enough to have their own pages. If you're asking how far a reading can be trusted, the accuracy page gives expected ranges by device type. If you want to know exactly how the number is computed, the methodology page writes out the whole chain. The FAQ covers the rest.
What we can't help with
We can't interpret a measurement as evidence in a dispute, certify a reading, or advise on whether a specific workplace is compliant — all of those need a calibrated instrument and, usually, an occupational hygienist. We also can't give medical advice about your hearing; that is a question for an audiologist.