Hide not the money factor. If your application has a charge associated with it - either as part of the initial purchase or within the application itself (for example, buying in-game content, accessories, etc), reveal that the initial point using language clear in the description. Apply a "dummy" test - that his notice of technology-challenged family member and read the disclosure, or is buried under miles of the terms and conditions?
Definitely not hide the money factor if your application is aimed at children. If you expect parents to download their free app but the children play it, consider whether the charges in the game to make sense from a business standpoint (weighed against the risks of parents claiming unauthorized charges for their children) . If there is a sound business reason for the options of loading the game, make sure you clearly and conspicuously disclose the potential costs upfront in the description.
Evaluate your drilling. Unless you are closely watching the courts and Congress may not have realized that the data user mobile applications bears his name. You must accurately assess user data is a collective application (intentional and unintentional) and why they are doing. Ask yourself these questions:
Does this mean the data collection's name, contact details or other personally identifiable information you or your contacts?
Does the application to gather information from the device location and / or a unique identifier per user or device?
Is there a business reason necessary for data collection and access?
Do you retain data for a period of time consistent with the reason that the collection?
Do you share that data with other parties (or allow others to access the data), and the parties may use the data to make a profile of users' personal identification?
If you answered yes to any of the foregoing, it should closely review how and whether the terms of its application to communicate that to the user and if the users understand the terms and consent to such use.
Legal jargon is bad. If you take care of everything identified above with a link to a long and repetitive terms and conditions privacy policy is mistaken. A boilerplate legalese does not insulate your business. The main question is if you clearly communicate the key terms - the same charges and personal data - the consumer so the consumer understood and accepted. That means ensuring that your application guides users through these key terms in a "just in time, so easy.