Security
Data Handling and Permissions
KQLRemix is built as a local-first Chrome Extension workflow. This page summarizes what data is used, where it goes, and why.
Data flow
KQL text
Browser extension and Gemini API
Used as context to generate or refine the query you request.
Schema
Browser extension and Gemini API
Helps generated KQL match the tables and fields visible in your workspace.
API key
Local browser storage
Stored on your device for Bring Your Own Key Gemini requests. It is not sent to KQLRemix servers.
Log data
Not collected by KQLRemix
The extension is designed around query text, intent, and schema context, not database rows.
Email
Waitlist system
Used to contact you about early access and launch updates when you join the waitlist.
Chrome Extension permissions
The extension manifest is not stored in this landing page repo, so this list should be reconciled against the final submitted manifest before launch.
Azure Portal page access
Allows the sidebar to appear beside supported Azure KQL workflows.
Storage
Keeps your Gemini API key and extension preferences in local browser storage.
Network access to Gemini API
Sends your prompt and selected query context directly to the Gemini API using your key.
Local API key storage
Your Gemini API key stays in browser storage and is used for direct Gemini API requests from the extension experience.
Security contact
Report security questions or issues at support@kqlremix.com.