> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bright-sdk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

<AccordionGroup>
  <Accordion title="Can Bright SDK be implemented in Steam apps">
    **Yes!** Bright SDK Windows version can be easily implemented in any Steam games.

    To do that, please follow the detailed integration guide we created here: [https://docs.google.com/document/d/1CO8KPNW\_gD-FNvNT0X8cOXFMXUfwjGpcp021kXOG7ew/edit?tab=t.0](https://docs.google.com/document/d/1CO8KPNW_gD-FNvNT0X8cOXFMXUfwjGpcp021kXOG7ew/edit?tab=t.0)

    Don't hesitate to reach out to our partnership managers with any question.
  </Accordion>

  <Accordion title="Am I being paid only when my Windows app is in use?">
    Great news! Once your user has opted-in you start earning even if your app isn’t necessarily in use. See [this article](https://docs.bright-sdk.com/help-center/payment-information#what-are-the-minimum-requirements-for-a-user-to-be-considered-as-qualified-device) for more details.

    This information is available to you in real time on the developer dashboard.
  </Accordion>

  <Accordion title="Does Bright SDK comply with Anti Virus guidelines?">
    **Yes.** Bright SDK has been developed under the strictest security guidelines and is constantly monitored accordingly. It has been certified by AppEsteem, trusted by major anti virus companies. This certification is also granted to all of our Windows partners, as part of our service and with no extra charge.\
    [Click](https://docs.google.com/spreadsheets/d/1iuWmD6t4maCcMXXtIFodwdOIZO_vXRwGpNKq3C_J0hA/) for a detailed view of the SDK compliance with security industry standards by leading organizations.
  </Accordion>

  <Accordion title="Which Windows versions are supported?">
    Bright SDK support all Windows 7 and up.
  </Accordion>

  <Accordion title="How do I implement Windows SDK?">
    All you need can be found in Windows integration guides:

    * [.NET](https://docs.bright-sdk.com/integration-guides/windows-integration-net)
    * [C/C++](https://docs.bright-sdk.com/integration-guides/windows-integration-c)
  </Accordion>

  <Accordion title="Can I see some examples of real Windows apps implementation?">
    **Sure!** Please see them here:

    * [App Monetization with Bright SDK - Windows Integration](https://www.youtube.com/watch?v=Snh_U2pbkn0)
    * [Guided tour video](https://www.youtube.com/watch?v=kQCmca0FHyw)
  </Accordion>

  <Accordion title="My dashboard shows 0 active devices even though users opted in. Why?">
    The app needs to pass the self-check and Bright Data review before devices start counting. Also check that the app status is set to "Active/Approved" in the dashboard.
  </Accordion>

  <Accordion title="How to obtain BrightSDK API Key?">
    The BrightSDK tools authenticate with the releases API using an API key. Follow these steps to create one.

    1. **Open API Keys**\
       Log in to the [BrightSDK Control Panel](https://bright-sdk.com/cp/settings/company_profile#api_keys) - this links directly to the **API keys** section. <img src="https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step2_api_keys.png" alt="API keys section" />
    2. **Create a new key**\
       Click **+ Add**. Choose an expiration (e.g. *One year*), give the key a descriptive name, then click **Generate key**. <img src="https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step3_key_creation.png" alt="Key creation dialog" />
    3. **Copy your key**\
       The generated key is shown **once only** - copy it immediately. <img src="https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step4_key_revealed.png" alt="New API key revealed" />
           <Warning>
             **Important:** Once you close this dialog the key cannot be retrieved. If lost, delete and create a new one.
           </Warning>
    4. **Set the environment variable** **macOS / Linux** - export in your shell:
       ```bash theme={null}
       export SDK_API_KEY="<your-api-key>"
       ```
       To persist across sessions:
       ```bash theme={null}
       echo 'export SDK_API_KEY="<your-api-key>"' >> ~/.zshrc
       ```
       **Windows (PowerShell)** - set for the current session:
       ```powershell theme={null}
       $env:SDK_API_KEY = "<your-api-key>"
       ```
       To persist for your user (survives reboots):
       ```powershell theme={null}
       [Environment]::SetEnvironmentVariable("SDK_API_KEY", "<your-api-key>", "User")
       ```
       **Windows (CMD)** - set for the current session:
       ```cmd theme={null}
       set SDK_API_KEY=<your-api-key>
       ```
       To persist for your user (survives reboots):
       ```cmd theme={null}
       setx SDK_API_KEY "<your-api-key>"
       ```
  </Accordion>
</AccordionGroup>