Transparency alternatives to BakedBot
Other Cannabis retail and compliance vendors we measure, sorted by how much we found at them and not at BakedBot. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from BakedBot on at least one criterion we measured for both. Public transparency score, not a product or security rating.
BakedBot has 9 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. The column “Found there, not found at BakedBot” is the one that closes them.
| Vendor | Score | Found there, not found at BakedBot | Found at BakedBot, not found there | |
|---|---|---|---|---|
| Flowhubflowhub.comSee also Transparency alternatives to Flowhub | 39/100 | 3 Data location stated, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Weedmapsweedmaps.comSee also Transparency alternatives to Weedmaps | 35/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Covacovasoftware.comSee also Transparency alternatives to Cova | 26/100 | 2 Data location stated, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Greenlinegetgreenline.coSee also Transparency alternatives to Greenline | 26/100 | 2 Data location stated, Public pricing | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| IndicaOnlineindicaonline.comSee also Transparency alternatives to IndicaOnline | 26/100 | 2 Data location stated, Public pricing | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| LeafLinkleaflink.comSee also Transparency alternatives to LeafLink | 22/100 | 2 Data location stated, Public pricing | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Trymtrym.ioSee also Transparency alternatives to Trym | 22/100 | 2 Data location stated, Public pricing | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| BLAZEblaze.meSee also Transparency alternatives to BLAZE | 9/100 | 2 Certifications named, Uptime SLA with a figure | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Distrudistru.comSee also Transparency alternatives to Distru | 22/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| POSaBITposabit.comSee also Transparency alternatives to POSaBIT | 22/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| AIQaiq.comSee also Transparency alternatives to AIQ | 17/100 | 1 Certifications named | 1 security.txt (RFC 9116) | Compare |
| Canixcanix.comSee also Transparency alternatives to Canix | 17/100 | 1 Status page with history | 2 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.