BlinkAI Privacy Policy
Last Updated: May 23rd, 2026
TL;DR
BlinkAI collects zero data. Your API key stays on your device. We have no servers, no tracking, no analytics.
1. Overview
BlinkAI is a Chrome extension that provides AI-powered text explanations using Google’s Gemini API. This privacy policy explains our data practices (spoiler: we don’t collect any data).
2. Data Collection
We collect ZERO user data.
BlinkAI does not collect, store, transmit, or process any personal information, browsing history, or user activity.
2.1 Your Gemini API Key
- Stored: Locally on your device using Chrome’s secure extension storage (
chrome.storage.local)
- Never transmitted to us: We have no servers. Your key only travels directly from your browser to Google’s Gemini API
- Your control: Delete it anytime from the extension popup
2.2 Selected Text
- Never stored: Text you highlight is immediately sent to Google’s Gemini API and then discarded
- Never seen by us: It goes directly from your browser to Google—we’re not in the middle
- Not logged: We have no servers to log it on
2.3 Extension Settings
- Stored locally: Model preference, enable/disable state
- Never transmitted: These settings stay on your device
3. Third-Party Services
BlinkAI uses Google’s Gemini API to process your text selections. When you use BlinkAI:
- Selected text is sent directly to
generativelanguage.googleapis.com
- Google processes the text according to their privacy policy: https://policies.google.com/privacy
- BlinkAI does not intermediate, log, or see this data
4. BYOK (Bring Your Own Key) Model
You provide your own free Gemini API key from Google AI Studio. This means:
- ✅ You control your data relationship with Google
- ✅ We never see your API key or usage
- ✅ No subscription fees or vendor lock-in
- ✅ Full transparency—you can verify in DevTools that all API calls go directly to Google
5. Permissions Explained
BlinkAI requests these Chrome permissions:
- activeTab: To read text you select on the current page
- scripting: To inject the UI (pill + chat panel) into webpages
- storage: To store your API key locally
- tabs: To detect when the active tab is a PDF and show an informational notice that BlinkAI is unavailable, since Chrome does not allow content scripts in the built-in PDF viewer. Online PDFs work normally as regular web tabs
- host_permissions (all URLs): So you can use BlinkAI on any website you visit
None of these permissions are used for tracking, analytics, or data collection.
6. No Analytics, No Tracking
BlinkAI does not use:
- ❌ Google Analytics
- ❌ Error reporting services
- ❌ Usage telemetry
- ❌ Crash reports
- ❌ A/B testing
- ❌ Any third-party scripts
We literally have no idea how many people use BlinkAI or what they use it for. And that’s by design.
7. Data Security
Since we don’t collect data, there’s no data to breach. Your API key is stored using Chrome’s built-in secure storage, encrypted at rest.
8. Children’s Privacy
BlinkAI does not knowingly collect data from anyone, including children under 13. Since we collect zero data from all users, this protection extends universally.
9. Changes to This Policy
If we ever change our data practices, we’ll update this policy and the “Last Updated” date.
10. Your Rights
Under GDPR, CCPA, and other privacy laws, since BlinkAI collects no data, there’s nothing to access, delete, export, or opt out of. Your API key is stored locally and you can delete it anytime.
Developer: Sunny (@isunnybits)
Support the project: If you find BlinkAI useful, consider buying me a coffee ☕
Questions? Open an issue on the GitHub repository
BlinkAI • Built with privacy in mind • No servers, no tracking, no BS