Transparency alternatives to ZeroNorth
Other Maritime and port operations vendors we measure, sorted by how much we found at them and not at ZeroNorth. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from ZeroNorth on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ZeroNorth has 9 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at ZeroNorth” is the one that closes them.
| Vendor | Score | Found there, not found at ZeroNorth | Found at ZeroNorth, not found there | |
|---|---|---|---|---|
| Veson Nauticalveson.comSee also Transparency alternatives to Veson Nautical | 48/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Data processing agreement, HTTPS enforced with HSTS | Compare |
| Kaleriskaleris.comSee also Transparency alternatives to Kaleris | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Solvermindssolverminds.comSee also Transparency alternatives to Solverminds | 22/100 | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| GISGROgisgro.comSee also Transparency alternatives to GISGRO | 26/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Hanseaticsofthanseaticsoft.comSee also Transparency alternatives to Hanseaticsoft | 26/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| RadiantFleetradiantfleet.comSee also Transparency alternatives to RadiantFleet | 26/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Seasea.liveSee also Transparency alternatives to Sea | 26/100 | 2 Data location stated, Certifications named | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Vortexavortexa.comSee also Transparency alternatives to Vortexa | 26/100 | 2 Subprocessor list, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Awake.AIawake.aiSee also Transparency alternatives to Awake.AI | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Kplerkpler.comSee also Transparency alternatives to Kpler | 22/100 | 2 Status page with history, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Portchainportchain.comSee also Transparency alternatives to Portchain | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Windwardwindward.aiSee also Transparency alternatives to Windward | 22/100 | 2 No third-party tracking before consent, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | 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.