Last Updated: May 16, 2024
This Privacy Policy explains how Scripture Verse Popup Preview ESV (the "Extension") handles your information. Your privacy is a top priority.
The Extension is designed to function without collecting or transmitting any of your personal or sensitive user data. Specifically, we do not collect, store, track, or transmit:
To enhance your experience and provide configurable options, the Extension stores certain preferences locally in your browser using Chrome's secure storage (`chrome.storage.sync`). This data is synchronized across your signed-in Chrome browsers but is not accessible to the Extension author or any third party, other than Google as part of its Chrome Sync service. This locally stored data includes:
https://api.esv.org/) when you request verses from the ESV translation.This data remains on your computer and is managed by your browser.
When you select a Bible reference or use the browser action popup to look up a verse, the Extension communicates with external, public Bible APIs to retrieve the scripture text. The specific API used depends on the translation selected, as configured in the Extension's `bibles.json` file. These APIs may include:
The Extension only sends the minimal information required to fetch the requested scripture (i.e., the Bible reference and API key where necessary as per `bibles.json` configuration). No user-identifiable information beyond what is intrinsic to an API request (like your IP address, which is handled by the API provider according to their own privacy policies) is sent by this Extension to these APIs.
We encourage you to review the privacy policies of these third-party Bible API providers if you have concerns about how they handle data.
The Extension includes a `bibles.json` file that maps Bible translation codes to their display names and API configurations. This file is part of the Extension's static assets and is fetched locally using `chrome.runtime.getURL('bibles.json')`. API keys for services like ESV or scripture.api.bible are intended to be placeholders in the repository version of this file and replaced with actual keys during a build process (e.g., via GitHub Actions secrets) for published versions. For KJV, ASV, WEB, etc., that use keyless public APIs (like the CDN or bible-api.com), no keys are stored or needed in this file. No external communication is initiated by the Extension to fetch or update this configuration file post-installation.
We take reasonable precautions to protect the information stored locally by the Extension. However, no method of electronic storage is 100% secure. Your ESV API key is stored as you provide it, and it's your responsibility to ensure its security if obtained from Crossway.
We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy within the Extension or on its Chrome Web Store listing. You are advised to review this Privacy Policy periodically for any changes.
If you have any questions or concerns about this Privacy Policy or the Extension's practices, please contact the extension author via the Chrome Web Store listing for Scripture Verse Popup Preview ESV.