Transparency alternatives to Acodei
Other Accounting vendors we measure, sorted by how much they publish that Acodei does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 66 that differ from Acodei on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Acodei has 7 gaps in what we could measure: Data location stated, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact. The column “publishes and Acodei does not” is the one that closes them.
| Vendor | Score | Publishes, and Acodei does not | Acodei publishes, and they do not | |
|---|---|---|---|---|
| Odooodoo.com | 48/100 | 5 Data location stated, Status page with history, HTTPS enforced with HSTS, +2 | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| AccountKitaccount-kit.com | 61/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 No third-party tracking before consent, Notice before subprocessors change | Compare |
| Xeroxero.com | 36/100 | 3 Data location stated, Status page with history, Certifications named | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Zervantzervant.com | 36/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Clear Booksclearbooks.co.uk | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| FreeAgentfreeagent.com | 30/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Billbill.com | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Billomatbillomat.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Meliomelio.com | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Subprocessor list, No third-party tracking before consent, +1 | Compare |
| Candiscandis.io | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Fortnoxfortnox.se | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| Papierkrampapierkram.de | 22/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | 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.