Transparency alternatives to Bdo Digital
Other Document AI and data capture vendors we measure, sorted by how much we found at them and not at Bdo Digital. This is a comparison of disclosure, not of features or fitness.
12 shown of 39 that differ from Bdo Digital on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Bdo Digital has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Bdo Digital” is the one that closes them.
| Vendor | Score | Found there, not found at Bdo Digital | Found at Bdo Digital, not found there | |
|---|---|---|---|---|
| Parseurparseur.comSee also Transparency alternatives to Parseur | 65/100 | 6 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +3 | 1 Status page with history | Compare |
| Hypatoshypatos.aiSee also Transparency alternatives to Hypatos | 65/100 | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Formxformx.aiSee also Transparency alternatives to Formx | 57/100 | 5 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +2 | 2 Status page with history, Certifications named | Compare |
| Docsumodocsumo.comSee also Transparency alternatives to Docsumo | 52/100 | 5 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +2 | 2 Status page with history, Public pricing | Compare |
| Anyrowanyrow.aiSee also Transparency alternatives to Anyrow | 48/100 | 5 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +2 | 2 Status page with history, Certifications named | Compare |
| Mindeemindee.comSee also Transparency alternatives to Mindee | 57/100 | 4 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Nanonetsnanonets.comSee also Transparency alternatives to Nanonets | 57/100 | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | 1 Certifications named | Compare |
| Deepsetdeepset.aiSee also Transparency alternatives to Deepset | 39/100 | 4 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 2 Status page with history, Certifications named | Compare |
| Affindaaffinda.comSee also Transparency alternatives to Affinda | 63/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Public pricing | Compare |
| Veryfiveryfi.comSee also Transparency alternatives to Veryfi | 48/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | nothing | Compare |
| Upstageupstage.aiSee also Transparency alternatives to Upstage | 43/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Certifications named | Compare |
| Abbyyabbyy.comSee also Transparency alternatives to Abbyy | 39/100 | 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | 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.