Privacy Policy

Last updated: 2026-10-04

1. Who this covers

This policy covers the Modulate browser extension (Chrome and other Chromium-based browsers), this website (modulate.top and any Vercel-hosted preview of it), and any email you send to support. It applies to every version of Modulate distributed through the Chrome Web Store or as a packaged file.

Modulate is built and maintained by a single independent developer, not a company. That has not changed how carefully this is written: an extension that can touch every tab's audio has no business phoning home, so it does not.

Questions about this policy: support, or email chinhfey9009@gmail.com.

2. Our privacy promise

Modulate is built to give every tab its own volume. It is not built to watch you, measure you, or monetize you. In concrete terms:

• We do not sell or rent personal data. There is none to sell.
• We do not build advertising profiles from your browsing, tabs, or audio.
• We do not run analytics, telemetry, crash reporters, or usage pings inside the extension.
• The extension does not use cookies or local storage for tracking. The only local storage is your per-tab volume settings (section 4).
• We do not send your browsing activity, tab titles, page content, or audio information anywhere, ever.

If a future version of Modulate ever needs to change any of this, this page will be updated first with a new "Last updated" date, and the change will be called out in the Chrome Web Store listing. Silence is not consent: no change is made quietly.

3. Information we do not collect

Nothing. Modulate does not collect, transmit, log, cache, or have any mechanism to collect the following, or anything else:

• Personal information (name, email address, account identifiers, payment details)
• Browsing history, page content, form input, or URLs you visit
• Tab titles, favicons, or which sites are playing audio (read only in memory to render the mixer, never stored off-device)
• Analytics, telemetry, feature-usage counts, or A/B experiment flags
• Crash reports, diagnostic logs, or stack traces
• IP addresses, device fingerprints, advertising identifiers, or cross-site cookies
• Audio content, microphone input, or anything audible in a tab

Modulate has no application server and no backend. There is nowhere for your data to go, because that path was never built.

4. Information stored on your device

The only data Modulate handles at all is your per-tab volume and mute level, saved locally with Chrome'schrome.storage.local API. In plain terms, when you drag a slider or mute a tab, that one number is written into your own browser profile so the next time you open the popup, the slider is where you left it.

Each entry is keyed to a specific browser tab. It is deleted automatically when that tab closes. This local data:

• Never leaves your device or browser profile
• Is not accessible to the developer, to us, or to any third party
• Is not synced to any account or cloud service (unless you yourself enable Chrome Sync, which is Chrome's feature, not Modulate's)
• Is not used for profiling, recommendations, or advertising
• Disappears completely when you remove the extension or clear site data for it

You can also reset any single tab from the popup (reset that tab to 100%, unmuted, adjustments cleared) without uninstalling anything.

5. Permissions we request, and why

Chrome requires every extension to disclose why it needs each permission. Here is the complete list Modulate requests, and the exact, sole reason for each:

• tabs: read tab titles, icons, and audible state, so each playing tab can be shown and identified in the mixer. Titles and icons are rendered in the popup UI only; they are not written to storage or sent anywhere.
• storage: remember each open tab's volume and mute level for as long as that tab stays open (see section 4).
• scripting and host access: apply the volume level you set to that page's audio output, by injecting a small audio-adjustment script into the tab. That script changes playback volume in that tab. It does not read the page, send anything out, or persist anything.

No permission is used beyond that single stated purpose. None of them are used to read, log, or transmit page content, browsing activity, or personal information, at any time. There is no background worker that phones home, no update ping beyond what the Chrome Web Store itself does, and no hidden permission.

6. How your information is used

Since nothing is collected off-device, there is nothing to use, sell, rent, train models on, or analyze. The one piece of local data Modulate keeps, your per-tab volume setting, exists for exactly one purpose: so the tab stays at the level you set it to. That is the whole loop.

When you contact support by email (section 8), whatever you choose to write in that email is handled only to answer you and fix the problem. It is not added to a mailing list, not shared with third parties for marketing, and not used to profile you.

7. Sharing and third parties

Modulate shares no user data with anyone, for the simple reason that it collects none to share. Specifically:

• No third-party analytics SDKs inside the extension
• No advertising networks or attribution partners
• No crash-reporting or session-replay tools
• No data brokers, no "service partners" receiving usage data
• No sale, rental, or disclosure of personal data for any purpose, commercial or otherwise

The only external hosts the extension itself contacts are public font CDNs (jsDelivr, Fontshare, and Google Fonts) so the popup can render its typefaces. Those requests are ordinary font file loads, the same kind any website makes. They contain no Modulate data and nothing about your tabs or audio.

