Privacy Policy
Bible Verse Labs is designed as a calm, mostly read-only scripture experience. This page explains what the current site does, what it does not do, and how routine technical data may be handled when pages are delivered.
Privacy Details for the Public Site
This page is written for the current public experience only: daily scripture, random verse browsing, topic pages, and local copy or share actions initiated by your device.
Overview
Bible Verse Labs is a scripture discovery website built around daily scripture, a random verse tool, and topic pages. The current public experience is primarily read-only.
This policy reflects the current version of the site. It is written for the features that exist today and does not assume accounts, payments, uploads, private messaging, or contact-form workflows that are not present in the app.
Information Collected
Bible Verse Labs does not currently ask visitors to create an account, submit a form, upload content, or enter payment information. The site does not provide a public user profile or comments system in its current version.
When pages are requested, the systems that deliver the site may process routine technical information such as IP address, browser or device type, referring page, and request timing. Bible Verse Labs also uses Fathom Analytics to measure page visits and referral patterns in a privacy-focused way. If you use copy or share actions on a supported device, those actions are initiated by your browser or device and are not submitted back through a public form on this site.
How Information Is Used
Because the current site experience is mostly read-only, Bible Verse Labs does not currently use personal information for account management, checkout, user-generated content moderation, or customer relationship workflows.
Routine technical data, if processed to deliver the site, may be used to serve pages, maintain reliability, troubleshoot errors, support basic security and operational monitoring, and understand which pages or traffic sources are helping people find the site.
Cookies and Technical Data
Bible Verse Labs is not built around login sessions, shopping carts, or personalized dashboards. The current site therefore does not depend on those kinds of feature-specific cookies.
Like most websites, browsers and delivery infrastructure may still use cookies, headers, caches, or similar technical mechanisms that are reasonably necessary for security, performance, and page delivery. The site currently uses Fathom Analytics for traffic measurement and is configured to respect browser Do Not Track signals.
Third-Party Links and Services
Bible Verse Labs may link to third-party websites or resources. If you leave this site through an external link, the privacy practices of the destination site will apply there instead of this policy.
Analytics information handled by Fathom Analytics is also subject to that provider's own terms, infrastructure, and privacy commitments. Device-level sharing, clipboard access, and browser features are governed by your browser, operating system, and any services you choose to use through them.
Data Retention and Security
Because the current public site does not provide accounts or stored user submissions, Bible Verse Labs does not intentionally maintain a visitor profile database through the features available here.
Any routine technical logs or operational records kept by the systems that deliver the site may be retained only as reasonably needed for security, debugging, and reliable operation. No method of internet transmission or electronic storage can be guaranteed to be completely secure.
Children's Privacy
Bible Verse Labs is a general-audience scripture website and is not designed to knowingly collect personal information from children through the current public experience.
If the site's features change in a way that introduces direct data collection, this section should be reviewed and updated to reflect that change.
Policy Changes
Bible Verse Labs may update this privacy policy as the site changes. If new features introduce different data practices, this page should be revised to reflect them.
When updates are made, the date shown on this page should be changed from April 5, 2026 to the new effective date.