Transparency alternatives to Precisely
Other Data catalogs and governance vendors we measure, sorted by how much we found at them and not at Precisely. This is a comparison of disclosure, not of features or fitness.
12 shown of 24 that differ from Precisely on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Precisely has 8 gaps in what we could measure: Data processing agreement, Data location stated, 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 Precisely” is the one that closes them.
| Vendor | Score | Found there, not found at Precisely | Found at Precisely, not found there | |
|---|---|---|---|---|
| Privaceraprivacera.comSee also Transparency alternatives to Privacera | 57/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 3 Subprocessor list, security.txt (RFC 9116), Named privacy contact | Compare |
| Metaplanemetaplane.devSee also Transparency alternatives to Metaplane | 61/100 | 4 Data location stated, Public pricing, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Anomaloanomalo.comSee also Transparency alternatives to Anomalo | 52/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Bigeyebigeye.comSee also Transparency alternatives to Bigeye | 48/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Satorisatoricyber.comSee also Transparency alternatives to Satori | 43/100 | 3 Data location stated, HTTPS enforced with HSTS, No third-party tracking before consent | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Immutaimmuta.comSee also Transparency alternatives to Immuta | 39/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Lightuplightup.aiSee also Transparency alternatives to Lightup | 35/100 | 3 Data processing agreement, Data location stated, Notice before subprocessors change | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Validiovalidio.ioSee also Transparency alternatives to Validio | 30/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | Compare |
| Varonisvaronis.comSee also Transparency alternatives to Varonis | 30/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | Compare |
| Acceldataacceldata.ioSee also Transparency alternatives to Acceldata | 26/100 | 3 Data location stated, Certifications named, HTTPS enforced with HSTS | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Colectica Repositorycolectica.comSee also Transparency alternatives to Colectica Repository | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 4 Subprocessor list, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Datagalaxydatagalaxy.comSee also Transparency alternatives to Datagalaxy | 22/100 | 2 Data location stated, Certifications named | 3 Subprocessor list, Status page with history, security.txt (RFC 9116) | 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.