Version 2 · Last updated on 2026-09-06
The Buboflash extension lets you highlight a passage on any webpage and turn it into a flashcard, and shows you the highlights you made when you come back to that page.
To show you your old highlights it has to ask our server "do I have anything for this page?" — and to ask that, it has to tell the server which page you are on. That is the whole privacy trade, and everything below is detail on it.
Annotations in tabs is a checkbox in the extension's popup. The browser-action icon shows
its state: crossed out
when off, plain
when on.
When it is off — or when you are not logged in to Buboflash — the extension sends nothing about your browsing. Not the URL, not the page, nothing. It does not even load itself into the page: with the switch off no script is injected into any tab, so there is nothing running there to send anything.
This is a gate in the code and not a promise about intent. It is checked before the URL is sent, and again before anything is created.
Every page address you open is sent to the Buboflash server. It is sent twice, for two questions:
The page itself is not sent. We send the address; the server answers with your own annotations for it; the extension then finds the matching passages inside your browser and highlights them there. The server never sees the text it is highlighting.
So if you open your bank, your medical records or your employer's intranet with the extension on, what reaches us is the address of the page and nothing that is on it. That holds even if somebody else has maliciously created an annotation on a page with the same address — the matching happens in your browser, and the annotation text is theirs, not your page's.
But an address is not nothing. https://example-clinic.co.uk/results/appointment-confirmed
tells a reader a great deal without a single word of the page body. Please read § 3 and § 6
with that in mind.
Creating an annotation, a flashcard or a reading point sends us, in addition to the address:
That passage is the only page content we receive that you did not select yourself, and it is bounded. We do not receive the rest of the page.
mail.google.com is blocked outright, server-side.http: or https: — local files, browser settings pages,
extension pages.Stored in your browser, per browser (so you can have the extension on at home and off at work): the Annotations in tabs switch itself, how long a highlight's popup stays open, and your keyboard shortcuts.
Stored on your Buboflash account, shared across every browser: the Annotations from selector, which chooses whose annotations you see. It is a normal account preference that happens to be reachable from the extension popup.
Sending the address of every page you open to an outside server is almost certainly against your employer's or your school's policy, whatever the server does with it. You may also get buboflash.eu blocked by whoever runs the firewall, which would be a bad outcome for both of us.
If you want to learn from something at work, use buboflash.eu directly. Nothing in the extension is unavailable there.
Nothing. The address is removed from our server's request log before the log is written, and the log itself is deleted after 14 days; what it keeps is that your extension asked, when, and for which account. We do not keep a record of your browsing — not a permanent one, and not a temporary one. The Privacy Notice § 5 and § 8 give the detail.
Annotations, flashcards and the reading schedule are managed by the
https://buboflash.eu backend service, which the extension's author also wrote.
scriptingThe extension injects a content script that lets the user annotate websites and displays previously made annotations on mouse hover. Text with annotations is highlighted in the website.
The content script is injected only if the Annotations in tabs checkbox is enabled and the user is logged in. Users enable and disable this in the popup. If it is disabled there is no content script, and the popup shows only a generic learning summary from the server with no connection to the page being browsed.
This is explained at
https://buboflash.eu/bubo5/tal-static-fullscreen-forall/annotations-privacy, linked next to
the checkbox in the popup. That page also discourages enabling the extension at work and
suggests using https://buboflash.eu directly instead.
contextMenusAnnotations and flashcards are created by selecting text on a website and right-clicking, then choosing a menu item: create annotation, create flashcard. A reading point is set the same way.
storageExtension settings are stored locally in the browser: whether Annotations in tabs is on, how long to show an annotation's popup when the mouse hovers over an annotated passage, and the keyboard shortcuts.
One preference reachable from the popup — Annotations from, which chooses whose annotations are displayed — is not local; it is an account preference stored on the Buboflash server, as it is also settable on the website.
tabsThe extension needs access to:
If Annotations in tabs is unchecked, or the user is not logged in, the extension does not touch tabs.
webRequestThe extension listens for https://buboflash.eu/bubo5/logout so it knows when the user logs
out of the backend server. When the user logs out, the extension stops injecting anything into
tabs.
When the user enables annotations in webpages and the backend server confirms that a page loaded into a tab may be annotated, a content script is dynamically injected into that tab, so that (1) existing annotations retrieved from the backend can be shown in the text as a highlighted passage with a popup on hover, and (2) a context menu is available to create new annotations.
The server declines injection for Buboflash's own pages, for mail.google.com, and for
anything that is not an http: or https: page.
No.