QuickAi is built around one rule: your data goes from your browser directly to the AI provider you choose, and nowhere near our servers — because we don't run any that touch your content. This policy explains, in plain language, exactly what that means, what little data the extension does handle, and what we never touch.
Your own API key for the AI provider you pick, kept in local browser storage on your device.
Text you highlight, or the active page's content, sent directly to your chosen provider only when you trigger a summary.
No name, email, address, age, or ID number is requested, stored, or transmitted by QuickAi.
QuickAi does not read, log, or monitor any of these — no clicks, scroll tracking, browsing history, or keystrokes. Your one-time purchase is handled entirely by a third-party storefront, not by QuickAi.
This policy covers two things: the QuickAi browser extension (available for Chromium-based browsers) and this companion website, which is used to explain the extension, demo its UI, and host these legal pages. Both are built by the same small team and follow the same data practices described below.
QuickAi's single purpose is letting you select text on any webpage and get an instant AI-generated summary, explanation, or extracted insight, using an AI provider of your choosing.
QuickAi is a paid, one-time purchase. That purchase is processed entirely by a third-party storefront, not by any server QuickAi operates — see Section 3 for what that means for your payment data.
QuickAi collects the minimum needed to do its one job, and nothing else.
To use QuickAi you connect your own account with an AI provider (OpenAI, Anthropic, Google Gemini, Groq, OpenRouter, or a local Ollama server) by pasting in your API key. That key is saved using your browser's local extension storage, on your device only. We never see it, never transmit it to any server we operate, and never ask you to create a QuickAi account.
When you highlight text and trigger QuickAi, or ask it to summarize the active tab, the extension reads that specific selection (or page content) and sends it — together with your API key, directly from your browser — to the AI provider's API endpoint. We do not intercept, copy, cache, or log this content on any server, because there is no QuickAi server in that path at all.
This site itself does not use tracking cookies, analytics pixels, or third-party ad scripts.
The two data types we handle exist for exactly one purpose each:
Neither is used for advertising, profiling, analytics, resale, model training on our end, or any purpose unrelated to producing the summary you requested in that moment.
This is a deliberate architecture choice, not just a policy promise: the extension is a thin client. If we wanted to see your data, the current design wouldn't let us — we'd have to rebuild the extension to route through a server first.
Because your requests go straight to the provider you pick, that provider's own privacy policy and terms govern how they handle the content you send them. Please review the policy for whichever provider you configure:
Picking a provider, and trusting it with your selected text, is your choice — QuickAi just gives you the switch.
Your API key is stored in your browser's local extension storage until you remove it or uninstall the extension. Summarized text and AI responses are shown in the popup for that session and are not written to any persistent QuickAi storage — closing the popup clears them from view. We retain nothing server-side because nothing passes through a server we control.
Your API key is stored using the browser's built-in extension storage APIs, sandboxed to the extension and inaccessible to other sites. All requests to AI providers are made over HTTPS/TLS. Because we don't operate servers that receive your content, there's no QuickAi-side database that could be breached to expose it.
Because we hold no account or server-side data tied to you, there's no QuickAi database to request a copy of, correct, or delete — your device already is the entire record.
QuickAi is not directed at children and is not knowingly used to collect data from children. Given the extension collects no personal information, this risk is inherently limited, but if you believe a child has configured the extension, simply remove the stored API key to fully reset it.
If this policy changes in a way that affects what data QuickAi handles, we'll update the "Last updated" date above and, where the change is material, prompt returning visitors on this site to re-review and re-accept before continuing.
Questions about this policy or how QuickAi handles data can be sent to Nyxs.Contact@gmail.com.