Transparency alternatives to Relecura
Other Patent and trademark management vendors we measure, sorted by how much we found at them and not at Relecura. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Relecura on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Relecura has 10 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, 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 Relecura” is the one that closes them.
| Vendor | Score | Found there, not found at Relecura | Found at Relecura, not found there | |
|---|---|---|---|---|
| PatSnappatsnap.comSee also Transparency alternatives to PatSnap | 52/100 | 5 Status page with history, Certifications named, HTTPS enforced with HSTS, +2 | nothing | Compare |
| Doppeldoppel.comSee also Transparency alternatives to Doppel | 50/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| IPRallyiprally.comSee also Transparency alternatives to IPRally | 48/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| PatentBotspatentbots.comSee also Transparency alternatives to PatentBots | 48/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| Wellspringwellspring.comSee also Transparency alternatives to Wellspring | 48/100 | 4 Subprocessor list, Status page with history, HTTPS enforced with HSTS, +1 | 1 Public pricing | Compare |
| TechInsightstechinsights.comSee also Transparency alternatives to TechInsights | 32/100 | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | 2 Data location stated, Public pricing | Compare |
| Amplifiedamplified.aiSee also Transparency alternatives to Amplified | 43/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | nothing | Compare |
| Corsearchcorsearch.comSee also Transparency alternatives to Corsearch | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 2 Data location stated, Public pricing | Compare |
| Nameshieldnameshield.comSee also Transparency alternatives to Nameshield | 17/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Data location stated, Public pricing | Compare |
| EBRANDebrand.comSee also Transparency alternatives to EBRAND | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 1 Public pricing | Compare |
| Questelquestel.comSee also Transparency alternatives to Questel | 22/100 | 2 Subprocessor list, Notice before subprocessors change | 2 Data location stated, Public pricing | Compare |
| MyMediaboxmymediabox.comSee also Transparency alternatives to MyMediabox | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data location stated, 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.