Hacker News new | ask | show | jobs
by jrochkind1 1953 days ago
It's weird if the policy is you can do whatever you want as powerful as you want if you roll your own, but you can't do anything no matter how simple if you use a free third-party SDK, but... is that what it looks like?
1 comments

No sorry, that isn't it at all but it's easy to see how you would think so.

You can do whatever tracking you like, however you like using whatever SDK you like, as long as you obey basically two rules:

* If you are tracking identifiable information you must present an opt-in dialog. It doesn't matter if you roll your own or use an SDK to do it.

* If you are doing 3rd party tracking, and generally these SDKs are designed to do that, you must indicate this in the App's privacy information.

Honestly, that's all there is to it. The whole article, and the "de-factor ban' narrative being pushed so hard on this forum are predicated on the assumption that doing either of these things is simply inconceivable. However if you are willing to do them, all the restrictions melt away. It's really as simple as that. Ask the users and tell them the truth. That's all that's being required.

The only complications come if you want to weasel your way out of doing these things. That's why the blog post author, and the 'de-facto ban' crowd here think this is such a fiendishly difficult problem.