Last Updated: September 2, 2026 · Applies to v1.41.0 and later
BibliaTab does not collect, sell, or share personal data. Nearly everything it stores stays on your device (or in your browser's own account sync, under your control). This page explains exactly what data moves where, and why.
Local & Synced Storage
BibliaTab saves your preferences so they're there next time you open a new tab.
Settings, notes, and shortcuts are saved via your browser's built-in storage.sync API. If you're signed into your browser (Chrome, Edge, or Firefox account) with sync enabled, these travel with your browser's own encrypted sync — the same mechanism it uses for your bookmarks or other extensions' settings. BibliaTab never sends this data to any server we operate; it goes only through your browser vendor's own sync infrastructure.
Custom background photos you upload are kept in local browser storage on that device only — they are not synced, since they're too large for sync storage.
Verse highlights are kept in local browser storage.
If sync isn't available, everything above falls back to plain local storage on that one device.
Uninstalling the extension, or clearing its site data in your browser, removes all of it.
External Services BibliaTab Talks To
These requests happen only when you use the related feature. None of them include your name, email, or any account identifier — BibliaTab has no accounts.
bolls.life & bible.helloao.org
Purpose: fetch Bible verse/chapter text.
Data sent: the book, chapter, and translation you requested.
api.scripture.api.bible
Purpose: fetch the list of books for certain Bible translations in the Bible Reader.
Data sent: the translation ID you selected, plus an app-level API key (not tied to you personally).
api.open-meteo.com
Purpose: fetch the current weather for the widget.
Data sent: latitude/longitude only.
nominatim.openstreetmap.org (OpenStreetMap)
Purpose: turn coordinates into a readable city name, or a city name you type into coordinates.
Data sent: either device/IP-derived coordinates (see "Geolocation" below), or the city name you manually enter in Settings.
api.bigdatacloud.net
Purpose: coarse, city-level location fallback for weather, used only if device location isn't available (see below).
Data sent: your IP address, sent automatically by the browser as part of any web request — BibliaTab doesn't add anything to it.
picsum.photos
Purpose: background photos when "Picsum Photos" is selected as your background type.
Data sent: a randomly generated number and the image size requested — no personal data, no category label.
All requests use HTTPS.
Permissions Explained
Storage required
Lets BibliaTab save your settings, notes, and shortcuts as described above. It cannot read anything else in your browser.
Search required
The new-tab search bar uses your browser's Search API to send what you type to your own default search engine — the same one your browser's address bar already uses. BibliaTab doesn't see, log, or store your search queries; the browser hands them directly to your search engine.
Geolocation optional feature, still requires the permission be present
Used only for the weather widget, in this order:
Device location (GPS / Wi-Fi / network), via your browser's own one-time permission prompt. You can Allow or Deny this prompt — either is fine.
If denied, unavailable, or it times out: coarse IP-based location (city-level, via BigDataCloud).
If that also fails: BibliaTab shows a default forecast and a prompt to type your city manually in Settings.
You can skip all of this by typing a city name (or exact coordinates) directly into Settings → Weather Location at any time.
What BibliaTab never asks for
✗ Browsing history, open tabs, or bookmarks
✗ Your files, downloads, camera, or microphone
✗ Any account, sign-in, email, or password
✗ Advertising or analytics identifiers
Third-Party Data Sharing
BibliaTab does not sell or share data with advertisers, analytics companies, or data brokers. The only outbound requests are the ones listed above, each triggered directly by something you did (opened a tab, read a chapter, checked the weather, changed a background).
Security
All external requests use HTTPS
A Content Security Policy restricts the extension to a known list of endpoints (the ones listed above)
User-entered text is sanitized before being inserted into the page