Viblyy — Privacy Policy

Chrome extension and the Windows and Mac apps “Viblyy” · Effective 1 September 2026 · Last updated 13 October 2026

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.

If you have linked the extension with the Viblyy app, it also reads what a site you allowed yourself calls itself (its site name, such as “SVT Play”), so the app can show that name while the site is playing.

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.

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

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, the Claude desktop app, the ChatGPT app and Codex. It has no analytics and no advertising. Unlike the extension, it asks you to sign in, and its account is the one thing it sends over the network (see Your account). Everything below that it looks at and stores stays on your computer.

What it looks at

• Which programs are playing sound, and their volume, through Windows, so it can turn them down and back up.
• What the player says it is playing. While Viblyy’s window is open, it asks Windows for the title, the artist and the cover the player has given Windows, to show them in the window. That is the program Viblyy turns down, or a browser that is playing while no extension is linked with the app. They are kept in memory while the window shows them: never written to the log or to a file, and never sent anywhere.
• 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, where Claude Code keeps the conversation’s transcript on your computer, and how many tasks Claude Code still has running in the background, as a number. It never holds what you or Claude wrote. If you connect Claude Code in WSL, the Linux inside Windows, the same hooks go into Claude Code’s own settings in each WSL distribution.
• 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; in its Code tab, the same for its “Stop” and “Send” buttons. 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.
• The Claude desktop app’s language. Viblyy finds Claude’s buttons by their English names, so it checks which language the Claude app is set to and tells you if it is not English. It reads only that setting from the Claude app’s settings file, and the list of languages in Windows’ settings, which the Claude app goes by when none is set.
• 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 ChatGPT app and Codex. The ChatGPT app for Windows and the Codex command line keep each conversation in a file on your computer, in the .codex folder in your user folder. Viblyy reads the lines added to the files of the last few days, and checks only whether a line says that an answer has started or finished. From the first line of each file it reads which program wrote it, the folder it runs in, and whether it is a helper’s conversation rather than yours. The text of your conversations is in the same files. Viblyy does not read it, keep it or send it anywhere. If you connect WSL, Viblyy also adds hooks to Codex’s own settings in each WSL distribution that has Codex, which tell the app when you send a message and when an answer is finished, in the same way as Claude Code’s hooks.
• The ChatGPT app’s buttons, and how busy it is. The ChatGPT app’s Chat mode keeps no such file. So, as for the Claude desktop app, Viblyy checks through Windows’ accessibility interface whether its stop button is showing and whether its send button is on, and never reads the text of the conversation or of what you are typing. While the window is minimised or behind another one, it also checks how busy the app is, as a share of the processor, to tell when the answer is finished.
• The Viblyy extension, if you link them. If you have both and turn on “Link with Viblyy Desktop” in the extension’s settings, the two talk on your computer, through Chrome, and nowhere else. The extension tells the app 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. The app tells the extension which assistant it is following (Claude Code, the Claude desktop app, the ChatGPT app or Codex), whether that answer is being worked on, waiting for your approval or finished, whether its music is down or it is paused, and its three music settings, so the extension can show them and use them; it never sends folder names, conversation ids or text. The extension’s “Open Viblyy Desktop” button asks the app to open its window.

Your account

The account exists so that Viblyy Desktop can be yours, and later be paid for. It knows who you are, and never what Viblyy did for you.

