• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Creating Privacy Policy for Super-Simple App

I am trying to submit to Google Play a rather simple app my daughter made in class, sort of a cute little “game” that plays by itself, made with MIT App Inventor, so it can be downloaded for free. I am finding that the submission console won’t let me submit an app which kids could be interested in without a privacy policy. But this is just a simple app that doesn’t collect any information of any sort, contact the internet, or even interact with the user, so I have no idea what a privacy policy is supposed to mean. Nor do I have a web site to put such a policy on. I tried to figure what to write and where to post it, but it was rejected for lacking an adequate privacy policy, they I don’t see any feedback on how to make a privacy policy that would be accepted.

I tried to share it from my google drive with the text


The Pleasant Bouncing Balls game does not collect or store any personal information.
Hey there, I've released a few apps so I can speak to this. Any time you release an app and have ages 13 or under selected as the target audience google will demand a privacy policy. Generally app store restrictions are increased as you select a lower age range. Because of this many devs just say all of their apps are 18+. That's what I do as well. It doesn't show to the user that it's only for "18+" but it won't appear to younger users (as far as I know).

However, if you want to get your daughter's app to a younger audience then you'll just need to make a privacy policy. Legally I can't tell you how to do that as I am not a lawyer. However, I know some developers make their privacy policy with policy generators online. You could probably find one by just googling around.

Then you could just copy and paste that policy text into a "Google Sites" document. Google Sites allows you to make a website easily. It'll give you a URL and you could give that URL to google play.

Once again, I'm not a lawyer haha, so that might not be the "safest" option legally. If you google around though and explore r/androiddev you'll see that a bunch of other people have dealt with this problem for small project apps like yours. They might have more advice for you there.
Upvote 0


We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.