Privacy first · transparent by design

Privacy Policy

Effective date: April 2025 · Last updated: April 2026

QuickAsk AI includes the Chrome extension, the website at quickask.me, the web app at quickask.me, and related services. It helps you highlight text, ask AI, translate selected text, manage quick tasks, take notes, and sync your highlights, notes, and tasks across devices. This page explains what data QuickAsk AI touches, what may be sent to our servers, what may be sent to third-party AI providers, and the controls you have over your data.

At a glance

What we collect

2.1 When you are not signed in

Nothing leaves your browser. Highlights, notes, tasks, and preferences are stored locally via chrome.storage.local. Clearing extension data or uninstalling removes them entirely.

2.2 When you sign in with Google

To create your QuickAsk account we receive — only what Google's standard sign-in returns to us:

We do not request access to Gmail, Drive, Calendar, Contacts, or any other Google scope beyond basic profile.

We may also store basic account metadata needed to operate the service, such as your account creation date, current plan, subscription status, app settings, and login/session information.

2.3 Content you create inside the extension

Once signed in, the following — and only the following — is synced to our servers so it is available across your devices:

Sync traffic uses HTTPS and is authenticated using secure session mechanisms appropriate to the web app and extension. We avoid storing sensitive authentication tokens in extension storage unless required for the signed-in experience.

2.4 Minimal operational logs

Our backend writes server-side logs containing request timestamps, your user ID, resource IDs, and technical metadata for debugging and abuse-prevention purposes. We design our logging to avoid storing the body of your notes, highlights, or tasks. Logs are retained for up to 30 days.

What we do not collect

Chrome permissions — why each is needed

Chrome may show you a list of permissions when you install or update the extension. The permissions we request are used for specific product features and are not used for tracking.

Permission Why it is needed
storage Persist your preferences, guest highlights, and offline cache via chrome.storage.local.
clipboardWrite Copy selected text when you explicitly use a copy/paste-style action, or prepare text for insertion into the AI provider you choose.
tabs Open or reuse a supported AI provider tab or popup window when you click "Ask AI" or choose an AI action.
scripting Inject the highlight toolbar and "Ask AI" button into the current page when you select text.
sidePanel Show the Notes / Tasks / Highlights panel on the side of the browser window.
windows Open or reuse a supported AI provider tab or popup window in the right size and position on your screen when you click "Ask AI" or choose an AI action.
system.display Read screen size so popup windows and floating UI elements can be positioned and sized appropriately on your screen.
alarms Schedule periodic background sync and task-due reminders.
idle Pause sync when your computer is idle to save bandwidth and battery.
host_permissions: http://*/*, https://*/* Required because the extension needs to show QuickAsk UI and make highlights, the "Ask AI" toolbar, notes, tasks, and page-summary features available on pages where you choose to use QuickAsk AI. Content scripts may load on supported pages, but we do not read page content in the background; content is accessed only when needed for a feature you explicitly use.

All permissions are used locally in your browser. None of them are used to track, profile, or monetise you.

Automatic protection on sensitive sites

To minimise risk on pages where sensitive information may appear, the extension limits or disables content features on a built-in list of sensitive domains. This includes:

You can override this list at any time from the extension settings (whitelist / blacklist), but the defaults err strongly on the side of safety.

AI provider integrations

QuickAsk does not run its own large language model for these direct-provider features. When you click "Ask AI" or use the radial menu with content selected, the extension opens or reuses the AI provider you have chosen and sends or inserts the content you selected into that provider's interface:

Once your selected content is sent or inserted into one of those provider interfaces, the prompt and any subsequent conversation are governed by that provider's privacy policy, not ours. We do not proxy AI traffic through our servers and we do not see your prompts or AI responses.

If available, the optional YouTube/video summary feature may read the public transcript or visible transcript content of the video you are watching and send only the transcript text to the AI provider you choose — only when you click the summary button.

Security

Your controls and rights

If you are in the EU/UK, you also have GDPR rights of access, rectification, erasure, restriction, portability, and objection — exercised through the same email address.

Data retention

Children's privacy

QuickAsk AI is not directed to children under 13. If the laws of your jurisdiction require a higher minimum age or parental consent for services like ours, you may use QuickAsk AI only if you meet that requirement. We do not knowingly collect personal data from children who are not allowed to use the service. If you believe a child has provided us with data, please contact us and we will delete it.

Changes to this policy

If we make material changes, we will update the "Last updated" date at the top of this page and, where appropriate, provide notice in the app, extension, or by email. We encourage you to review this policy periodically.

Contact

Questions, concerns, or data-subject requests:

vietanhbkaaa@gmail.com

We aim to respond within 5 business days.

Ready to try QuickAsk?

Install the Chrome extension and start highlighting in under 30 seconds.

Add to Chrome