Skip to content
QiblaWeb

Trust Center

Trust is the product. Below is how QiblaWeb keeps its no-ads, no-tracking, no-stored-visitor-data promise — technically, not just on paper.

Public promise

How this is implemented technically

  1. There is no visitors table in the database. The D1 schema only contains public reference data: cities, methods, sourced duas.
  2. GPS coordinates do not appear in URLs or request bodies. The browser-side script computes results locally.
  3. No third-party assets on public pages (except Stripe on /donate and Turnstile on contact/donate forms).
  4. Every deploy is auto-checked by CI for forbidden tracking patterns. The build fails immediately if Google Analytics, Meta Pixel, Clarity, PostHog, Amplitude, Mixpanel or similar appears.
  5. Server logs redact sensitive parameters (lat/lng/donation amounts/push endpoints).

What we do store

Only public reference data (numbers below are read live from the production database):

Infrastructure providers

QiblaWeb runs entirely on Cloudflare's global network. When donations launch later, payment sessions will be created via Stripe Checkout. These are infrastructure providers only.

AI engines and crawlers

Our robots.txt allows search engines (Google, Bing) and answer engines (OAI-SearchBot, PerplexityBot, ClaudeBot) to read our public content — QiblaWeb's value is being a sourced, citable resource. We disallow only crawlers that don't serve end users or that train closed models on the data.

Contact

For questions about privacy or content accuracy: support@qiblaweb.com