[relics443]

My point is, I have no clue what's collecting data in an improper way, and I'm not going to hire a lawyer for a hobby app.

The amount of conflicting information about whether I do or don't need consent based on what services I use is just stupid. And I wouldn't even be showing ads.

Part of the apps function is related to location, do I need consent? Maybe.

It will use Firebase, do I need consent? Maybe.

It will collect crash data so I can debug the stupid thing, do I need consent? Maybe.

Etc...

[hekfu]

Welcome to the real world. If your little hobby project leaks the personal information of a real person, then they don't care how much of an unimportant side project it was to you.

For purely personal use "hey guys, this is just a hobby use at your own risk" you won't get hit with gdpr

Imagine if you were building cars for a hobby then selling them. Would you complain about all of those onerous regulations like seatbelts, crunch zones etc when all zou really want to do is tinker with some cool engine tech?

[relics443]

I don't see what leaking personal information has to do with collecting crash data, or using Google's infrastructure to store my data. Why should I have to be on the hook for what is most definitely much safer than trying to safeguard the data myself?

Like I said, all it will accomplish is discouraging projects like mine that aim to provide utility to some people. One of my released hobby apps is no great commercial success (I don't show ads or collect revenue), but it's one of the top rated apps in its category on the Play Store, and I have about 20k DAU.

If the GDPR ever came after me for it, I'd just take the app down. Bam, 20k people a day affected because of over regulation.

Also, I wouldn't equate personalized ads with the life and death regulations involved in the auto industry.