SaaS Ranking

Alternatives to Tillhub

Other Retail point of sale vendors we measure, sorted by how much they publish that Tillhub does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 13 that differ from Tillhub on at least one criterion we measured for both. Public transparency score, not a product or security rating.

Tillhub has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Tillhub does not” is the one that closes them.

VendorScorePublishes, and Tillhub does notTillhub publishes, and they do not
Kassensichvfiskaly.com 35/100 2 Data location stated, Status page with history 1 security.txt (RFC 9116) Compare
Hikehikeup.com 30/100 2 Data location stated, Public pricing 2 security.txt (RFC 9116), Named privacy contact Compare
Ls Retaillsretail.com 22/100 1 Data location stated 2 security.txt (RFC 9116), Named privacy contact Compare
Efstaefsta.eu 17/100 1 Status page with history 2 security.txt (RFC 9116), Named privacy contact Compare
Epsonposepson.de 17/100 1 Data location stated 2 HTTPS enforced with HSTS, security.txt (RFC 9116) Compare
Orishaorisha.com 9/100 1 No third-party tracking before consent 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact Compare
Ccvccv.eu 14/100 nothing we found there and not here nothing Compare
Payonepayone.com 13/100 nothing we found there and not here 1 Named privacy contact Compare
Anybillanybill.de 9/100 nothing we found there and not here 2 security.txt (RFC 9116), Named privacy contact Compare
Helloclayhelloclay.de 9/100 nothing we found there and not here 2 security.txt (RFC 9116), Named privacy contact Compare
Ncr Counterpointncr.com 9/100 nothing we found there and not here 2 security.txt (RFC 9116), Named privacy contact Compare
NewPOSnewpos.ai 0/100 nothing we found there and not here 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact 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.