Privacy Policy

BibleHearth has no accounts, advertising, or fields that ask for your name. The site does use four measurement tools, and its hosting service keeps ordinary server logs. This policy explains each service and the data it sees.

Last updated August 20, 2026.

The short version

BibleHearth does not know your identity. The site does not sell visit data, build an advertising profile, or send information to an ad network. Its analytics show which pages are read, how visitors arrive, and their approximate location.

A page address can still reveal which passage or sensitive topic someone is reading. The section below explains that in more detail.

What this site does not do

There is no account, no login and no sign-up.
There is no newsletter and no email is ever collected.
There is no advertising, no ad network, and no tracking pixel from a social platform or an advertiser.
Nothing about a visit is sold, rented, or shared for money, and nothing is used to target advertising anywhere else.
This site sets no cookies of its own. It keeps no session, so it has nothing to keep one in.
No page here has a comment box, a form that asks about you, or a field you can type into. The only form on the site is three dropdowns that pick a translation, a book and a chapter — so the only thing you can submit to this site is which passage you want to read.

Who receives what

Four third parties see something about a visit. Each is named here with what it collects and what it stores in your browser.

Vercel

Hosting, and Web Analytics

What it collects: Every request to this site passes through Vercel, which serves the pages and keeps ordinary server logs. Its Web Analytics records the page, the referrer, approximate location from the request, and the browser, operating system and device type.
Cookies: None. Vercel uses a hash of the incoming request to identify a visit and discards it after 24 hours.
Their policy: vercel.com/legal/privacy-notice

Google Analytics 4

Traffic measurement

What it collects: Page views, referrers, approximate location, and browser and device information, used to see which pages are read and how people arrive.
Cookies: Sets first-party cookies named _ga and _ga_ followed by a property identifier. By default, they can remain for up to two years, longer than any other cookie used on this site.
Their policy: policies.google.com/privacy

Microsoft Clarity

Session replay and heatmaps

What it collects: Records pointer movement, clicks, scrolling, and where a reader stopped. This shows whether people reach the end of a chapter study or leave partway through.
Cookies: Sets cookies named _clck and _clsk. Clarity applies its own consent mode by default to visitors in the European Economic Area, the United Kingdom, and Switzerland. It sets no cookie for those readers unless the site passes a consent signal; BibleHearth passes none.
Their policy: Microsoft Privacy Statement

Ahrefs Web Analytics

Traffic measurement

What it collects: Page views and referrers, used alongside the search data the same account reports on.
Cookies: None, according to Ahrefs, which describes the script as cookie-free.
Their policy: ahrefs.com/legal/privacy-policy

These are the only third parties currently receiving visit data. If the list becomes incomplete, please tell us so we can correct it.

Session recording, plainly

Microsoft Clarity can reconstruct how a page was used from pointer movement, clicks, and scrolling. It cannot see your camera, microphone, other tabs, or anything outside BibleHearth.

The site has no account fields, search box, or other place to type personal information. Clarity therefore has no form entries to capture.

What your reading reveals

The passage you are reading appears in the page address, so a page view records that someone read Psalm 23, or a topic page about grief, or a question about the unforgivable sin. In several countries what a person reads about their faith is treated as a special category of information, and rightly.

None of it is tied to a name, an account or an email, because this site has none of those to tie it to, and we make no attempt to work backwards from a visit to a person. But it is measured, by the four tools above, and a page about a hard subject is measured exactly like any other.

Scripture is fetched by BibleHearth's server. Your browser never requests it directly from a translation publisher, so the publisher receives no visit data from you. The commentaries are also stored and served here.

How to stop it

A content blocker will stop all four scripts, and nothing on this site breaks when it does. The pages are rendered on the server and ship almost no JavaScript. With every analytics script blocked, you still get the text, the commentary, and the links. Nothing here detects a blocker, asks you to turn it off, or works less well because one is on.

Private or incognito browsing discards the cookies at the end of the session, and clearing cookies for this site removes them. Google also publishes a browser add-on that opts out of Google Analytics across every site that uses it.

BibleHearth does not currently respond to Do Not Track or Global Privacy Control signals. A content blocker is the reliable way to prevent these analytics requests.

Email you send us

If you write to hello@biblehearth.online, your message and address stay in that mailbox, and are used to answer you and to fix whatever you wrote about. They are not added to any list, because there is no list, and they are not passed to anyone else.

Children

This site is written for adults and older readers. It has no account, profile, or place to submit personal information, and it does not knowingly collect a child's details. If you believe something has been collected about a child, write to us and we will remove what we can.

Your rights and what we can do

Depending on where you live, you may have the right to ask what is held about you, to have it corrected or deleted, or to object to it being processed at all. Write to hello@biblehearth.online and we will do what we can.

Our ability to act is limited because analytics data is not tied to an identity. We cannot look you up because there is no record with your name on it to send you, correct or delete. For the aggregate measurement that does exist, the effective remedy is the one above: block the scripts, and nothing about your visits is measured at all. For anything held by Google, Microsoft, Ahrefs or Vercel about you across their own services, their policies above are where those requests are handled.

Changes to this page

When the list of tools above changes, this page changes with it and the date at the top moves. There is no archive of previous versions; if you want to know what it said before, ask.