title: Are there any volume issues regarding the Facebook app id and app secret and how many separate "applications" I use the same app id/secret on?
body: <p>Are there any volume issues regarding the Facebook app secret and how many separate connections (or "applications") I can use the same app id/secret on? For example, I'm creating a SharePoint auto-hosted Facebook application. Auto-hosted means that the server component of my app will be automatically deployed to Azure each SharePoint customer. There is no way (that I know of, obviously anything is hackable to a degree) that a user will be able to get the app id or secret, so I'm not concerned about the security aspect of it, or sharing the secret. However, potentially thousands of individual apps could be using the same app id/secret to connect to Facebook. Is this an issue?</p>
  
  <p>By the way, I'm not necessarily talking about the bandwidth/traffic threshold, I'm more concerned with the number of individual connections using the same id/secret. I realize that the policy states: "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)." This is not my immediate concern.</p>