Account data
Cross-Examine uses a secure third-party authentication service and stores account-related data needed for sign in, saved library access, usage limits, and subscriptions.
Privacy
This page explains how Cross-Examine handles your data during private beta. Final legal review will happen before public paid launch.
Cross-Examine uses a secure third-party authentication service and stores account-related data needed for sign in, saved library access, usage limits, and subscriptions.
Saved studies, sermons, audio source records, course progress, and notes are private to the user account unless a specific public sharing feature, such as a sermon session link, is used.
Cross-Examine may log protected audio access, including account, audio item, plan, page path, basic browser information, access time, and a hashed network identifier when available. These logs help protect rights, investigate misuse, and keep rare sermon archives secure.
AI prompts and responses may be sent to the configured AI provider so the app can generate responses. Do not enter confidential counseling details, private church discipline matters, or sensitive personal information.
Cross-Examine may record basic sponsor impressions and clicks, such as placement and page path. It should not use private sermon content, saved studies, notes, or doctrine responses for ad targeting.
Cross-Examine shows ads through Google AdSense. Google and its advertising partners may use cookies and similar identifiers to serve, measure, and (unless you opt out) personalize ads based on prior visits. Visitors in the EEA, UK, and Switzerland are asked for consent through a Google-certified consent platform before personalized-ad cookies are set, and can change or withdraw their choices at any time. You can review and control Google ad personalization at google.com/settings/ads, and read how Google uses advertising data at policies.google.com/technologies/ads.
Stripe handles payment information. Cross-Examine should not store raw card numbers or sensitive payment details.
Users are responsible for making sure uploaded or linked sources, audio, and transcripts are owned, permissioned, public-domain, or open-license.