Last updated: 31 July 2026.
This policy explains what MissionDefend collects when you visit missiondefend.com or read the blog at missiondefend.com/blog, why we collect it, and what you can do about it. We publish guidance about protecting other people’s information, so it would be a poor look to be vague about our own.
The short version
- We collect an email address only if you choose to type one into the launch-list form.
- We do not sell, rent, or trade your information, and we do not hand it to anyone else for their own purposes.
- The blog uses Google Analytics. The main site does not.
- There are no advertising trackers anywhere on this site.
- You can have your details deleted by emailing contact@missiondefend.com, and we will not ask you why.
When you join the launch list
The form asks for your email address, which is required, and your organization name, which is optional and can be left blank.
Three other things are recorded automatically when you submit it: the date and time, which page or button you submitted from, and your IP address. The IP address is kept for one reason — to spot and slow down automated abuse of the form. It is not used to identify you, build a profile, or work out where you are.
We use your email address to tell you once when the free assessment opens, and occasionally to share something directly related to it. Every message includes a way to stop receiving them. The list is not shared with anyone.
Signups are written to a file stored outside the public web directory, so it cannot be downloaded by guessing a web address, with file permissions restricted to the account that owns it. A copy of each signup is also emailed to us at contact@missiondefend.com. The form is served over an encrypted connection.
When you are just reading
You do not have to give us anything to read the blog. Our hosting provider, Hostinger, keeps standard web server logs of requests to the site — IP address, browser and device type, the page requested, the page you came from, and the time. Every web server does this. We use it for security and troubleshooting, and its retention is controlled by our host rather than by us.
Analytics
The blog uses Google Analytics, added through the Google Site Kit plugin. It sets a cookie named _ga and reports aggregate usage — which articles are read, roughly where readers come from, which devices they use. We look at it to decide what to write next, not to identify individuals.
Google processes that data under its own terms. You can opt out with Google’s browser add-on, by blocking cookies, or with any content blocker. Nothing on the site breaks if you do.
The main landing page has no analytics of its own. Because the analytics cookie is set for the whole domain, you may still see a _ga cookie there after visiting the blog, but the landing page does not send anything to Google.
Whose servers your browser contacts
This is the complete list of third parties involved in loading this site:
- Hostinger — hosting and content delivery for everything here.
- Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — typefaces on both the main site and the blog. Your browser requests the font files, which means Google receives your IP address as part of that request.
- Google Analytics (googletagmanager.com) — blog only, as described above.
- Gravatar (secure.gravatar.com) and s.w.org — WordPress defaults used for author avatars and site assets.
There are no advertising networks, no social media tracking pixels, no session recording, and no heatmap tools on this site.
The share buttons
The sharing buttons at the foot of each article are ordinary links assembled in your own browser. They load no code at all from Facebook, X, or LinkedIn, and those companies learn nothing about you unless you actually click through to them. The “copy link” button never sends anything anywhere — the address goes straight to your clipboard.
What we do not do
- We do not sell, rent, or trade personal information, and we never will.
- We do not share it with advertisers, data brokers, or partners for their own marketing.
- We do not build advertising profiles.
- Comments are turned off, so there is nothing to moderate and no commenter data to keep.
- Readers do not have accounts, and we do not collect payment details. When the assessment launches, this policy will be updated before anything new is collected.
Cookies
_ga— Google Analytics, on the blog.wp-settings-*— set only for signed-in site administrators, which means us. Readers never receive these.- The landing page sets no cookies of its own.
You can block or delete cookies in your browser settings. The site works normally without them.
How long we keep things
- Launch-list entries — until the assessment launches and for a reasonable period afterwards, or until you ask us to remove you, whichever comes first.
- Analytics data — according to Google’s retention settings for the property.
- Server logs — according to our host’s rotation schedule.
Your choices
Email contact@missiondefend.com and we will, within 30 days: send you a copy of what we hold about you, correct it, delete it, or stop contacting you. You do not need an account, a form, or a reason.
Depending on where you live — California and a number of other US states, and the UK and EU — you may have specific legal rights over your personal information, including access, correction, deletion, and the right to opt out of its sale or sharing. We do not sell or share personal information in the sense those laws use, and the same email address is how you exercise any of these rights. For readers in the UK or EU, we rely on your consent for the launch list and on our legitimate interest in keeping the site running for security logging.
Children
This site is aimed at adults running churches and nonprofits. It is not directed to children under 13 and we do not knowingly collect information from them. If you believe a child has sent us information, email us and we will delete it.
Security
Everything here is served over an encrypted connection. The launch list is stored outside the public web directory with restricted permissions. The signup form uses a hidden decoy field to catch bots rather than a tracking-based CAPTCHA. Administrative access is limited to the people who run the site.
We will not tell you that any of this makes a website impossible to breach, because that is not true of any website. What we can say is that we would rather be told than not: if you find a security problem on this site, email contact@missiondefend.com.
Changes to this policy
If this policy changes, the date at the top changes with it, and anything material will be described rather than quietly edited in. If we ever begin collecting something new — assessment answers, for example — this page will be updated before that collection starts.
Contact
Questions, requests, or corrections: contact@missiondefend.com.