Viblyy — Privacy Policy
The short version. Viblyy turns your music down while an AI assistant writes an answer, and turns it back up afterwards. Everything it needs to do that stays on your computer. Viblyy has no account, no server, no analytics, and no advertising. It does not collect, transmit, sell or share your personal data. It never keeps what you or an AI assistant write: where it looks at text on the page, it is to answer a yes-or-no question — is the message box empty, has the answer begun — and the text is let go in the same step.
Who is responsible
Viblyy is made by Elliot Marions, an individual developer. Questions about this policy or about the extension can go to support@viblyy.com.
What Viblyy is for
Viblyy has a single purpose: to lower the volume of music playing in your browser at the moment an AI assistant’s answer arrives, and to raise it again when the answer is finished. Everything described below exists to serve that purpose and nothing else.
What Viblyy looks at
On the AI sites you allow
Viblyy needs to know three things: that you sent a message, that the answer has begun, and that it has finished. To tell, it watches the following, and nothing else:
- That a network request to the service started and finished. Viblyy observes the address, the timing and the outcome of the request the site makes when you send a message, and nothing else. It reads neither headers nor bodies, of requests or of responses: Chrome’s extension API hands those only to an extension that asks for them, and Viblyy does not ask.
- That you pressed Enter in the message box. Viblyy listens for the Enter key only; every other key is ignored the moment it is pressed, and no keystroke is recorded. If a site has changed its layout so that the message box cannot be found, Enter in any text field on that AI site counts instead. When Enter is pressed, Viblyy checks whether the box is empty — an empty box sends nothing, so that Enter is not a message. To make the check it looks at what is in the box, and keeps only the answer: empty or not.
- The label of a button you click — its accessible name, its tooltip, or the word written on it — to tell a send or stop button from any other. Nothing about the click is kept.
- That a stop button appeared or disappeared on the page.
- How much text has appeared in the part of the page that holds the answer, and on some services in the part that shows the assistant is working. Viblyy counts the characters; it does not keep them, and the count starts over with every message.
- Which part of the site you are on. claude.ai hosts Claude, Claude Code and Cowork at one address, and only the page’s path tells them apart.
None of this leaves the tab except as a short signal about timing — a message was sent, the answer began, the answer finished. None of the text Viblyy looks at is stored or sent anywhere: not your prompts, not the answers, not the labels of buttons. Viblyy does not read your conversation history, account details or cookies at all.
Tab titles. Viblyy’s popup names your open AI tabs by their titles, so that you can choose which one Viblyy follows. On most AI services a tab’s title is the name of the conversation. The titles are read from Chrome when the popup asks for them and shown there; they are not stored, and they are kept out of the diagnostic report on purpose.
On the music sites you allow
Viblyy looks for audio and video elements on the page so that it can change their volume, and reads whether they are playing and how loud they are. It does not read what is playing, your listening history, playlists, or account details.
Everywhere else
Nothing. Viblyy only runs on the sites listed in its permissions. It cannot read the address or the content of any other tab, and it has no access to your browsing history, your bookmarks, your downloads, or your saved passwords.
One thing it does see, stated so that the paragraph above is exact: to find the tab your music is playing in, Viblyy asks Chrome which tabs are currently making sound. For a tab on a site you have not allowed, Chrome withholds the address and the title, so what Viblyy learns is that some other tab is playing something — never which site, and never what. The diagnostic report shows those tabs as “unknown” for that reason.
What Viblyy stores, and where
All of it is stored by your browser, on your computer, using the extension storage Chrome provides. None of it is transmitted anywhere. None of it is readable by the developer or by any third party.
| What | Contains | Kept |
|---|---|---|
| Your settings | On/off, duck or pause, the volume level, the resume rule, when to quiet the music, theme | Until you change them or uninstall |
| Working state | Which tab is currently turned down, which AI tab has the controls — as browser tab numbers, not addresses | Cleared when the browser closes |
| Counters | How many times the music has been turned down today and in total, when it last happened, how many times under each mode, and the date each AI service was last seen in use | Until you uninstall |
| Support log | The last 20 events, each one a short code (for example duck,
restore, ai-tab-lost), a service name or domain, and a
timestamp |
Rolling; the 21st event pushes out the first |
| Debug trace | The last 120 diagnostic lines the extension wrote about its own behaviour | Cleared when the browser closes |
| Service list | A cached copy of the file describing which sites Viblyy can recognise. Contains no information about you | Until the next update |
The support log deliberately holds domains and never full addresses — no path, no query string, no fragment — and never a page title, a conversation name, or any page content. That rule is enforced in the code that writes the log, not merely by convention.
What Viblyy sends over the network
One thing, and it carries no information about you.
The service list
About twice a day, Viblyy requests a single file from
https://viblyy.com/providers.json. This is how
Viblyy learns that a site has changed its layout without you having to install an update.
The request carries no parameters, no body, no identifier, and no information about your
browsing, your settings, or your use of Viblyy.
Stated plainly for completeness: like any request to any website, this one reveals your IP address and browser user-agent string to the server that answers it. Since 14 September 2026 that server is Viblyy’s own website, delivered by Cloudflare, Inc.; before that date it was GitHub Pages. The change is worth stating because it makes the address Viblyy’s rather than a third party’s — what is sent does not change, and is still nothing but the request itself. Viblyy neither reads nor records it, and no profile, log or count of these requests is assembled from it; the traffic Cloudflare carries is covered by Cloudflare’s privacy policy. If you would rather not have Viblyy make this request, the extension works without it, using the list bundled with the installed version.
There is nothing else. Viblyy contacts no analytics service, no error reporting service and no advertising network. The one address above is the only server it contacts at all, and it is asked for a file rather than told anything. There is no account to create and no identifier assigned to you or your installation.
The support report
Viblyy’s settings page has a button that writes a short diagnostic report and copies it to your clipboard, so you can paste it into an email if you ask for help. Nothing is sent automatically: the report is created only when you press the button, it goes only to your clipboard, and you decide whether to send it and to whom.
The report contains the extension version, your browser and operating system, your settings, the domains of the music and AI services in use, the counters described above, the version of the service list, the domains you have granted access to, and the last 20 log events. It contains no full web addresses, no page or conversation titles, no page content, and no identifiers. You can read all of it before you send it, which is the reason it is kept short.
Why Viblyy asks for each permission
| Permission | Why |
|---|---|
storage | To remember your settings and counters between sessions. |
scripting | To place the small script that changes an audio element’s volume into music tabs, and the one that watches for the answer signal into AI tabs. |
alarms | To schedule the twice-daily check for an updated service list. |
webRequest | To observe that a request to an AI service started and finished — the earliest and most reliable sign that an answer is coming. Observation only: Viblyy does not block, redirect or modify any request, and does not read request or response bodies. |
nativeMessaging (optional) | Only if you turn on “Music in other apps too”: to tell the Viblyy Windows app on your computer when the music went down or back up, so it can do the same for other programs. Not asked for at install. |
| Site access to the listed AI and music services | Viblyy can only act on sites it is allowed to see. The list ships with the extension and you can view it on the settings page. |
What Viblyy never does
- It does not sell or transfer your data to third parties.
- It does not use your data for advertising, marketing, or profiling.
- It does not use your data to determine creditworthiness or for lending purposes.
- It does not use your data for any purpose unrelated to turning your music down and back up again.
- It does not track you across sites or build a profile of your activity.
- It does not store or transmit the content of your conversations with an AI assistant, and it looks at that content only as described above.
Viblyy’s use of information received from Google APIs, and of all data it handles, adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Your control over your data
- See it. The settings page shows what Viblyy can reach, and the diagnostic button shows everything Viblyy has recorded.
- Switch it off. The main switch in the popup stops Viblyy acting on anything, without removing it. The sites listed above ship with the extension and are what it is for, so Chrome does not offer them up one at a time; uninstalling withdraws them all at once.
- Delete it. Removing the extension from Chrome deletes everything listed above. There is no copy anywhere else, because none was ever made.
Viblyy for Windows
Viblyy is also a Windows app, from the Microsoft Store. It does the same thing for AI assistants that run outside the browser: Claude Code and the Claude desktop app. Like the extension, it has no account, no server, no analytics and no advertising, and it sends nothing over the network.
What it looks at
- Which programs are playing sound, and their volume, through Windows, so it can turn them down and back up.
- Claude Code. If you add Viblyy’s hooks to Claude Code, Claude Code tells the app when you send a message, when an answer is finished, and when it waits for your approval. Each message holds the kind of event, Claude Code’s id for the conversation, the folder it runs in, and where Claude Code keeps the conversation’s transcript on your computer. It never holds what you or Claude wrote.
- The Claude desktop app’s buttons. Through Windows’ accessibility interface, Viblyy checks whether Claude’s “Stop response” button is showing, and whether its “Send message” button is on. It checks whether the buttons are there, and never reads the text of the conversation or of what you are typing.
- The Claude desktop app’s cache on your computer. While the Claude window is minimised, its buttons cannot be seen. So Viblyy reads the file where the Claude app keeps the conversation it has open, and checks only whether a new answer has been marked as finished: an answer’s id, and whether it is done. The text of your conversations is in the same file. Viblyy does not read it, keep it or send it anywhere.
- How busy the Claude desktop app is, as a share of the processor, as a fallback for the same question.
- Claude Code’s transcript. If you choose to have the music go down as the answer arrives, while Claude is working on an answer Viblyy reads the lines Claude Code adds to the conversation’s transcript file on your computer, and checks only whether a line is Claude’s finished answer: what kind of line it is and whether it ends the turn. This works when the window is hidden and in a terminal. The text is in the same file; Viblyy does not read it, keep it or send it anywhere.
- The Viblyy extension, if you connect them. If you have both and turn on “Music in other apps too” in the extension’s settings, the extension tells the app, on your computer, when it turned the music down or back up, and on which AI site (for example claude.ai). Nothing from the page is in the message.
What it stores
A log on your computer, in the app’s own folder, of what it saw and did: times, the events above, conversation ids and folder names. It helps with support when the music did not do what you expected, and you can open it from the app’s menu. It holds at most about 2 MB and is never sent anywhere. The app also remembers your settings, such as whether it starts with Windows.
Deleting it
Uninstalling Viblyy from Windows removes the app, its log and its settings. If you added its hooks to Claude Code, remove them from Claude Code’s settings file as well.
Children
Viblyy is a volume control. It is not directed at children, and it collects no personal information from anyone, of any age.
Changes to this policy
If Viblyy ever begins handling data differently, this page will be updated before the change ships, and the date at the top will change with it. A change that would mean collecting or transmitting personal data would be announced in the extension itself, not only here.