4 ms·

Just like StreetLend, most likely nothing, and it's just a fear, but again you need to realize that this is a site run purely as a hobby. I'm sorry but reading

Just like StreetLend, most likely nothing, and it's just a fear, but again you need to realize that this is a site run purely as a hobby. I'm sorry but reading through legalese and combing my website's code to make sure it's compliant isn't part of my hobby. I'm not a company, I don't have millions of users, I just run a small tool that a few people use. Yet apparently I run the risk of being fined $20m...

joosters 9y ago
You already had to comply with many other complex laws, like copyrights, trademarks and so on. I don’t see why a privacy law is anything different or special.
- closeparen 9y ago
  >many other complex laws It takes 30 seconds to find out whether your identifier violates a trademark. Your content is trivially not a copyright violation if you created it yourself. Hobby projects are not debating the finer points of fair use and whether the conflicting name is for a sufficiently different kind of business to avoid confusion. But every HTTP server handles personal data, and a web-based tool with a database backend especially so, so all the subtlety of GDPR is in play.
  - outsideoflife 9y ago
    > But every HTTP server handles personal data But not all of them have a good reason to log it. /dev/null
    - Karunamon 9y ago
      Hard disagree. Abuse prevention, performance metrics. Httpd logs are a basic and necessary tool.
GordonS 9y ago
There are lots of guides out there designed for humans. Essentially, all you have to do is tell your users what data you are collecting and how you will use it. Also, if a user asks for their data, you give it to them, and if a user asks for their data to be deleted, you delete it. I imagine if either of these things were to happen today, you would do as they wished GDPR or not.
- closeparen 9y ago
  >There are lots of guides out there designed for humans. It's not even remotely okay to use random people's blog posts as a compliance strategy.
  - 2trill2spill 9y ago
    Its funny that your being downvoted, but using a random persons blog for legal compliance seems risky.
  - outsideoflife 9y ago
    > There are lots of guides out there designed for humans. > It's not even remotely okay to use random people's blog posts as a compliance strategy. Then use the simple, human friendly guide from the body who will be enforcing it in the UK. I did. I thought it was simple. https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/ https://ico.org.uk/for-organisations/guide-to-the-general-da...
salvar 9y ago
If you think a hobby app runs a risk of being fined $20m then you clearly haven't looked into this at all. Why don't you do that first before getting worried about it?

joosters 9y ago

You already had to comply with many other complex laws, like copyrights, trademarks and so on. I don’t see why a privacy law is anything different or special.

closeparen 9y ago
>many other complex laws It takes 30 seconds to find out whether your identifier violates a trademark. Your content is trivially not a copyright violation if you created it yourself. Hobby projects are not debating the finer points of fair use and whether the conflicting name is for a sufficiently different kind of business to avoid confusion. But every HTTP server handles personal data, and a web-based tool with a database backend especially so, so all the subtlety of GDPR is in play.
- outsideoflife 9y ago
  > But every HTTP server handles personal data But not all of them have a good reason to log it. /dev/null
  - Karunamon 9y ago
    Hard disagree. Abuse prevention, performance metrics. Httpd logs are a basic and necessary tool.

GordonS 9y ago

There are lots of guides out there designed for humans. Essentially, all you have to do is tell your users what data you are collecting and how you will use it. Also, if a user asks for their data, you give it to them, and if a user asks for their data to be deleted, you delete it. I imagine if either of these things were to happen today, you would do as they wished GDPR or not.

closeparen 9y ago
>There are lots of guides out there designed for humans. It's not even remotely okay to use random people's blog posts as a compliance strategy.
- 2trill2spill 9y ago
  Its funny that your being downvoted, but using a random persons blog for legal compliance seems risky.
- outsideoflife 9y ago
  > There are lots of guides out there designed for humans. > It's not even remotely okay to use random people's blog posts as a compliance strategy. Then use the simple, human friendly guide from the body who will be enforcing it in the UK. I did. I thought it was simple. https://ico.org.uk/for-organisations/guide-to-the-general-data-protection-regulation-gdpr/ https://ico.org.uk/for-organisations/guide-to-the-general-da...

salvar 9y ago

If you think a hobby app runs a risk of being fined $20m then you clearly haven't looked into this at all. Why don't you do that first before getting worried about it?