Data Privacy by Default
- Your chats and documents are never used to train or fine-tune AI models.
- All data is secured in transit with TLS 1.2 or higher, and all uploaded files and saved data are securely stored on our servers.
- Documents you attach during chats are automatically deleted after your session ends. They are only retained if you explicitly save them to your private Data Sources.
BYOK (Bring Your Own Key) Explained
Geekflare Connect supports a Bring Your Own Key (BYOK) model, allowing you to use your own API keys for various providers, including OpenAI, Anthropic, Gemini, OpenRouter, and others. Your API keys are encrypted and securely stored on Geekflare’s servers. API keys are encrypted at rest in our database using AES-256-CBC, an industry-standard encryption method. They are never stored on individual user browsers or local devices, minimizing client-side vulnerabilities. All requests originating from your Geekflare Connect are securely proxied through the Geekflare backend. This architecture ensures that your sensitive API keys are never directly exposed to individual team members or client-side applications. Only authorized users with the correct role can manage or update these keys.How Geekflare Handles API Data
When users interact with models through Geekflare Connect, the platform processes prompts and responses through its backend to communicate with the respective model provider using the API key. Geekflare Connect stores prompts, responses, and chat history so that users can revisit conversations, maintain continuity across projects, and access analytics or usage insights. This stored data is also used to support product features such as project-level context, shared chats, and workspace collaboration. Geekflare does not expose API keys in chat history or interface elements accessible to members.Team Access Controls
Geekflare Connect uses role-based access control (RBAC) to manage how members interact within organizations, workspaces, and data. Owner & Admins can:- Assign roles such as Admin, Member etc.
- Decide which users can access specific workspaces.
- Control permissions for viewing chats, managing API keys, and configuring workspace settings.
- Restrict access to sensitive settings at the organization or workspace level.
Transparency & Control
- You are always in the know. We clearly display which AI model (e.g., GPT-4, Claude, Gemini, DeepSeek) is responding to your prompts.
- When you use your own keys via Geekflare Connect, you retain absolute control. We have zero access to them.
- We are committed to collecting only the data essential for the platform to function. You have full control to view, manage, and permanently delete your chat history, API keys and account data at any time from the dashboard.
Responsible AI in Practice
We believe AI should be used as a powerful assistant, not an authority. To help you get the most out of our tools safely and effectively, we recommend the following practices:- AI is an assistant, not an authority. We encourage users to validate outputs.
- Generative AI can produce incorrect, biased, or outdated information. Always review outputs and cross check with multiple models and loop humans, especially in sensitive contexts.
- Avoid sharing confidential, personal, or regulated data in prompts. While Geekflare AI doesn’t use your data, the model provider may process it depending on your API key or plan.