iOS App rejected from App store 3.2.2 (Business model unacceptable) I have an online service that adds on additional features to an existing online service. It's currently only accessible via desktop. It has free features and premium features that are offered via a subscription service. I've recently created an app version and applied to the Apple App Store. After a few back and forths with Apple, they have responsed with Guideline 3.2.2(vii) - Business - Other Business Model Issues - Unacceptable Your app contains content or features that may violate the rights of one or more third parties. ****Removed one line for confidentiality here. It was pointing out which features were specifically out of line(basically the core features)**** Your app and its contents should not infringe upon the rights of another party. In the event your app infringes another party’s rights, you are responsible for any liability to Apple because of a claim. Next Steps To resolve this issue, please remove any features or functionality that ****Removed for confidentiality. Above features****. I don't think that it infringes upon the rights of the other company since it only adds features and it does not affect the revenue stream of the other company. In fact it may increase their revenue. Google has approved the app already. Could anybody shed some light on what my options might be? Or if this is the end of the road? Also if these details are too little and you need more?
Apple has rules for publishing apps on the App Store, and either you follow the rules, or your app won't go on the App Store, simple as that. What you do is either not put your app on the App Store, or make the changes they ask you to make. Why are there conflicting statements? Because Apple and Google are different companies. Does Apple ask the other company? No, why would they spend their time on this, when they can ask you to make the changes? In the end, Apple has huge pockets, so they are not going to approve anything that might give a company a way to take money out of their pocket. What you want to do sounds very much like it could give some company a pretext to sue Apple; that's one thing that Apple won't let happen.
Social media platforms are not publishers under UK law (at present), as such, they are not legally responsible for the content they host providing that there is a mechanism for alerting them to infringing material and that, when alerted, they remove it. As to "why", that is a political question.
Interesting that they don't give a source and also don't link to anywhere (such as Wikimedia commons). So I assume that content is google's own. So generally speaking: No, when no license is provided, that means you can't use whatever it is in a project of yours (whether commercially or not), because the &quot;default&quot;, when nothing is specified, is that no license is given. So unless you find a license that grants you a permission on google's own content, these sounds can't be used freely.
You are not supposed to "explain" anything. See this site: http://www.dmlp.org/legal-guide/responding-dmca-takedown-notice-targeting-your-content What you have to do is to state, under penalty of perjury, that you have a good faith belief that your material was wrongly removed. That's it. Nothing more, nothing less. Google (or whoever the host is) doesn't care and shouldn't care about the actual copyright situation, only whether you supplied a counter notice where you state that your material was wrongly removed. Now Google should reinstate your app (however, since nobody can force them to host your app at all, I suspect they can remove it at any time for any reason), and whoever put in the DMCA claim can then go and sue you for copyright infringement. If they do, you can use as a defence that they could have and should have a DMCA notice to you. The whole DMCA is about your host, here: Google, to remove itself from any copyright infringement case. By following the rules for a proper notice and proper counter notice, they achieve that. And then the matter is between the complainant and you.
united-states You are protected by copyright as a matter of law, even if you don't post a copyright notice, although you have slightly more procedural rights if you do post a copyright notice and there would need to be a filing with the copyright registrar (a division of the Library of Congress) before you brought suit. You can't really get any other intellectual property protections for it except possibly a trademark if you have a distinctive mark or name or logo for the app.
An incomplete list: Getting the money. How did you plan to get paid? Credit card? Paypal? Integrating those into a website in compliance with their terms of service is not easy. (I wouldn't touch credit card numbers, in particular, even with a ten-foot pole. Too much liability risk for weak implementations. Too many highly skilled attackers to pounce on any mistake.) Distributing the App. Places like the Apple App Store have their own terms of service, especially regarding payment and in-app purchases. At a guess, Apple would reject your app, but if they allowed it, how does your withdrawal policy fit with the 30% cut they want from the initial transaction? Holding the money. So there are user accounts with a credit balance that can be withdrawn again. Would you be able to repay them if all users withdraw at the same time? Where do you keep the money? Currency risks. Say international customers pay in currency A, which the payment provider transforms into currency B. Then they want their money back, but exchange rates have changed. What do they get? Knowing your customer. There would be money laundering concerns. Do you have the infrastructure to identify your customers? Can customers change the (re)payment method from one account to another? Can you handle withdrawals if a user no longer has the same credit card, for instance? Scammers leaving you to hold the bag. Say a scammer tricks a victim into making a deposit, and then finds a way to redirect the withdrawal (see above). Would you be able to deal with the legal and administrative fallout?
Yes, this violates the GDPR if the user is in Europe. Data which is tied to a personal device can be tied to the person who owns it. From "What Is Personal Data" by the UK Information Commissioner's Office (ICO) (emphasis added): Personal data is information that relates to an identified or identifiable individual. What identifies an individual could be as simple as a name or a number or could include other identifiers such as an IP address or a cookie identifier, or other factors. If it is possible to identify an individual directly from the information you are processing, then that information may be personal data. If you cannot directly identify an individual from that information, then you need to consider whether the individual is still identifiable. You should take into account the information you are processing together with all the means reasonably likely to be used by either you or any other person to identify that individual. The bit about "all means reasonably likely" in the last bullet includes the kind of de-anonymisation tactics described in the NYT article. There are 6 lawful bases for data processing in the GDPR, and all processing must fall under at least one of them. (a) Consent: the individual has given clear consent for you to process their personal data for a specific purpose. (b) Contract: the processing is necessary for a contract you have with the individual, or because they have asked you to take specific steps before entering into a contract. (c) Legal obligation: the processing is necessary for you to comply with the law (not including contractual obligations). (d) Vital interests: the processing is necessary to protect someone’s life. (e) Public task: the processing is necessary for you to perform a task in the public interest or for your official functions, and the task or function has a clear basis in law. (f) Legitimate interests: the processing is necessary for your legitimate interests or the legitimate interests of a third party, unless there is a good reason to protect the individual’s personal data which overrides those legitimate interests. (This cannot apply if you are a public authority processing data to perform your official tasks.) Selling data isn't covered by any of the others, so consent must be obtained. Permission must be clear and positive, and you cannot predicate delivery of a service on the processing of data that isn't necessary for that service. So for instance you cannot say "You can use this service as long as we are allowed to collect and sell your data" because selling the data isn't necessary to the provision of the service. From "Consent" by the ICO: Consent requires a positive opt-in. Don’t use pre-ticked boxes or any other method of default consent. Explicit consent requires a very clear and specific statement of consent. Keep your consent requests separate from other terms and conditions. Be specific and ‘granular’ so that you get separate consent for separate things. Vague or blanket consent is not enough. [...] Avoid making consent to processing a precondition of a service. This applies to any processing of data about individuals within the EU, so just being an American company doesn't get you a free pass to ignore the GDPR if your app gets used by Europeans. The "Legitimate interests" basis is more problematic, in that the company collecting the data has to conduct a vague "balancing test" to determine if this basis applies. For direct marketing the ICO has written this, which says that direct marketing may be a legitimate interest, especially if you can show that the user has expressed interest in such adverts. For instance a location service which promises to tell you about nearby special offers would fall into this category. Against this, the impact on the user's privacy has to be considered, and location data is "special category data" because it can reveal medical information (e.g. hospital attendance) or religious affiliation (e.g. which church you go to). So unless the relationship between the recorded location data and the service is very direct its not going to pass the balancing test. The company would also need to distinguish between knowing the current location and keeping a record of historical locations; the two need separate justification. And of course nothing about this covers the sale of the data; this is considering a company which sells advertising space in it's app, not one that sells the data itself.
What SE can do is controlled primarily by the Terms of Service. What most matters is the section on Subscriber Content, which says: You agree that any and all content, including without limitation any and all text, graphics, logos, tools, photographs, images, illustrations, software or source code, audio and video, animations, and product feedback (collectively, “Content”) that you provide to the public Network (collectively, “Subscriber Content”), is perpetually and irrevocably licensed to Stack Overflow on a worldwide, royalty-free, non-exclusive basis pursuant to Creative Commons licensing terms (CC-BY-SA), and you grant Stack Overflow the perpetual and irrevocable right and license to access, use, process, copy, distribute, export, display and to commercially exploit such Subscriber Content, even if such Subscriber Content has been contributed and subsequently removed by you... This means that you cannot revoke permission for Stack Overflow to publish, distribute, store and use such content and to allow others to have derivative rights to publish, distribute, store and use such content. The CC-BY-SA Creative Commons license terms are explained in further detail by Creative Commons, but you should be aware that all Public Content you contribute is available for public copy and redistribution, and all such Public Content must have appropriate attribution. This part has not changed: the purported license is still "CC-BY-SA", and the TOS does not explicitly specify a version. What apparently has changed in the relevant section is one "helpful information" link, which now points to https://creativecommons.org/licenses/by-sa/4.0/. So the interesting question arises whether that would constitute an unpermitted post-hoc change in the terms by which SE has license to my older stuff. This matter came up in a reviled Meta question; as I pointed out, the TOS also included a merger clause that This Agreement (including the Privacy Policy), as modified from time to time, constitutes the entire agreement between You, the Network and Stack Exchange with respect to the subject matter hereof. This Agreement replaces all prior or contemporaneous understandings or agreements, written or oral, regarding the subject matter hereof. Because of that, the TOS is self-contained and stuff found on other web pages are not part of the agreement. This in itself is a bit of a problem because you can't both say "we're not bound by stuff outside of this page" and say "the specific terms of the license are outside this page". That particular clause is gone, but there is an analog in the current TOS: These Public Network Terms represent the entire agreement between you and Stack Overflow and supersede all prior or contemporaneous oral or written communications, proposals, and representations with respect to the public Network or Services or Products contemplated hereunder. Furthermore, the TOS contains the following "we can change it" clause: Stack Overflow reserves the right, in its sole discretion, to modify or replace these Public Network Terms, as our business evolves over time and to better provide Services and Products to the Stack Overflow community, or to change, suspend, or discontinue the public Network and/or any Services or Products at any time by posting a notice on the public Network or by sending you notice via e-mail or by another appropriate means of electronic communication. I assume but do not know for a fact that a similar clause existed in prior versions of the TOS. So I conclude that the change is legal.