Transparency alternatives to Chronograph
Other Fund administration and private markets vendors we measure, sorted by how much we found at them and not at Chronograph. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from Chronograph on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Chronograph has 8 gaps in what we could measure: Data processing agreement, Data location stated, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Chronograph” is the one that closes them.
| Vendor | Score | Found there, not found at Chronograph | Found at Chronograph, not found there | |
|---|---|---|---|---|
| Affinityaffinity.coSee also Transparency alternatives to Affinity | 70/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | nothing | Compare |
| Intappintapp.comSee also Transparency alternatives to Intapp | 57/100 | 4 Data processing agreement, Public pricing, HTTPS enforced with HSTS, +1 | 2 Certifications named, Notice before subprocessors change | Compare |
| Juniper Squarejunipersquare.comSee also Transparency alternatives to Juniper Square | 48/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Anduinanduintransact.comSee also Transparency alternatives to Anduin | 35/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| Visiblevisible.vcSee also Transparency alternatives to Visible | 52/100 | 3 Data processing agreement, Public pricing, HTTPS enforced with HSTS | 1 Subprocessor list | Compare |
| Fundwavefundwave.comSee also Transparency alternatives to Fundwave | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Subprocessor list, Notice before subprocessors change | Compare |
| Runditrundit.comSee also Transparency alternatives to Rundit | 39/100 | 3 Data processing agreement, Data location stated, Named privacy contact | 3 Subprocessor list, Status page with history, Certifications named | Compare |
| Eddaedda.coSee also Transparency alternatives to Edda | 30/100 | 3 Public pricing, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| 4Degrees4degrees.aiSee also Transparency alternatives to 4Degrees | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 4 Subprocessor list, Status page with history, Certifications named, +1 | Compare |
| Standard Metricsstandardmetrics.ioSee also Transparency alternatives to Standard Metrics | 57/100 | 2 Data processing agreement, HTTPS enforced with HSTS | nothing | Compare |
| Vestlanevestlane.comSee also Transparency alternatives to Vestlane | 22/100 | 2 Data location stated, Named privacy contact | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| AngelListangellist.comSee also Transparency alternatives to AngelList | 17/100 | 2 Public pricing, HTTPS enforced with HSTS | 4 Subprocessor list, Status page with history, Certifications named, +1 | 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.