- cross-posted to:
- privacy@lemmy.ml
- cross-posted to:
- privacy@lemmy.ml
cross-posted from: https://lemmy.zip/post/1076839
Archived version: https://archive.ph/zPlSB
Archived version: https://web.archive.org/web/20230805061146/https://themarkup.org/the-breakdown/2023/08/03/how-to-quickly-get-to-the-important-truth-inside-any-privacy-policy
You must log in or register to comment.
I just assume if there is a privacy policy, then the policy is no privacy.
Def the other way around.
Writing a privacy policy generally forces a company to make commitments about what they will and won’t do with data they collect about you.
No privacy policy means anything goes — they didn’t say what they will or won’t do, so you can’t sue them if they do something sketchy.
But many jurisdictions require companies to publish a privacy policy, so just about any company these days will have one. The devil is in the details though, as this article points out.
Eh I figure everything you put online is on a marketplace somewhere. If it’s not the website that sold it, it’s the hackers that stole the data. Even when they claim they don’t store the data there always seems to be a plain text storing backup server that they forgot about. Then there’s data scrapers and 3rd party embedded trackers (looking at you share to Facebook button). And good luck convincing a court that thinks a PC is just a chrome portal that your owed damages for a company leaking your data.
Much easier to control the data at the source and keep websites from getting data in the first place. Trust is long dead online.
