Congregation records and prayer walls

Did that prayer request go public?

Church plugins store member directories, prayer requests, sermon and people pages, and sometimes attendance or giving history. A prayer wall can publish a name next to health or family details. Religious-affiliation data can be treated as a special category under privacy laws in some places. This page is not legal advice. Giving forms and paywalled memberships have separate pages. Compare the documented setups below.

Based on plugin documentation, not tests of your site. Prayer publish settings, directory privacy flags, and retention decide what outsiders can see. This is not legal advice or a compliance rating.

Scan your site for third-party requests

This scan checks requests made by a visitor's browser on a church page, including maps, sermon players, CAPTCHA, or giving embeds when they load. It does not inspect member databases, prayer archives, or giving history stored only on the server, test directory access controls, or assess how long records remain after someone leaves.

Public prayer walls vs gated member records

Records stored on your WordPress site

Check whether prayer requests publish after moderation, stay private to staff, or allow anonymous display. Review member-directory shortcodes and map widgets for which names, phones, or addresses appear. Check how long prayer archives and directory records remain after someone leaves the congregation.

Hosted church apps and outside connectors

Some setups email a prayer chain, push to a church app, load maps or CAPTCHA in the browser, or send giving details to a payment processor. Server-side member and giving storage does not appear in a browser page scan. Review each hosted app, email path, and processor before you publish directory or prayer pages. Donation processors are covered on the donation privacy page.

Church setups

No paid placement. Site-hosted church tools appear first, followed by any vendor-connector group, then unreviewed rows. Site-hosted tools may still use outside CAPTCHA, maps, email, apps, or payment services when enabled. Review prayer-name display and directory fields separately. Names are alphabetical within each group.

SetupDocumented behaviorVisitor-browser hostsHow long data is keptBefore consentLinksSource
Church Admin

Documented self-hosted membership database and church directory with privacy settings. Address-list and map shortcodes can show member details on the front end when placed. Prayer requests are saved as drafts for staff review. Published requests are public and searchable unless the private option is enabled; that option requires members to log in to view requests or submit a new one. Publishing can also distribute requests through the prayer-chain email and church app. Moderation alone does not restrict who can see a published request. Review directory privacy flags, which member fields appear on maps or lists, prayer publish settings, and any premium app or email distribution. Browser hosts were not verified for this snapshot.

Congregation records stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Church Content

Documented self-hosted post types for sermons, events, people, and locations. Compatible themes present that content on the front end. Review which people and location fields you publish, whether speaker pages expose contact details, and how long archived sermons and people profiles remain public. Browser hosts were not verified for this snapshot.

Congregation records stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None
Intercessor

Documented self-hosted prayer requests with moderation, anonymous display (name hidden), and private requests visible only to administrators and prayer managers. Listing says data stays in local database tables except optional Google reCAPTCHA. When reCAPTCHA is enabled, the form page loads Google scripts and verification can contact www.google.com; prayer text is not sent to Google per the listing. Review private vs public settings, login gates, Prayer Wall blocks, exports, and reCAPTCHA. Other browser hosts were not verified for this snapshot.

Congregation records stored on your WordPress sitewww.google.comNot assessedNot tested
  • None
PrayerPop

Documented self-hosted prayer and testimony submissions stored as WordPress posts for admin review. Free workflow keeps submissions in a private inbox until staff act; the listing says public prayer walls and testimony displays are part of PrayerPop Pro. Optional visitor Chat stores name, reply email, and messages in local tables and uses an HTTP-only cookie so the same browser can return. Email notifications use your WordPress mail path. Review whether Pro public walls are enabled, Chat retention settings, and which fields visitors must provide. Browser hosts were not verified for this snapshot.

Congregation records stored on your WordPress siteBrowser hosts not verifiedNot assessedNot tested
  • None

What this table does and does not prove

This table describes documented church workflows, not tests of your site. Consent timing, live prayer-wall exposure, directory access strength, and retention lengths have not been assessed. Check prayer publish settings, directory privacy flags, member fields, and any app, email, map, or giving connectors. Donation forms and paywalled memberships are covered on their own pages.

Documentation snapshot: Oct 8, 2026. Sources are linked in each reviewed row.

Related pages

Scan your site for third-party requests

/wp-church-plugin-privacy