Privacy

GEBible has no accounts and no analytics. This page lists every cookie it sets, everything your browser keeps on your own device, and exactly what Google’s ad system does here.

Last updated August 4, 2026.

The short version

No account — nothing here asks you to sign up, and there is no user table for you to be in.
No analytics — no analytics product, no tracking pixel, no session recording, no script of mine watching what you read.
Few cookies, all listed — every cookie this site sets is named below, with what it does and how long it lasts.
Your notes stay in your browser — notes, saved passages and your recent trail live on your device and are never sent here.
Advertising is the one third party — Google’s ad system is the only outside code that ever runs on these pages.
Nothing about you is sold — I do not sell or rent reader information. There is none to sell.

What this site collects

Every request your browser makes has to carry a few things for the server to answer it: the address you asked for, your IP address, your browser’s user-agent string, and whichever of the cookies below your browser is holding. That is what a web request is.

None of it is kept in a way that is tied to you. There is no account, no user table, no profile and no reading history on any server — so there is no record to join those requests together into.

Like any web server, the service that hosts this site processes your IP address in order to send you the page, and may keep standard server logs. I do not run analytics on top of those logs and I do not build any profile from them.

What this site does not do

No analytics or tracking scripts. No analytics product, no pixels, no heatmaps, no session recording.
No accounts, passwords, email list or newsletter. There is nothing here to sign up for.
No selling or renting. Reader information is not passed to anyone.
No cross-site tracking by this site. GEBible does not follow you around the web. Google’s advertising cookies can — see Advertising below.
No third-party fonts. The typefaces are served from this site’s own server, not from Google Fonts, and the content-security policy permits fonts from nowhere else.

What stays on your device

These live in your browser’s own storage. The server never receives them and has no way to ask for them.

theme — your light/dark choice, mirrored from the cookie so the page paints in the right theme before anything else loads.
gb_recents — the short trail of passages you have looked at, shown on the home page.
gb_saved — the passages you star.
gb_note:<passage> — the study note you type on a verse page, one key per passage.
gb_reader_tip_dismissed — that you closed the reader’s one-time tip, so it stays closed.
gb_ad_notice_dismissed — that you closed the note about blocked ads, so it stays closed.
gb_patron — a copy of your supporter state, used only to notice when it changes.
ge-runtime — pages you visit are kept here automatically as you browse, so they still open when you go offline. You do not switch this on. It holds up to 120 of the most recent items — pages, and the styles, scripts, images and fonts they use — and drops the oldest to stay under that. Pages the server marks as not-to-be-stored, such as sign-in, are never put in it.
ge-shell-… — the handful of files the site itself is made of (the stylesheet, the script, the icons, the fonts), stored when the service worker installs so the app starts without the network. Replaced on each update.
ge-offline-… — the one you do choose: if you use “Read offline” in Settings, whole translations are downloaded into a bucket of their own and kept until you delete them.

None of this is sent to the server, none of it is backed up anywhere, and clearing your browser data deletes all of it. There is no copy of it on any machine but yours.

Advertising, and Google’s use of cookies

When this site shows you an ad, it is served by Google AdSense. Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this website or to other websites. Google’s use of advertising cookies enables it and its partners to serve ads to you based on your visit to this site and/or other sites on the Internet.

You can opt out of personalised advertising:

For Google, at Google Ads Settings.
For other vendors, at aboutads.info/choices.

Google sets out what it does with information from sites that use its services in How Google uses information from sites or apps that use our services.

Those advertising cookies are set by Google, not by this site, and this site cannot read them.

Where an ad can appear is a rule, not an accident. No ad is placed between the verses of a chapter, or inside a Scripture Analysis argument. Most pages carry one, after the last block of content. A few carry more: the blog, search results and the tools and topics lists each add one above the content, and the book index adds one there and a third at a seam between two of its sections. This page carries one too, at the foot.

Supporters see none of it. If you are signed in at any paid level, no ad is shown to you and Google’s ad script is not loaded on your pages at all — there is nothing to opt out of, because nothing third-party runs.

Where consent is required before personalised ads may be served, Google’s certified consent message is shown first. It is delivered by the AdSense tag itself — there is no separate consent script of mine — and your choice is recorded by Google, not stored here.

This site runs no cookie banner of its own and sets no advertising cookies itself. The cookies in the list above remember choices you made on this site — your translation, your theme, your reading mode, your supporter level — and are not used for advertising.

Search, and what leaves this server

Searches run entirely on this server. The optional “Related by meaning” band ranks passages with a sentence-embedding model that runs here as well — your search is never sent to any third party.

Your search terms do travel in the page address, so they are in your own browser history and in whatever standard server logs the host keeps, exactly as any address is.

If a request fails, the server writes the method and address to its error log so the fault can be found. That log is not analytics and is not joined to anything about you.

Signing in with Patreon

Signing in is optional. Nothing on this site requires an account, and the only thing signing in does is tell this site which support level you are on.

The sign-in asks Patreon for two scopes, identity and identity.memberships, and the request that follows asks for no profile fields at all — only whether a membership is active and what it is worth. This site does not ask Patreon for your name or your email address.

The access token Patreon issues is used once, in memory, for that single check. It is never stored and never written to a log.

There is no user table and no server-side record of you. The signed cookie is the entire record: a Patreon account id, the name of your level, and the timestamps that expire it — when it was issued, when you first signed in, and when it stops being valid. Nothing else, and you can decode it yourself and check. Signing out clears that cookie and nothing is left behind, because there was nothing else.

Payment happens on Patreon. No payment details ever reach this site.

Children’s privacy

This site is not directed to children under 13 and does not knowingly collect personal information from them. There are no accounts, so there is nothing to collect.

If you believe a child has provided personal information here, email me and I will remove it — though with no accounts and no reader records, there is normally nothing to remove.

Links to other sites

This site links out to Patreon, to the sibling app Lemma, and to the source archives credited on Sources & licenses.

Once you follow a link, that site’s privacy policy applies to what happens there, not this one.

Changes to this policy

If this policy changes materially, the date at the top of the page changes with it. That date is the whole record: it moves when the text moves, and it does not move otherwise.

There is no mailing list to notify you from, and no changelog — the date is the notice.

How to reach me

Email john@godlessengineering.com. One person, not a ticket system.

There is no data-request form here because there is no database of readers to search. What you can do yourself covers it: clearing your browser data removes everything listed under What stays on your device, and signing out clears pt_session.