On the other hand, the OCR.space OCR API has a very strict privacy policy:
https://ocr.space/privacypolicy - All uploaded images and the extracted text are deleted immediatly after processing.
Until they are served with a subpoena for a particular client, or a sweeping subpoena to store everything forever, or the company is sold and the new parent has different values, or the company decides to mine customer data for advertising uses, or there's a bug in the software, or there's a long-lived cache of the data, or it gets into their backups accidentally or deliberately, or they don't keep the data but keep "just" the meta-data, or they do statistics or analytics before deleting the data, or they are hacked, or they simply change their minds.
In terms of privacy, even a non-free non-open-source local app with DRM or license management is better than a server app with a "strict privacy policy". With a good firewall setup, you can be pretty sure that the local app won't betray you.
http://www.daemonology.net/blog/2012-01-19-playing-chicken-w...
You mean that we have to place some trust that they are. Some users cannot afford that kind of trust.
Personally, I chose .space simply because it's cool, cheap, and not overcrowded. It also seems to lend itself well to being part of a name.
I know spam is a hard problem, but I wish you wouldn't label me a spammer simply because of the TLD I chose.
There are a few others which you may want to avoid according to this report: https://securityintelligence.com/enticing-clicks-with-spam/
> Why did you end up going with a .space domain? We blocked that whole TLD because we were getting massive amounts of spam from it when it first came out.
From your comment:
> I know spam is a hard problem, but I wish you wouldn't label me a spammer simply because of the TLD I chose.
The author is not "labeling you a spammer". They're simply stating a fact about their experience. And in fact, it doesn't even mention you.