Transparency alternatives to Funeralone
Other Funeral home software vendors we measure, sorted by how much we found at them and not at Funeralone. This is a comparison of disclosure, not of features or fitness.
12 shown of 22 that differ from Funeralone on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Funeralone has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Funeralone” is the one that closes them.
| Vendor | Score | Found there, not found at Funeralone | Found at Funeralone, not found there | |
|---|---|---|---|---|
| Wellthywellthy.comSee also Transparency alternatives to Wellthy | 43/100 | 4 Data location stated, Public pricing, Certifications named, +1 | nothing | Compare |
| Everdayseverdays.comSee also Transparency alternatives to Everdays | 22/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Aeternitasaeternitas.deSee also Transparency alternatives to Aeternitas | 17/100 | 1 No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Passarepassare.comSee also Transparency alternatives to Passare | 17/100 | 1 Status page with history | 1 security.txt (RFC 9116) | Compare |
| Willowwillow.coSee also Transparency alternatives to Willow | 17/100 | 1 Public pricing | 1 security.txt (RFC 9116) | Compare |
| Chroniclechronicle.ripSee also Transparency alternatives to Chronicle | 13/100 | 1 Data location stated | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Osirisosirissoftware.comSee also Transparency alternatives to Osiris | 9/100 | 1 Public pricing | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Srissris.comSee also Transparency alternatives to Sris | 9/100 | 1 No third-party tracking before consent | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Bestattungsvergleichbestattungsvergleich.deSee also Transparency alternatives to Bestattungsvergleich | 4/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Kartdatakartdata.co.ukSee also Transparency alternatives to Kartdata | 4/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Parting Propartingpro.comSee also Transparency alternatives to Parting Pro | 4/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Trauertrauer.deSee also Transparency alternatives to Trauer | 4/100 | 1 Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.