Funeral and obituary privacy
Where does your online condolence book store names, emails, and messages?
Obituary plugins can store condolence messages on your WordPress site or manage them through a cloud service. This sample compares those documented setups and any flower or memorial-tree sales they describe. Check who can access submissions, which details appear publicly, and what your exports and backups contain.
Based on plugin documentation, not tests of your site. Your collected fields, staff permissions, integrations, exports, and backups affect who can access submissions. This is not legal advice or a compliance rating.
Scan your site for third-party requestsThis scan checks requests made by a visitor's browser on an obituary page, tribute wall, livestream player, or flower/donation widget, including scripts when they load. It does not inspect family-record databases, moderated condolence email tables, vendor flower orders stored only on the server, test staff permissions, or assess whether backups include those tables.
Site-hosted memorials vs cloud assistants
Family and condolence records on your WordPress site
Check which next-of-kin and condolence fields you keep, which roles can open those screens, whether condolence emails appear publicly, and whether exports or backups expose them. Review retention after services end. A remote memorial wall without site-hosted family rows is a different surface.
Cloud obituaries, flowers, and vendor memorials
These plugins manage obituaries through a vendor account or API. Condolences, candles, and flower or memorial-tree purchases may run on the vendor host. Check any separate livestream, donation, or analytics tools you enable. A browser scan cannot inspect vendor family databases or moderated condolence email tables stored only on the server.
Funeral and obituary setups
No paid placement. Site-hosted memorial tools appear first, followed by any vendor-connector group, then unreviewed rows. Vendor tools may still use paid flower or memorial commerce when enabled. Names are alphabetical within each group.
This is a small documentation sample of WordPress funeral-home and memorial plugins, not a survey of every funeral CRM or newspaper obituary desk.
| Setup | Documented behavior | Visitor-browser hosts | How long data is kept | Before consent | Links | Source |
|---|---|---|---|---|---|---|
| ObitMaker Lite Documented Book of Condolences that holds submissions for admin moderation before public display, with email notification on new messages and CSV export of condolence messages. The Privacy section states submissions consist of name, email address, and message; emails are stored in a dedicated database table and are never displayed publicly. Obituary records can also be exported to CSV. No memorial flower or donation checkout path is documented in the Lite package. Retention after services is not documented. Browser hosts have not been verified. | Book of Condolences stores name, email, and message on your site | Browser hosts not verified | Not assessed | Not tested |
| |
| WP Obituary Manager Documented custom obituary post type with a frontend submission form and condolence management. The listing FAQ states condolences are stored as WordPress comments and can be moderated in the admin dashboard. Family-submitted obituaries and visitor condolence text therefore live in the site database when enabled. No memorial flower or donation checkout path is documented in the free package. Retention after services is not documented. Browser hosts have not been verified for this snapshot. | Obituaries and condolences stored on your WordPress site | Browser hosts not verified | Not assessed | Not tested |
| |
| Obituary Assistant Documented cloud assistant: you sign up for an Obituary Assistant account, manage obituaries outside the WordPress login, and the listing states your data is stored and backed up in the cloud. Visitors can leave condolences, share memories, and light candles; flower and memorial-tree purchases are documented revenue paths. Public plugin JavaScript references www.obituary-assistant.com and res.cloudinary.com as visitor-browser hosts. Retention of family contacts, condolences, or flower orders after services is not documented in the WordPress package. | Obituaries and flower commerce handled through Obituary Assistant cloud | www.obituary-assistant.com, res.cloudinary.com | Not assessed | Not tested |
|
What this table does and does not prove
This table describes documented funeral and obituary workflows, not tests of your site. Consent timing, whether access controls work, and exact retention after services have not been assessed. Check which family and condolence fields you collect, who can open those tools, embeds, exports, connectors, and whether backups include those tables when records are site-hosted.
Documentation snapshot: Oct 9, 2026. Sources are linked in each reviewed row.
Related pages
Scan your site for third-party requests/wp-funeral-plugin-privacy