Transparency alternatives to Kartdata
Other Funeral home software vendors we measure, sorted by how much we found at them and not at Kartdata. This is a comparison of disclosure, not of features or fitness.
12 shown of 20 that differ from Kartdata on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Kartdata has 11 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, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “Found there, not found at Kartdata” is the one that closes them.
| Vendor | Score | Found there, not found at Kartdata | Found at Kartdata, not found there | |
|---|---|---|---|---|
| Wellthywellthy.comSee also Transparency alternatives to Wellthy | 43/100 | 5 Data location stated, Public pricing, Certifications named, +2 | nothing | Compare |
| Passarepassare.comSee also Transparency alternatives to Passare | 39/100 | 4 Data location stated, Status page with history, Certifications named, +1 | nothing | Compare |
| Everdayseverdays.comSee also Transparency alternatives to Everdays | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Aeternitasaeternitas.deSee also Transparency alternatives to Aeternitas | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 1 Named privacy contact | Compare |
| Willowwillow.coSee also Transparency alternatives to Willow | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Empathyempathy.comSee also Transparency alternatives to Empathy | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Funeralonefuneralone.comSee also Transparency alternatives to Funeralone | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Named privacy contact | Compare |
| Chroniclechronicle.ripSee also Transparency alternatives to Chronicle | 13/100 | 1 Data location stated | 1 Named privacy contact | Compare |
| Mymoriamymoria.deSee also Transparency alternatives to Mymoria | 9/100 | 1 HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Osirisosirissoftware.comSee also Transparency alternatives to Osiris | 9/100 | 1 Public pricing | 1 Named privacy contact | Compare |
| Plotboxplotbox.ioSee also Transparency alternatives to Plotbox | 9/100 | 1 HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Srissris.comSee also Transparency alternatives to Sris | 9/100 | 1 No third-party tracking before consent | 1 Named privacy contact | 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.