← Back to Home

Privacy Policy

Last Updated: February 2026

The Short Version

We don't have your data. Period. HolyorNOT uses a Bring Your Own Key (BYOK) architecture. Your photos are sent directly from your browser to Groq AI using your personal API key. There is no HolyorNOT server — just static code hosted on Cloudflare's CDN. We have no database, no user accounts, and no way to see what you're verifying.

How HolyOrNOT Works

Understanding our architecture is the best way to understand our privacy. Here's exactly what happens when you use HolyorNOT:

Your Phone → Groq AI (api.groq.com) → Your Phone — your key
Your Phone → HolyOrNOT Servers → Anything
  1. You type a verse reference or Bible quote, or snap a photo of text containing a verse.
  2. Your browser sends the text or image directly to Groq's API at api.groq.com using your personal API key.
  3. Groq's AI reads the text (if image), then uses web search to look up the actual scripture and verify the quote.
  4. Your browser displays the verification results: verdict, actual scripture text, translation match, and more.

There is no HolyOrNOT server. The website is a static page hosted on Cloudflare's CDN — it delivers the code that runs in your browser, and that's it. No backend, no API, no database.

What We Collect

Data Type Collected? Details
Photos of verses No Sent directly from your browser to Groq (if you use camera). We never receive them.
Verse queries No Sent directly from your browser to Groq. We never see them.
Verification results No Returned from Groq directly to your browser. We never see them.
API keys No Stored in your browser's local storage only. Sent only to Groq.
User accounts No There are no accounts. No login, no registration, no email.
Usage analytics No No tracking pixels, no analytics scripts, no cookies.

Your API Key

Your Groq API key is stored exclusively in your browser's local storage — the same mechanism websites use to remember your preferences. It is:

Third-Party Services

Groq (AI Provider)

When you use HolyOrNOT, your browser sends data directly to Groq's API for both text reading (vision) and scripture verification (web search). This is governed by your own relationship with Groq — you signed up for your own API key and agreed to their terms.

HolyorNOT has no partnership, data-sharing agreement, or business relationship with Groq. You use their API independently.

Cloudflare (Hosting)

HolyorNOT is hosted on Cloudflare Pages. Cloudflare may log basic access data (IP address, page requested, timestamp) as standard web infrastructure. Cloudflare does not receive any verse queries, photos, API keys, or verification results.

Google Fonts

We use Google Fonts for typography. Google may collect basic connection data (IP address) when fonts are loaded. No personal information is shared.

Verify It Yourself

We encourage you to verify our privacy claims independently:

  1. Open HolyorNOT in your browser
  2. Open Developer Tools (F12 or right-click → Inspect)
  3. Go to the Network tab
  4. Verify a verse
  5. Look at every network request — you'll see requests only to api.groq.com and fonts.googleapis.com

Data Breaches

In the event of a data breach, your data would not be affected because we don't have it. There is no database to breach, no search history to leak, and no user records to expose.

Children's Privacy

HolyorNOT does not knowingly collect any data from anyone, including children. Since no personal data is collected or stored anywhere, COPPA compliance is inherent to our architecture.

Changes to This Policy

If we change our architecture in a way that affects data flow, we will update this policy prominently and clearly explain what changed and why.

Contact Us

Questions about privacy? Reach out:

The Bottom Line

We can't sell what we don't have. We can't leak what we don't store. We can't share what we never see. That's not a promise — it's our architecture.