API Key Storage Options

Geekflare AI provides flexibility in how you manage and store API keys for third-party AI model providers (like OpenAI, Google Gemini, DeepSeek, etc.). Understanding these options will help you choose the method that best suits your security preferences.

We offer two primary methods for handling your external API keys:

Option 1: Browser Storage (Client-Side Only)

How it Works:

• You enter your AI API key into the Geekflare AI interface.
• The API key is stored locally in your web browser’s storage (e.g., localStorage).
• When you initiate a AI chat, requests to the AI model provider are made directly from your browser to their API endpoint.
• Geekflare AI’s servers never see or store your API key in this mode.

Pros:

• ✅ Maximum User Control: You retain full control over your API key; it never leaves your browser to be stored on Geekflare AI servers.
• ✅ No Server-Side Storage: This can be preferable for users with strict policies against sharing API keys with any third-party service.

Considerations:

• ⚠️ Browser Dependent: The security of the key relies on the security of your browser and your local machine.
• ⚠️ Device Specific: Keys stored in browser storage are typically tied to that specific browser on that specific device. You would need to re-enter the key if you use Geekflare AI on a different browser or device.
• ⚠️ Clearing Browser Data: When you logout, you clear your browser’s cache, cookies, the stored API key will likely be erased, requiring you to re-enter it.

Option 2: Secure Storage with Geekflare AI (Server-Side)

How it Works:

• You provide your API key to Geekflare AI, explicitly choosing to save it with us.
• The API key is transmitted securely (over HTTPS) to Geekflare AI’s servers.
• Before storing it in our database, we encrypt your API key using strong AES-256-CBC encryption.
• When you initiate an AI chat requiring the key:
  1. Geekflare AI’s services retrieve the encrypted key from the database.
  2. Geekflare AI server decrypts the keys and stores temporarily in your browser’s local storage until you log out/delete it.
  3. Subsequent AI requests to the AI model provider are made directly from your browser using your API key.
• When you explicitly delete the key from your Geekflare AI settings or log out, the key is also removed from your browser’s local storage.

Pros:

• ✅ Convenience: Your API key is available across any device or browser you use to access your Geekflare AI. No need to re-enter it frequently.
• ✅ Centralized Management: Manage all your AI API keys within your Geekflare AI account.

Our Security Commitment for Stored Keys

When you choose to store your API keys with Geekflare AI (Option 2), we are committed to the following security practices:

• Strong Encryption: We use AES-256-CBC for encrypting your API keys at rest in our database.
• Secure Transmission: API keys are transmitted from your browser to our servers over HTTPS (TLS).
• Access Controls: Strict access controls are in place internally to limit who can access the systems.
• Regular Security Audits & Updates: We continuously monitor and update our security practices.

Which Option Should You Choose?

• Choose Option 1 (Browser Storage) if:

  • You prioritize keeping your API keys under your direct local control and do not want them stored on Geekflare server.
  • You primarily use Geekflare AI interactively from a single, trusted device/browser.

• Choose Option 2 (Secure Storage with Geekflare AI) if:

  • You value convenience and want your keys accessible across devices.
  • You are comfortable with Geekflare AI’s stated security measures for protecting your encrypted keys.

You can typically choose your preferred storage method when adding a new API key within the Geekflare AI platform.