PUBLIC WEBSITE · SEPTEMBER 5, 2026
Privacy for your application
This notice covers information supplied through the public DLR Command website. Operational member access and church records are configured separately.
What you share
The church application collects the administrator’s name and email, church identity and branding links, campus and service information, team role titles, document source information, and optional notes. Please do not include passwords, personal incident records, access codes, or sensitive security plans.
How it is used
DLR Command uses your application to review fit, prepare a proposed configuration, and follow up with your nominated administrator. Submitting an application does not create an account, activate a church, or publish its app.
Where it goes
Applications are stored in DLR Command’s Cloudflare-hosted database and reviewed through its protected owner administration area. The public website offers no application lookup or public response list. Application content is not placed in public pages or notification text.
Your browser and technical requests
Unsubmitted church intake entries remain in page memory and clear when you refresh or leave. The website does not use advertising trackers. Hosting services process technical request information, including IP addresses, to serve the site and limit abuse. A submitted application remains available to DLR Command for review after the browser is closed.
Corrections and removal
Contact info@dlrcommand.com to request a correction, ask about retention, or request removal of an application. Include its reference if available. We may need to verify your authority before changing or releasing information. Applications are retained for review and follow-up; an automatic expiry is not currently configured.
Document and website links
Supplying a website or library link does not grant DLR Command permission to change its access settings. Keep protected documents protected. Logo import and document permissions are reviewed separately.