Privacy policy
This page explains, in plain language, what the public ministry site and Dave chat may receive, why that information is used, and where the boundaries need to stay clear.
Effective and last updated: May 10, 2026.
1. Information you provide directly
When you use the public ministry website, you may choose to submit information through contact, prayer, support, billing-related messages, or the public feedback button. That can include your name, email address, subject line, prayer request, account or payment context, website report type, page link, suggested fix, and any message content you type.
The public feedback button is meant for website repair reports and ideas. It may save the current page URL and title, your report, your optional fix suggestion, an optional email address, basic browser context such as viewport and language, referrer, user-agent, and a salted IP hash. Please do not use that button for private account, payment, medical, legal, financial, emergency, or prayer details.
If you use Dave AI chat, the system creates a session identifier in your browser so the chat service can keep track of daily usage and recent conversation history for that session.
2. Operational and technical information
Like most public websites, the systems that keep the site running may process technical request information such as IP address, page path, timestamps, browser details, and response codes. That information helps with security, abuse prevention, debugging, and basic service reliability.
The current public Dave AI deployment also keeps session identifiers, usage counters, and recent chat messages for the active service so the chat can work like a real service instead of resetting every time someone asks a question. Conversion and telemetry dashboards are intended to use aggregate route, event, and status counts rather than exposing raw personal data, prompt bodies, or private message content.
3. How information is used
- To receive and respond to ministry contact or prayer requests
- To route app support, account, cancellation, refund, or billing questions to the right follow-up path
- To operate the public Dave chat surface and enforce usage limits
- To triage public website feedback into fixes, content corrections, accessibility repairs, ideas, Company HQ assignments, or website workorders
- To secure, monitor, debug, and improve the public website and chat service
- To process donations or paid access through third-party payment providers rather than direct card storage on the ministry site
4. Advertising, analytics, and consent baseline
As of this public benchmark, the main ministry marketing pages are intended to run without advertising pixels, retargeting tags, or cross-site campaign scripts such as Meta Pixel, Google Ads remarketing, or similar ad-tech trackers. The current privacy baseline is to keep the public site understandable before adding that layer.
Operational analytics and telemetry should stay limited to route, event, status, and service-health signals that help the site function responsibly. If Dancz Ministries later adds non-essential analytics, advertising tags, or campaign retargeting, the ministry should first update the public notice language, consent flow, and campaign-readiness checks before launch.
The absence of an advertising-cookie banner on the current public pages should not be read as permission for silent campaign tracking later. It reflects the current benchmark: essential/session behavior only, with future consent controls required before non-essential tracking goes live.
The current public event plan is route-based and intent-based: page views, guided-path clicks, giving starts, support starts, beta starts, and content engagement can be counted in aggregate, but private bodies and cross-site behavioral dossiers should stay out of scope. See Data Handling → Privacy-safe analytics plan for the current implementation checklist.
5. Payments, access, and third-party handling
The giving and access paths may route donors, supporters, or subscribers to Stripe, PayPal, app-store billing, or another clearly named payment provider for payment processing. Dancz Ministries does not present itself as storing your card or bank details directly on this public site.
The site also relies on hosted infrastructure and WordPress/plugin tooling to run public pages, forms, and site operations. Those providers may process technical information as part of normal service delivery.
6. Dave AI chat note
Dave AI is an AI-assisted chat surface, not a human staff member. The public Dave AI service may use session-based chat usage, recent message history, configured runtime context, and memory-gateway writeback so the service can answer with continuity, apply safety boundaries, and enforce usage limits. Do not type anything into Dave chat that you would not want handled by a live AI service and its operating infrastructure.
7. What not to send
Please do not use this site or Dave chat for emergencies, urgent crises, or highly sensitive legal, medical, financial, or identifying information. Those situations deserve safer channels and faster real-world help than a public web surface can promise.
8. Sharing and retention
Dancz Ministries does not present this public site as a place where personal information is bought or sold. Information may still pass through hosting, form, email, security, support, and payment providers when that is necessary to operate the site responsibly.
Operational data, submitted messages, support or billing records, chat session records, and website feedback records may be kept for ministry response, service operation, abuse prevention, dispute handling, repair history, or recordkeeping for as long as reasonably needed unless a shorter retention path is introduced later.
For the public website feedback lane, Dancz Ministries may keep the non-private repair history while scrubbing optional contact email addresses from closed feedback after the configured retention window. IP addresses for that lane are stored as salted hashes rather than plain addresses.
9. Questions, corrections, or deletion requests
If you want to ask how something was handled, request a correction, or request deletion where appropriate, start with the ministry contact page. For private RuachDavid app, account, or billing issues, use the direct support path rather than public Discord. Not every request can be granted in every situation, but the path for asking should stay human and clear.