Effective August 14, 2026 · Version 5.0
Data collected
The platform may process essential technical data, search and navigation events, contact information you submit, and commerce information supplied through Stripe.
Payments
Payment card data is handled by Stripe through hosted Checkout. KJV Visualized does not store raw card details.
Accounts and commerce records
When you sign in, KJV Visualized stores the minimum account profile, wallet ledger, credit holds and gifts, orders, plan subscription identifiers and status, entitlements, license status, saved resources, private Bible Desk records, download counts, API-key hashes, and API usage needed to provide and protect the service. License-key values and private Scripture notes are encrypted; API-key values are stored as one-way hashes.
CrownThrive IO boundary
The CrownThrive IO bearer credential remains server-only. The browser receives only a sanitized connection state and plan allowance. The KJV Visualized health probe uses the fixed documented API origin and minimal authenticated user endpoint; it parses and discards the bounded provider response and does not return upstream identity records, account payments, logs, team data, or the master credential to the browser.
Download security
Download activity is recorded against the entitlement. A short request fingerprint may be derived for abuse prevention, but raw IP addresses are not retained in the download ledger.
Creator Commerce privacy
KJV Visualized stores only the public creator profile owner, connected Stripe Account reference when created, approved marketplace policy, derived requirements and capability states, and event evidence needed to operate the creator rail. Settlement records will be stored only when connected-seller checkout is activated. Bank account numbers, identity documents, tax identifiers, payout-instrument details, and Stripe KYC answers remain with Stripe and are not copied into My Sanctuary.
Partner Circle privacy
The Partner Circle stores the verified account owner, application, append-only terms and review evidence, approved code, explicit per-order attribution, reward and reversal ledger, and a one-way buyer email hash used for self-referral review. It does not install a hidden sitewide referral cookie or create a cash earnings balance.
Analytics
Meaningful events may support CrownLytics and CrownPulse integration. Public metrics are not manufactured from internal analytics.
Choices
Where required, consent controls and tracking notices will be used before nonessential measurement.
Questions?
Contact CrownThrive at contact@crownthrive.com.