API Key Exposure in Chrome Extension

I'm creating a chrome extension and I'm worried that this will expose my API Key in a way that will violate this line of the Bungie Terms of Use: [quote]You agree to keep your API Key confidential and not to share it with any third party. This right is unique to you, and any affiliates or third parties must seek and obtain their own Bungie.net API right and API Key.[/quote] Doing an [b]Inspect Element[/b] of the Chrome Extension and navigating to the source javascript file where the API Key shows that it can be exposed. Is there a way around this? Or is this not a problem since the average user won't be using the Chrome Developer Tools.