Blinkling Privacy Policy
Blinkling / Privacy
Last updated: 18 October 2026 ยท Version 3.2.6
Blinkling has no telemetry. It does not send analytics or diagnostic events to its publisher. This policy explains what the optional browser helper reads, where that information goes, and how it is stored.
Blinkling has no publisher-operated answer service. Blink sends what you pick to your own signed-in Claude Code, on your own computer. The publisher does not receive those requests. Blinkling does not sell user data or use it for advertising.
Information the helper can access
The helper is a browser extension that works only together with Blink on the same computer. When Blink asks about the page under your pointer, the helper reads the page address and title and a short list of the page's visible elements: what kind each is, where it is, its role, its name and a bounded amount of its text. It reads at most 400 elements and skips hidden ones. It never reads the value of password, payment or other sensitive fields; those are listed as protected, without text.
When you ask for a full-page capture, the helper scrolls the page and takes screenshots of the visible tab. It refuses pages that contain a password field. When you ask to translate a page, the text of the page is sent in batches to Claude Code through Blink, and the translation replaces the text in place until you restore it. The PDF reader opens a PDF you are viewing in a page of the extension itself.
The helper asks the browser for access to all sites so that it can read the page you point at. It does nothing on a page until Blink asks. The browser's settings pages, extension stores and its built-in PDF viewer cannot be read.
Where information goes
The helper talks only to Blinkling on the same computer, over a local connection that both sides prove they are allowed to use. Nothing the helper reads is sent to a website or to the publisher. Blink passes what you pick, and what the helper read, to your Claude Code. The provider's terms apply, and the provider may retain what it receives. Auto explain is off until you turn it on.
The Chrome Web Store User Data Policy applies to this helper. Its Limited Use requirements are met: the publisher does not use page content for unrelated purposes or maintain a browsing-history log.
What is stored
| Location | What is stored |
|---|---|
| Browser local storage | A random secret that lets the helper and Blink recognise each other. It is created when you open the setup page and is not shared with any website. |
| Blink's runtime folder | The same secret, in a file only your user account can read. Deleting it ends the connection. |
| Memory of the helper and Blink | The latest page elements, kept for about a second and a half, and active requests. They are cleared when the browser or Blink stops. |
| Claude Code | Conversation transcripts, stored according to that program's own session behaviour. Blinkling does not keep them in the browser. |
Cost and controls
Requests go through your own Claude Code account, so provider usage charges apply. Cost depends on the model, context, images and output. Check your provider account for actual charges.
You can remove the extension in the browser's extension settings, which deletes its stored secret and disconnects it from Blink. Removing the extension does not delete Claude Code transcripts on the computer or records retained by your provider. Manage those with Claude Code or your provider account.
Contact
For privacy questions, contact the maintainer, Arthur031221, through the Blinkling issue tracker. Issues are public. Do not include private page content or credentials.