• What it holds. Your email address; an id; which way you signed in (Google, Microsoft, a code by email or a password); when the account was made and when you last signed in. If you chose a password, WorkOS keeps it hashed, in a form that can be checked against what you type and not read back; Viblyy never sees it. If you sign in with Google or Microsoft, that service also shares the name and the picture on your account with it, and they are stored with it; Viblyy does not use them.
• Who keeps it. WorkOS, Inc., in the United States, which runs the sign-in and stores the account on Viblyy’s behalf, as a processor under a data processing agreement, and uses it for nothing else. For security, WorkOS keeps a record of each signed-in session with the IP address and the browser it came from; the sign-in emails are sent through it too. Google or Microsoft, if you sign in with them, know that you signed in to Viblyy, under their own privacy policies.
• When it is made. An account cannot be made on a temporary address, one from a service that hands them out to anyone for a few minutes. So before WorkOS makes the account, it asks viblyy.com about the sign-up. The question holds your email address, the name you gave, and the IP address and browser it came from. viblyy.com looks up the address’s domain in a list of such services, answers yes or no, and keeps nothing of the question.
• What the app sends. When you sign in, the code from the sign-in page. After that, about twice a day, a request that keeps you signed in and confirms the account still exists. When you sign out or delete the account, that request. Each holds only the account’s tokens: nothing about your music, your conversations, which programs are playing, or when you use Viblyy.
• Offline. Viblyy keeps working for 30 days without reaching the server, and asks to check the account after that.
• Delete it. Settings, “Delete account”, removes the account and your email address from the server for good, and signs you out on the computer. You can also write to support@viblyy.com and it will be deleted for you.

Viblyy handles your email address because you need it to use the app (the performance of a contract, under the GDPR), and you can ask to see, correct or delete it at the address above.

What it stores

Everything else is on your computer and is never sent anywhere:

• Your sign-in, in the app’s folder, encrypted by Windows so that only your Windows user can read it: the tokens that keep you signed in, your account’s id and email address, and when the account was last confirmed.
• A log, 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 settings. It holds at most about 2 MB.
• The programs it has turned down, while they are down, in the same folder: each one’s name, the identifier Windows gives its audio (which contains the program’s location on your computer), and its volume before and after. If the app stops unexpectedly while the music is down, this is how it puts the volume back the next time it starts. The file is deleted as soon as nothing is turned down.
• How many answers each day had, and how long the music stayed down for them, in the same folder: one number of answers and one number of seconds per day, for the counts on the app’s first page. It holds no names, no times of day and nothing you or Claude wrote, and it keeps about a year.
• Your settings, in the same folder: what to do with the music, when it goes down, how far, whether it starts with Windows, light or dark, where you said you use Claude when you set it up, whether you have finished setting it up, and which of its suggestions you have closed.
• A note for Chrome saying where the app is, so that the extension can find it if you link them: a small file in the app’s folder, and an entry in the Windows registry pointing to it.

Deleting it

Uninstalling Viblyy from Windows removes the app and its folder, and with it your sign-in, the log, the list of programs it has turned down, the daily counts, and the file for Chrome. It does not delete your account: do that in Settings first, or write to support.

Before you uninstall, press “Clean up” next to “Before you uninstall” in the app’s settings. An uninstall cannot reach two things the app keeps outside its folder, and this removes both, then closes the app: Viblyy’s hooks in Claude Code’s settings file, in WSL too, if you connected Claude Code, and Chrome’s registry entry, under HKEY_CURRENT_USER\Software\Google\Chrome\NativeMessagingHosts\com.viblyy.desktop, which only says where the file for Chrome is and holds nothing about you. If you have already uninstalled, you can delete that entry with the Registry Editor, and remove the lines that run viblyy from Claude Code’s settings file by hand; left there, the entry points at a file that is gone, and nothing is started.

Viblyy for Mac

Viblyy is also a Mac app, downloaded from viblyy.com/mac. It does the same for Claude Code, the Claude desktop app, the ChatGPT app and Codex on a Mac, and turns down Spotify and Apple Music. Like the Windows app it has no analytics and no advertising, it asks you to sign in with the same kind of account (see Your account, which applies to it word for word), and everything it looks at and stores stays on your Mac.

What it looks at

