Feedback

Tell us what's broken, wrong, or missing.

Why we want to hear from you

One of our founding commitments is this: earn the skeptic's respect without losing the believer's trust. That only works if we would rather be corrected than confident-and-wrong. If you have caught something — however small — please tell us. Feedback is not a complaint channel here. It is how the site gets better.

Corrections

If you have found a mistranslation, a broken cross-reference, a misattributed source, a hallucinated claim, or a Strong's number that does not match the lexicon — send it over. Please include the exact verse reference, the page URL, and what you believe is wrong.
[email protected]

Bug reports

For anything that looks broken — a page that will not load, a search that returns nothing, a layout issue on your device, an audio player that misbehaves — please include your device, browser, the URL, and the steps that triggered it.
[email protected]

Feature requests

Tell us what study tool you wish existed. The roadmap is shaped by real use, not guessing. If you wanted to answer a specific question and could not, that is exactly what we want to hear.
[email protected]

Scholarly review

We invite academics, linguists, archaeologists, historians, and theologians — from any tradition or none — to submit critique of our methodology, data sources, or published claims. Disagreement is welcome; citations are better.
[email protected]

What happens next

We read every message. Verified corrections are applied to the data and, where relevant, the correction is noted in the commit history so the trail stays public. We cannot always reply individually, but nothing is ignored.