Transparency alternatives to Tegos
Other Waste management software vendors we measure, sorted by how much we found at them and not at Tegos. This is a comparison of disclosure, not of features or fitness.
12 shown of 31 that differ from Tegos on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Tegos has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Tegos” is the one that closes them.
| Vendor | Score | Found there, not found at Tegos | Found at Tegos, not found there | |
|---|---|---|---|---|
| Ecoprogecoprog.comSee also Transparency alternatives to Ecoprog | 30/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Rubiconrubicon.comSee also Transparency alternatives to Rubicon | 30/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Resourcifyresourcify.deSee also Transparency alternatives to Resourcify | 26/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Sap Wasteprologa.deSee also Transparency alternatives to Sap Waste | 26/100 | 1 HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Wasteboxwastebox.bizSee also Transparency alternatives to Wastebox | 26/100 | 1 No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Landbelllandbell.deSee also Transparency alternatives to Landbell | 13/100 | 1 HTTPS enforced with HSTS | 2 Data location stated, security.txt (RFC 9116) | Compare |
| AMCSamcsgroup.comSee also Transparency alternatives to AMCS | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Basestationthebasestation.comSee also Transparency alternatives to Basestation | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Cyclizecyclize.deSee also Transparency alternatives to Cyclize | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Der Gruene Punktgruener-punkt.deSee also Transparency alternatives to Der Gruene Punkt | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Enevoenevo.comSee also Transparency alternatives to Enevo | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | Compare |
| Interzerointerzero.deSee also Transparency alternatives to Interzero | 9/100 | 1 HTTPS enforced with HSTS | 3 Data location stated, security.txt (RFC 9116), 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.