Trust and legal
Privacy policy
We collect what you type into our forms and what an account needs. We do not sell it, we run no ad trackers, and you can have it deleted.
Last updated
In plain words
- What we hold The details you type into a form, and for a signed-in person a name, an email address and saved work.
- No ad trackers No analytics script, advertising pixel or tag manager runs on our pages.
- Never sold We do not sell or rent your information. A few service providers handle it for us, and they are named below.
- Delete it Delete a signed-in account in one step, unsubscribe in one click, or write to us and we remove anything else we hold.
Who we are
This policy covers churchposting.com and the free tools, forms and emails that run from it. The company behind it is Ministry Marketing LLC, doing business as Church Posting, a Kansas company, and it decides how the information described here is used. Write to hello@churchposting.com with any question.
Church Posting makes the free tools and also makes Covenant OS, Berean Blue, cOS Texting and Church SEO Experts. Those four have their own sites and notices, and this policy does not cover them. The one place the two meet is sign-in, described under Accounts and Covenant OS.
What we collect
Reading the site needs no account and sends us no form data. These are the things we collect, and the moment each one happens.
| When | What we store |
|---|---|
| You join the weekly email or any list | Your email address, your name if you give it, what you told us you are (job seeker, church staff, pastor, musician), the lists you agreed to, the exact sentence the form showed, the page, the time, and when you confirmed by pressing the link we email. Nothing goes out to a list until you confirm. |
| You get a file from a free tool | The tool asks for a name, an email address and a church. We store the name, the email address, the tool's name and the sentence the form showed. The church name is not stored. Giving the address also joins you to the weekly email, and the form says so. |
| You ask for Covenant OS beta access | Your email address, your name and your church's name. |
| You join the Berean Blue list | Your email address and the list's name. |
| You send a message with the contact form | Your email address, your name if you give it, the topic you chose and your message. A copy goes to our own inbox so we can answer. |
| You list or claim a church | Your name, role and email address, and the church's name, city, state, website and phone number. If you send a logo or photo link from your church's own website, we store the link. We record whether you affirmed the listing standard. |
| You post a ministry job | You sign in first. We store the church's name, the job title, city, state, category, hours and description, where to apply, pay and closing date if you give them, the church's website, address and service times, the denomination if you give it, whether you affirmed the listing standard, and the email address on your account. We read the church website you give us and save the lines that decided the automatic check with the posting. |
| You set a job alert | Your email address and the alert you saved: kinds of role or a role, denomination family, hours, the lowest pay you want, whether pay must be listed, keywords, a place with a distance or remote work, and how often the email comes. We also keep which jobs each alert already sent. |
| You follow a church | Your email address and the church, so we can email you when it posts a job. |
| You save something before signing in | Your email address and what you saved, for seven days. When you sign in with that address, you choose which saves to keep in your account. Saves are deleted after seven days either way. A save does not sign you up for any email. |
| You track jobs in your account | The jobs you save, the stage you mark for each (saved, applied, interviewing, offer, closed), the date you changed it, and any note you write. |
| You unsubscribe | Your email address, the time and how the request came in. See Your choices. |
| You sign in | An identifier from Covenant OS, your email address and your name. See Accounts and Covenant OS. |
| You use a free tool signed in | The documents, lists and saved items you choose to keep in your account. |
| You sign in, sign up for email or send a contact message | A salted hash of your IP address and a counter, so we can slow down repeated attempts. We do not keep the address itself. We also keep salted per-address counters for form requests and triggered emails. A separate counter limits settings links to one every 30 days for an address that asked us to stop email. |
| Anyone loads a page | Cloudflare, which hosts the site, records ordinary server logs such as IP address and the page requested, to run and protect it. |
Each form has a hidden field that real visitors never see. A bot that fills it gets no record. A form that shows a Cloudflare Turnstile check sends Cloudflare signals from your browser so it can tell people from bots.
Where it is kept
Forms post to our service at social.churchposting.com. It stores what you send in a Cloudflare D1 database named church-posting-social. Contact messages sit in their own table there, with your name, email address, topic and message. Cloudflare hosts the site and the service.
Each night the service copies the email list, consent records, job alerts and saved jobs to a private Cloudflare R2 storage bucket, so a fault cannot lose them. Each copy includes the salted IP hash held with each email consent capture. We delete each backup after 90 days.
We send email through Amazon SES or SendGrid. GoHighLevel (LeadConnector) is a temporary fallback for transactional messages and holds contact records and tags. Job alerts, welcome emails and requests to confirm an older signup use only Amazon SES or SendGrid.
Why we use it
- To send what you asked for: the weekly email, job emails, a launch notice for Berean Blue, or a note about the Covenant OS beta.
- To answer a contact message.
- To check a church claim against the listing standard, update a page and tell you.
- To check a job posting against the listing standard, publish it when it passes, tell the church when it is live, or tell it why we could not list it.
- To keep your saved work in sync across your devices when you are signed in.
- To keep the site safe, by limiting repeated sign-in and form attempts.
We do not use your information to advertise to you, and we do not build a profile of what you read.
Accounts and Covenant OS
A free account on churchposting.com uses a Covenant OS login. When you sign in, Covenant OS sends us your identifier, your email address and your name. We store those three, and nothing else comes from Covenant OS. If an older Church Posting account used the same verified email address, we join its saved work to your login.
Press "Set up your church in Covenant OS" and we send Covenant OS a signed message, good for five minutes, with your identifier and, if you have claimed a church here, that church's directory name, city, state and claim status. Nothing goes until you press the button.
Documents, lists and saved items you keep in a signed-in account are stored on our service. A share link makes one list readable by anyone who has the link. A shared list carries no name, email address or account identifier. A hymn's "churches singing this" count appears only when at least three accounts have shared a list with that hymn, and it counts accounts without naming them. Taking the link down removes the list from that count.
Your browser
The free tools run in your browser. A bulletin, slide deck, directory, certificate, funeral program, giving statement, calendar or song sheet you build is saved in your browser's local storage on your own device, and photographs you add stay in the browser. We never receive that work unless you are signed in and save it to your account. Clearing your browser's site data erases it.
Hymn pages that list videos show a small thumbnail from YouTube's image server when it scrolls into view. The video itself loads only when you press play, from YouTube's privacy-enhanced address. Fonts and scripts load from churchposting.com.
Church websites we read
We build the church finder and the job board by reading public church websites, the careers pages churches publish, and the hiring systems those pages link to. We do not copy listings from commercial job boards. Our reader identifies itself as ChurchPostingBot, reads a site's robots.txt first and follows it, and asks for at most one page a second from a host. It collects what a church publishes about itself, such as its name, address, phone number and service times, and the details of a job a church advertises. It does not log in anywhere or read private pages.
When you post a job, the same reader opens the home page of the church website you entered and up to six pages it links to, such as beliefs, about and staff pages, to run the automatic check against the listing standard. It saves the lines that decided the check with the posting.
A church that wants its page or a job listing corrected or taken down can use the contact form or write to hello@churchposting.com.
Job seekers and hiring churches
These records exist only when you use the job board's account features. Each row says what we store, who sees it, how long we keep it and how to delete it. Our service deletes old records every day on the schedule below.
| Record | What we store and who sees it | How long, and how to delete it |
|---|---|---|
| Your ministry profile | Your name, headline, place, state, the roles you want, the confessions you hold, a beliefs note, your ministry experience, education, links and references, and your two search choices. You see all of it. A church you apply to gets a copy. If you choose "Show my profile to churches searching for candidates", churches with an approved claim see your name, headline, place, roles, confessions and experience, and your email address only if you also choose to show it. Candidate search never shows your references. | Until you delete it. Press Delete my profile on your profile page, or delete your account. |
| References you list | The name, how they know you, and the email address and phone number you give for each reference. These are other people's details: list only people who agreed to be contacted. References go only to the church behind each job you apply to, through its applicant inbox and the application address it lists. Candidate search and invitations never show them. | In your profile until you remove them. In each application for 2 years, as part of that application. |
| Applications you send | The job, the church, your account email address, a copy of your profile at the moment you apply, your note, the stage the church sets, and the church's notes and replies. Only that church sees it: an account holder with an approved claim on the church or the job, the person who posted the job, and the search committee members they add by email. If the church lists an application address, a copy goes there by email. No other church sees it. You see each application and its stage in your account. A church's internal notes stay with the church. | 2 years from the day you apply, then deleted with the church's notes and replies. Deleting your account deletes them at once. An email copy already delivered stays in the church's own inbox, and the church answers for it. |
| Invitations to apply | When a church with an approved claim invites you from candidate search: the church, the job if it names one, and its message. You see them in your account. | 1 year, or until you delete your account. Turn off "Show my profile to churches searching" to stop new ones. |
| Shared job links | When someone opens a job through a shared link, we store the job, the day, and a salted hash: of the account for a signed-in visitor, or of the IP address and browser for a signed-out visitor who passes the Cloudflare Turnstile check, which sends Cloudflare signals from the browser. We never store the address or the account itself. The count adds to the job's Featured points, and no one sees who visited. A counter keyed by a hash of the IP address limits how many visits one address can add in a day. | 180 days. The counter is deleted within two days. Deleting your account deletes the visits you made signed in. |
| Church accounts | For a church with an approved claim: the church profile it writes (photo links, service times, beliefs, staff names and roles, what to expect, attendance), which shows on the church's public page. Photo links show only after we approve them. Also the email addresses of the committee members it seats, which only that church sees, and pay or inbox changes to jobs it claimed. | Until the church changes or removes them. Write to hello@churchposting.com to remove a church profile. A committee member who deletes their own account loses the seat. |
| Church invitations | When a church invites another church to claim its listing: the invited church's name and the email address entered, and the inviting church. We use them to count the invitation once that church claims its listing. Invitation emails go out only when we turn that sending on. | 2 years. An invited church can write to hello@churchposting.com to have its address removed sooner. |
A church sees an application through a current approved claim on that church or job, or a committee seat granted by that claimant. Profile applications to posted jobs open once the poster has an approved claim. Until then, use the church's external application link. We check ownership against the church website already in our records. A typed church name or website gives no access to another job's applicants.
How long we keep it
- A sign-in session lasts 10 minutes. A sign-in in progress lasts 10 minutes. A claim cookie lasts 24 hours. Our service deletes expired sessions, sign-in records and claim receipts every day.
- We keep a salted IP hash with each email consent capture. Each day we remove hashes from consent records at least 90 days old. Copies in private backups remain for up to another 90 days, until those backups expire. We keep the consent text and date after removing the hash.
- We delete network and ordinary per-address counters within two days. We keep the per-address counter for settings links to stopped addresses for up to 60 days, so a new month does not reset the limit early.
- A signed-in person's saved work stays until the person deletes it or deletes the account.
- Form records (the weekly email, job emails, beta and launch lists, contact messages, church claims and job posts) stay until you ask us to delete them or the purpose ends. We do not set a shorter fixed period today.
- Your unsubscribe record, with your address, the time and how you unsubscribed, stays so we never email that address again. A signup you make on purpose removes it.
- A job we found on a church site stays listed while the church lists it. A closed job keeps its page for 180 days, marked closed.
Your choices
Delete a signed-in account. Open your account, choose Delete account and type DELETE. That removes your documents, lists, saved items and hymn-sharing rows, ends your sessions on every device, detaches your church claims from your login and deletes your account record here. Your Covenant OS login stays active.
Everything else. Write to hello@churchposting.com from the address in question and tell us what you want. We send you what we hold, correct it, or delete it, including the contact record in GoHighLevel and any contact messages you sent.
Stop emails. Every list email carries an unsubscribe link. It opens a page with one button, and one click stops every Church Posting list email to that address, including the weekly email and the jobs email. A sign-in or a message you send us is not affected. Emails about a job you posted (received, live, declined) answer what you did and carry no unsubscribe link. If a link does not work, write to us from the address and we remove it by hand.
A church page. If your church's page is wrong, or you want it removed, write to us and we correct or remove it. A removed page answers with a 410 Gone notice.
Children
The site is written for adults and is not directed to children under 13. We do not knowingly collect information from them. If we learn that we hold a child's personal information, we delete it, and no later than 30 days after we learn of it.
Change history
- Added job seekers and hiring churches: ministry profiles, the references in them, one-click applications, candidate search, church profiles, committee seats, church invitations and shared job links, with who sees each, how long we keep it and how to delete it.
- Rewritten against what the site does. Added the data we hold by form, cookies by name, retention, saved work and shared lists, and the church websites we read. Added the contact form, unsubscribe, job postings that publish automatically, saved job searches, the service providers in use and what we do with the information of a child. Church Posting is named as the maker of the free tools and every product.
- Added sign-in with Covenant OS.