Features and Functionality. 1. You must not violate any law or the rights of any individual or entity, and must not expose Facebook or Facebook users to harm or legal liability as determined by us in our sole discretion. In particular you will (if applicable): comply with the Video Privacy Protection Act (VPPA), and obtain any opt-in consent necessary from users so that user data subject to the VPPA may be shared on Facebook. You represent that any disclosure to us will not be incidental to the ordinary course of your business. 2. You must not include functionality that proxies, requests or collects Facebook usernames or passwords. 3. You must not circumvent (or claim to circumvent) our intended limitations on core Facebook features and functionality. 4. If you offer a service for a user that integrates user data into a physical product (such as a scrapbook or calendar), you must only create a physical product for that user’s personal and non-commercial use. 5. If you exceed, or plan to exceed, any of the following thresholds please contact us as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day). 6. Your app or website must offer an explicit “Log Out” option. 7. Special provision for apps on Pages: When a user visits your Page, if they have not given explicit permission by authorizing your Facebook app or directly providing information to your Page, you may only use information obtained from us and the user’s interaction with your Page in connection with that Page. For example, although you may use aggregate analytics for your individual Page, you must not combine information from any other sources to customize the user’s experience on your Page and may not use any information about the user’s interaction with your Page in any other context (such as analytics or customization across other Pages or websites). 8. You must not use or make derivative use of Facebook icons, or use terms for Facebook features and functionality, if such use could confuse users into thinking that the reference is to Facebook features or functionality. 9. Mobile Web Apps that are running within the Facebook iOS app must not accept payments. In particular, these apps must not reference, use, or otherwise encourage the use of Facebook Payments or other non-iOS approved payment methods. 10. Reciprocity and Replicating core functionality: (a) Reciprocity: Facebook Platform enables developers to build personalized, social experiences via the Graph API and related APIs. If you use any Facebook APIs to build personalized or social experiences, you must also enable people to easily share their experiences back with people on Facebook. (b) Replicating core functionality: You may not use Facebook Platform to promote, or to export user data to, a product or service that replicates a core Facebook product or service without our permission. 11. The primary purpose of your Canvas or Page Tab app on Facebook must not be to simply redirect users out of the Facebook experience and onto an external site. 12. You must not include data obtained from us in any search engine or directory without our written permission. 13. Special provisions for games: a. Desktop web games off of ▇▇▇▇▇▇▇▇.▇▇▇ may only use Facebook Login (Authentication, excluding user connections such as friend list), Social Plugins and publishing (e.g., Feed Dialog, Stream Publish, or Open Graph). When authenticating, these games may not request additional permissions other than age, email, and our Publishing Permissions.
Appears in 1 contract
Sources: Facebook Platform Policy (King Digital Entertainment PLC)
Features and Functionality. 1. You must not violate any law or the rights of any individual or entity, and must not expose Facebook or Facebook users to harm or legal liability as determined by us in our sole discretion. In particular you will (if applicable): comply with the Video Privacy Protection Act (VPPA), and obtain any opt-in consent necessary from users so that user data subject to the VPPA may be shared on Facebook. You represent that any disclosure to us will not be incidental to the ordinary course of your business.
2. You must not include functionality that proxies, requests or collects Facebook usernames or passwords.
3. You must not circumvent (or claim to circumvent) our intended limitations on core Facebook features and functionality.
4. If you offer a service for a user that integrates user data into a physical product (such as a scrapbook or calendar), you must only create a physical product for that user’s personal and non-commercial use.
5. If you exceed, or plan to exceed, any of the following thresholds please contact us (▇▇▇▇▇://▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/help/content/?id=206103619499608) as you may be subject to additional terms: (>5M MAU) or (>100M API calls per day) or (>50M impressions per day).
6. Your app or website must offer an explicit “Log Out” optionoption that also logs the user out of Facebook.
7. Special provision for apps on Pages: When a user visits your Page, if they have not given explicit permission by authorizing your Facebook app or directly providing information to your Page, you may only use information obtained from us and the user’s interaction with your Page in connection with that Page. For example, although you may use aggregate analytics for your individual Page, you must not combine information from any other sources to customize the user’s experience on your Page and may not use any information about the user’s interaction with your Page in any other context (such as analytics or customization across other Pages or websites).
8. You must not use or make derivative use of Facebook icons, or use terms for Facebook features and functionality, if such use could confuse users into thinking that the reference is to Facebook features or functionality.
9. Mobile Web Apps that are running within the Facebook iOS app must not accept payments. In particular, these apps must not reference, use, or otherwise encourage the use of Facebook Payments or other non-iOS approved payment methods.
10. Reciprocity and Replicating core functionality: (a) Reciprocity: Facebook Platform enables developers to build personalized, social experiences via the Graph API and related APIs. If you use any Facebook APIs to build personalized or social experiences, you must also enable people to easily share their experiences back with people on Facebook. (b) Replicating core functionality: You may not use Facebook Platform to promote, or to export user data to, a product or service that replicates a core Facebook product or service without our permission.
11. The primary purpose of your Canvas or Page Tab app on Facebook must not be to simply redirect users out of the Facebook experience and onto an external site.
12. You must not include data obtained from us in any search engine or directory without our written permission.
13. Special provisions for games:
a. Desktop web games off of ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas) may only use Facebook Login (Authentication, (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/authentication) excluding user connections such as friend list), Social Plugins (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/plugins) and publishing (e.g., Feed Dialog, Stream Publish, or Open Graph). When authenticating, these games may not request additional permissions (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/authentication/permissions) other than age, email, and our Publishing PermissionsPermissions (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/publishing).
b. Games on ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas) and mobile must not share the same app ID with desktop web games off of ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas). You must not use Canvas (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas/#canvas/) apps to promote or link to game sites off of Facebook, and must not use emails obtained from us to promote or link to desktop web games off of ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas).
c. Games on ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas) or Mobile Web must use Facebook Payments as their sole and exclusive payment method for all virtual goods and currencies made available to users within the game. All other payment options are prohibited within games on ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas) or Mobile Web unless they go through Facebook Payments rather than directly through that payment option. By “Payment Method” we mean any method that allows a user to complete a transaction in a game that is on ▇▇▇▇▇▇▇▇.▇▇▇ (▇▇▇▇▇://▇▇▇▇▇▇▇▇▇▇.▇▇▇▇▇▇▇▇.▇▇▇/docs/guides/canvas) or Mobile Web, including, without limitation, by exchanging monetary value for virtual currency or virtual goods, whether directly at the time of purchase or via any previous transaction such as the user’s earlier purchase of a prepaid gift card or electronic code. In-game rewards of virtual currency or virtual goods earned by users through game-play activity alone are exempt from this definition.
Appears in 1 contract
Sources: Facebook Platform Policies (King Digital Entertainment PLC)