Transparency alternatives to ROC-P
Other Association management vendors we measure, sorted by how much they publish that ROC-P does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 34 that differ from ROC-P on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ROC-P has 10 gaps in what we could measure: Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and ROC-P does not” is the one that closes them.
| Vendor | Score | Publishes, and ROC-P does not | ROC-P publishes, and they do not | |
|---|---|---|---|---|
| TidyHQtidyhq.com | 43/100 | 6 Data location stated, Public pricing, Certifications named, +3 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Wild Apricotwildapricot.com | 70/100 | 5 Subprocessor list, Data location stated, Public pricing, +2 | nothing | Compare |
| GrowthZonegrowthzone.com | 35/100 | 4 Data location stated, Status page with history, HTTPS enforced with HSTS, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Membermeistermembermeister.com | 35/100 | 4 Data location stated, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Amiliaamilia.com | 30/100 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Rakletraklet.com | 39/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 1 Data processing agreement | Compare |
| Novi AMSnoviams.com | 30/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Nimble AMSnimbleams.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| YourMembershipyourmembership.com | 26/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Class Managerclassmanager.com | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Fontevafonteva.com | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Jackrabbitjackrabbitclass.com | 17/100 | 2 Status page with history, Public pricing | 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.