Transparency alternatives to Carbonite
Other Backup and recovery vendors we measure, sorted by how much we found at them and not at Carbonite. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from Carbonite on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Carbonite has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 Carbonite” is the one that closes them.
| Vendor | Score | Found there, not found at Carbonite | Found at Carbonite, not found there | |
|---|---|---|---|---|
| SimpleBackupssimplebackups.comSee also Transparency alternatives to SimpleBackups | 52/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 1 Status page with history | Compare |
| Rewindrewind.comSee also Transparency alternatives to Rewind | 48/100 | 4 Subprocessor list, Public pricing, Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Afiafi.aiSee also Transparency alternatives to Afi | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| SpinOnespin.aiSee also Transparency alternatives to SpinOne | 39/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 2 Status page with history, security.txt (RFC 9116) | Compare |
| BorgBaseborgbase.comSee also Transparency alternatives to BorgBase | 39/100 | 3 Data location stated, No third-party tracking before consent, Named privacy contact | 1 Status page with history | Compare |
| Comet Backupcometbackup.comSee also Transparency alternatives to Comet Backup | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| HYCUhycu.comSee also Transparency alternatives to HYCU | 26/100 | 3 Public pricing, Certifications named, Named privacy contact | 2 Status page with history, security.txt (RFC 9116) | Compare |
| SysCloudsyscloud.comSee also Transparency alternatives to SysCloud | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Barracudabarracuda.comSee also Transparency alternatives to Barracuda | 35/100 | 2 Data location stated, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Keepitkeepit.comSee also Transparency alternatives to Keepit | 35/100 | 2 Subprocessor list, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Redstorredstor.comSee also Transparency alternatives to Redstor | 32/100 | 2 Subprocessor list, Notice before subprocessors change | 1 Status page with history | Compare |
| Acronisacronis.comSee also Transparency alternatives to Acronis | 30/100 | 2 Data location stated, Certifications named | 1 Status page with history | 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.