Hacker News new | past | comments | ask | show | jobs | submit login

The data collected is, as mentioned, used to analyze crashes. In case of an error, some information is collected, that can be explained as being justified: device unique ID, to know if an error happened on one device multiple times, IP address is collected in web server access logs, configuration of the app could mean a lot of things, i.e. resolution of the viewport, etc.

If the Privacy Policy contains no mention of sending images to the server and storing the images and/or text contents, then ... it's not happening.

edit: This comment was posted before you edited yours.




If the Privacy Policy contains no mention of sending images to the server and storing the images and/or text contents, then ... it's not happening.

A Privacy Policy is just words in most jurisdictions. Short of a Wireshark analysis, there's no way to know for sure.

I'd rather the program asked if I want to send the crash log the next time I opened it. I have several programs that do that, and I wish it was more widespread.


> A Privacy Policy is just words in most jurisdictions. Not for long. At least in EU.

Well, it's already illegal, it just takes time to prosecute enough data processors until others start being afraid of the fines and start ACTUALLY implementing GDPR.


I don’t feel so concerned about images being sent to the server, but rather the information derived and collected about the images.


If it makes you comfortable, I am not sending text (or any other metadata for images including location, camera fingerprint etc). I plan to add basic analytics to know which views/features are being used and also crash detections.


Again, if it's not mentioned in the Privacy Policy, a sane thing would be to assume it's not being done.

You can be paranoid, but then you shouldn't have a cell phone at all, let alone an always-connected smartphone.


No, its actually insane to take every written statement at its word.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: