Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Let's put it in simple CRUD terms. Users want to:

C - control when you collect it.

R - read what you have on them, and know how you read it and/or share it with others.

U - update it, e.g. when it is wrong.

D - delete it.

Most users just want non-hostile defaults, but all users should have CRUD-control.



I'm not sure why this is downvoted - it's a little bit counter to the scope of the parent article, which applies to all sorts of design decisions, not just data retention and usage, but I would agree that this /is/ the base level of control over any data that a third party has from me and should be enshrined in law.

It has been great to see Apple, for example, move more towards better awareness and defaults for C, but by and large the internet is still a mess of hostile defaults, opaque privacy statements, and no way to know that this weather app is selling your location to advertisers when they could've just asked you for your location, if they wanted to be a weather app.




Consider applying for YC's Winter 2027 batch! Applications are open till November 2.

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

Search: