BoltchatBoltchat does not require a Boltchat account, run advertising or include analytics. Chats and optional memories are stored on your PC. Because the AI models run on Groq, the information needed for a request is sent directly from the app to Groq using your API key.
The short version
No Boltchat account
Install the app and connect your own Groq API key. There is no separate Boltchat sign-up.
No analytics
The app and website do not contain analytics, advertising or behavioral tracking code.
Local history
Chats, settings, optional memories and workspace state are kept in the app's data folder on your PC.
Direct model requests
AI requests go from your PC to Groq. Boltchat does not operate a server in the middle.
What stays on your computer
- Your chat history and conversation branches.
- Settings, appearance choices and the selected model.
- Optional memories you allow Boltchat to save.
- Trusted workspace folders, AI workspace conversations, pending changes and undo checkpoints.
- Your API key, protected by Windows when entered through the app.
Boltchat's Settings provide controls to inspect and delete memories. Removing conversations and application data is handled locally on your PC.
What is sent to Groq
Groq receives what is needed to process the feature you choose. Depending on your request, that can include:
- Your prompt, relevant conversation history and optional memories.
- An attached image when you use a model that can understand images.
- Recorded audio when you request Whisper transcription.
- Search queries when web search is used.
- Generated Python code when the code runner is used.
- Selected project content and tool results in the Code workspace.
Groq handles that information under the terms and privacy policy associated with your Groq account. Boltchat cannot see or control Groq's account-side retention.
How the API key is protected
A key pasted into Boltchat is encrypted with Windows data protection tied to your Windows account. Boltchat sends it to Groq for authentication but does not send it to the Boltchat publisher. If you independently place a key in a project .env file, that file is plain text and should never be shared or committed.
Never paste an API key into a contact form, bug report, screenshot or public repository.
Code workspace boundaries
Opening a folder does not automatically upload it. File content is sent to Groq when the AI reads that content for a task. Commands run locally with your Windows account, while command text and output are sent to Groq so the agent can plan and interpret results. Browser text and requested visual screenshots can also be sent to Groq during browser-based QA.
Read the Code workspace guide before opening a sensitive project.
What this website receives
The public website sets no cookies and runs no analytics. Normal hosting infrastructure still receives standard connection information such as an IP address and browser request. If you use the contact form, the fields you submit are handled by Formspree and forwarded by email as described in the policy.
Your privacy controls
- Leave memory off, or review and delete every memory in Settings.
- Delete conversations from the app.
- Open only project folders you trust and review every meaningful AI edit.
- Disable browser access or change command approvals in Code settings.
- Revoke or rotate the API key from your Groq account.
- Uninstall Boltchat and remove its application data from Windows.
This page is an accessible overview, not a replacement for the authoritative Boltchat Privacy Policy.