Transparency alternatives to Camp Systems
Other Aviation maintenance software vendors we measure, sorted by how much we found at them and not at Camp Systems. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Camp Systems on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Camp Systems has 10 gaps in what we could measure: Data processing agreement, 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), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Camp Systems” is the one that closes them.
| Vendor | Score | Found there, not found at Camp Systems | Found at Camp Systems, not found there | |
|---|---|---|---|---|
| Swiss Aviationswiss-as.comSee also Transparency alternatives to Swiss Aviation | 41/100 | 4 Data location stated, Certifications named, No third-party tracking before consent, +1 | 1 Subprocessor list | Compare |
| Web Manualswebmanuals.aeroSee also Transparency alternatives to Web Manuals | 39/100 | 4 Public pricing, Certifications named, Notice before subprocessors change, +1 | 1 HTTPS enforced with HSTS | Compare |
| Fl3xxfl3xx.comSee also Transparency alternatives to Fl3xx | 35/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 1 Subprocessor list | Compare |
| Foreflightforeflight.comSee also Transparency alternatives to Foreflight | 26/100 | 3 Data location stated, Public pricing, Named privacy contact | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Comply365comply365.comSee also Transparency alternatives to Comply365 | 22/100 | 3 Data location stated, Certifications named, Named privacy contact | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Veryonveryon.comSee also Transparency alternatives to Veryon | 26/100 | 2 Data location stated, Named privacy contact | 1 Subprocessor list | Compare |
| AeroSightaero-sight.comSee also Transparency alternatives to AeroSight | 22/100 | 2 No third-party tracking before consent, security.txt (RFC 9116) | 1 Subprocessor list | Compare |
| Skylegsskylegs.comSee also Transparency alternatives to Skylegs | 13/100 | 2 Public pricing, Named privacy contact | 2 Subprocessor list, HTTPS enforced with HSTS | Compare |
| Lidolhsystems.comSee also Transparency alternatives to Lido | 17/100 | 1 No third-party tracking before consent | 1 Subprocessor list | Compare |
| Aviation Intertecaviationintertec.comSee also Transparency alternatives to Aviation Intertec | 13/100 | 1 Certifications named | 1 Subprocessor list | Compare |
| BARTbart.aeroSee also Transparency alternatives to BART | 13/100 | 1 Named privacy contact | 1 Subprocessor list | Compare |
| Portsideportside.coSee also Transparency alternatives to Portside | 13/100 | 1 Named privacy contact | 1 Subprocessor list | 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.