Protecting Your Intellectual Property

To protect your intellectual property, consider the following:

• Only publish package components that are your intellectual property and that you have the rights to share.
• After your components are available on AppExchange, you can’t recall them from anyone who has installed them.
• The information in the components that you package and publish might be visible to customers. Use caution when adding your code to a formula, Visualforce page, or other component that you can’t hide in your app.
• The code contained in an Apex class, trigger, Lightning, or Visualforce component that’s part of a managed package is obfuscated and can’t be viewed in an installing org. The only exceptions are methods declared as global. You can view global method signatures in an installing org. In addition, License Management Org users with the View and Debug Managed Apex permission can view their packages’ obfuscated Apex classes when logged in to subscriber orgs via the Subscriber Support Console.
• If a custom setting is contained in a managed package, and the Visibility is specified as Protected, the custom setting isn’t contained in the list of components for the package on the subscriber’s org. All data for the custom setting is hidden from the subscriber.