• Spotify and Apple Music. Through macOS’ Apple Events, the way a script would, Viblyy asks these two players whether they are playing and at what volume, and tells them to go down, pause, play or go back up. The first time, macOS asks you whether Viblyy may control each of them, and you can change that in System Settings, Privacy & Security, Automation. It does not ask them what is playing, and it touches no other program’s sound.
• Claude Code, its transcript, and Codex, exactly as described for the Windows app above: the same hooks, the same yes-or-no reading of the transcript, and the same reading of the files in the .codex folder in your home folder. The text of your conversations is never read, kept or sent.
• The Claude desktop app’s buttons, if you allow it. Through macOS’ accessibility interface, Viblyy checks whether Claude’s “Stop response” button is showing, and whether its “Send message” button is on; in its Code tab, the same for its “Stop” and “Send” buttons. To find them it goes through the parts of the Claude window and asks each what kind of part it is; only a button is asked its name. It never reads the text of the conversation or of what you are typing. macOS lets no app do this until you turn it on yourself, in System Settings, Privacy & Security, Accessibility; until you do, and again if you turn it off there, Viblyy does not look at the Claude app’s window at all. That permission would let an app read and control other apps’ windows; Viblyy uses it for these buttons in the Claude app, the same in the ChatGPT app, and for nothing else, and controls nothing with it.
• The ChatGPT app’s buttons, if you allow it. Under the same permission and in the same way as for the Claude app: whether the ChatGPT app’s stop button is showing and whether its send button is on, never the text of the conversation or of what you are typing. And how busy the ChatGPT app is, as a share of the processor, for an answer that ends while its window is not showing.
• Which app is in front, through the same interface: whether it is the Claude app, the ChatGPT app or another one. Viblyy keeps nothing about the other app and looks at nothing in it.
• The Claude desktop app’s cache, how busy it is, and its language, exactly as described for the Windows app above: whether a new answer has been marked as finished in the file where the Claude app keeps the conversation it has open, in ~/Library/Application Support/Claude, never its text; the Claude app’s share of the processor; and the language setting in the Claude app’s settings file, with the list of languages in macOS’ settings.
• The Viblyy extension, if you link them, exactly as described for the Windows app above, through Chrome or another Chromium browser on your Mac and nowhere else.

What it sends over the network

Two things. The account’s requests, as described under Your account. And, once when it starts and once a day while it runs, a request for a single file, https://viblyy.com/mac/latest.json, which says which version of the Mac app is the newest, so the app can tell you when there is one to download. The request carries no parameters, no identifier, no version and nothing about you or your use of Viblyy; like any request it reveals your IP address to the server that answers, which is Viblyy’s own website, delivered by Cloudflare, Inc. You can turn it off in Settings, “Check for updates once a day”. The app never downloads or installs anything by itself.

What it stores

Everything is on your Mac and is never sent anywhere:

• In ~/Library/Application Support/Viblyy: your settings (the same choices as on Windows, and whether to check for updates); a log of what it saw and did, with times, the events above, conversation ids and folder names, at most about 2 MB; while the music is down, which player it turned down and its volume before and after, so that the volume can be put back if the app stops unexpectedly; and your sign-in, encrypted with a key that is kept in your login Keychain, under the name “Viblyy account key”.
• If you turn on “Open at login”, a small file in ~/Library/LaunchAgents, com.viblyy.desktop.plist, that starts the app when you log in.
• A note for each Chromium browser you have (Chrome, Edge, Brave, Vivaldi, Arc or Chromium) saying where the app is, so that the extension can find it if you link them: a file named com.viblyy.desktop.json in the NativeMessagingHosts folder of that browser’s own folder in ~/Library/Application Support.

Deleting it

Delete your account in Settings first if you want it gone too, and press “Disconnect” next to Claude Code for the same reason as on Windows. Moving Viblyy to the Trash removes the app, but macOS leaves what it stored where it is. To remove all of it, delete the Viblyy folder in ~/Library/Application Support, the file com.viblyy.desktop.plist in ~/Library/LaunchAgents, the files named com.viblyy.desktop.json in the browsers’ NativeMessagingHosts folders, and the item “Viblyy account key” in Keychain Access. None of them holds anything about you except the sign-in and the log.

Children

Viblyy is a volume control. It is not directed at children. The only personal information it collects from anyone is the Windows and Mac apps’ account, described above.

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.