This website is hosted on Vercel. Like any host, Vercel's infrastructure may process standard technical logs (IP address, request time, requested path) for delivery and security. That is the host's processing of ordinary web traffic, not Modulate collecting product data. The extension never talks to this website.

8. Support email and this website

If you email support, we receive what you send: your message, any screenshots you attach, and the email address you write from. We use it only to reply, debug, and (if you allow) improve Modulate. We may keep the thread while it is useful for follow-up, then it is ordinary mail in a personal inbox, not a CRM record.

We do not add support contacts to a newsletter. We do not sell or share support correspondence. If you want a copy of what you sent, or want it deleted, ask and it will be done.

This website, as opposed to the extension, does use analytics. It uses Google Analytics (GA4) to count visits and see which pages are read, and Google Search Console to see how the site appears in Google Search. Google Analytics does not load, and sets no cookies, until you accept it in the cookie banner. If you accept, it sets cookies in your browser and sends standard visit data to Google: the page you viewed, how you arrived, your browser and device type, and an approximate location. We use it only to understand and improve the site. We do not run ads, and we do not connect it to anything the extension does, because the extension never talks to this website. You can change your choice at any time with Cookie settings in the footer. You can also use your browser's cookie settings or Google'sAnalytics opt-out browser add-on. Search Console reports search performance to us and adds nothing to your visit.

The home page also keeps a small flag (modulate:entered) in your browser's local storage so its short intro plays only once, and another (modulate:consent) to remember your cookie choice. Both stay on your device and are never sent anywhere. The website has no chat widgets or advertising trackers. It loads its fonts from public font hosts (jsDelivr, Fontshare and Google Fonts) and, for analytics, Google.

9. Data security and retention

Because everything product-related stays local, Modulate's security model rests on the same sandboxing Chrome already provides to chrome.storage.local: your settings live in your own browser profile, isolated from other extensions and sites, and protected by whatever device-level security you already have in place. There is no remote database to breach, because there is no remote database.

Retention, in short:

• Local volume settings: until the tab closes, or until you clear them or remove the extension.
• Support emails: as long as needed to finish the conversation and any reasonable follow-up, then ordinary mail retention.
• Website host logs: whatever standard operational window the host keeps for delivery and abuse prevention. Not used by us to profile visitors.

No online system can promise perfect security. The honest claim is narrower and stronger: there is almost nothing here to steal.

10. Your rights and choices

Regulations like the GDPR and CCPA give you the right to access, correct, delete, port, or opt out of the sale of your personal data, and to lodge a complaint with a supervisory authority. Modulate makes all of those automatic by never collecting off-device data to begin with. There is no access request to fulfill, because there is no personal database holding you.

What you can still do on your own device, at any time:

• Reset a tab's volume from the popup
• Clear all stored settings by removing the extension (which deletes its local storage with it)
• Disable or mute Modulate's access per site using Chrome's own site controls
• Ask support any privacy question, including "what do you have on me?" (the answer is: nothing)

If you email a privacy request, identity may be checked only as far as needed to make sure the reply goes to the right person. Send requests to support orchinhfey9009@gmail.com.

11. Children's privacy

Modulate is not directed at children and does not knowingly collect information from anyone, child or adult, for the reasons already covered above: it has no data collection to speak of. If you believe a child has sent personal information to support by email, contact us and it will be reviewed and removed where appropriate.

12. International users

Because all of your Modulate settings stay on your own device and none of it is transmitted anywhere by the extension, no cross-border data transfer of that data ever takes place, no matter where you use Modulate from. Support email and this website's host may process data in the infrastructure regions their providers use; that covers only messages you choose to send, ordinary web traffic to this site and its analytics (section 8), not anything the extension collects (it collects nothing).

13. Legal requests

If we ever receive a lawful demand for data about you, the response starts from an empty set: the extension does not hold account data, browsing data, or usage data to hand over. For email you sent to support, any disclosure would be limited to what the law actually requires, and only after reviewing the request. We do not proactively monitor, scan, or pre-archive anything for law enforcement.

14. Changes to this policy

If this policy ever changes, the updated version will be posted here with a new "Last updated" date at the top. Material changes (anything that would let Modulate collect or share more than it does today) will also be reflected in the extension's Chrome Web Store listing so you can see them before you update. Minor clarifications and wording fixes may only refresh the date on this page.

We will not silently reverse the "no collection" promise. If that ever had to change, it would be a new product decision in the open, not a quiet paragraph edit.

15. Contact

Questions, concerns, or data requests about this policy:

• Support page
• Email chinhfey9009@gmail.com

You will get a real reply from the person who built Modulate, not a ticket bot.