Privacy Policy for Audio Anchor
Last Updated: January 25, 2026
1. Introduction
This Privacy Policy describes how the browser extension (the "Extension") handles information when you use it.
We are committed to protecting your privacy. The Extension is designed to work without collecting or transmitting your personal data to any external server.
2. Single Purpose
The Extension has one purpose: it lets you designate a single “anchor” tab for audio playback and automatically mutes any other tab that becomes audible, preventing unexpected audio interruptions.
3. Data We Access
To provide its functionality, the Extension may access limited tab state and basic tab metadata:
- Tab state: audible/muted state, used to detect when a tab begins playing audio and to mute/unmute tabs.
- Basic tab metadata: tab title and URL, used only to show you which tab was muted and which tab is currently the anchor.
4. Data We Store
The Extension stores the following data locally on your device (in Chrome extension storage):
- Anchor tab selection: the anchor tab id.
- Preferences: the Auto-Anchor on/off preference.
- Temporary UI data: an in-memory list of recently muted tabs (up to 10 entries) used to populate the popup UI. This list is not synced anywhere.
5. Data We Transmit
None. The Extension does not send any tab data, URLs, or user content to external servers.
6. Data Sharing / Selling
We do not sell, trade, or share your data with third parties.
7. Permissions
The Extension uses permissions strictly for core functionality:
- tabs: Required to detect when a tab becomes audible and to mute/unmute tabs. The Extension may read basic tab metadata (title/URL) to display which tab was muted and which tab is the current anchor.
- storage: Required to save the anchor tab selection and Auto-Anchor preference so they persist across browser restarts.
- notifications: Required to show a notification when a new tab is auto-muted, with optional action buttons to switch the audio source.
Host permissions: The Extension does not request host permissions (no website-wide access patterns).
8. Remote Code
The Extension does not load or execute any remote JavaScript or WebAssembly. All code is packaged within the Extension, and it does not use eval().
9. Data Retention & Deletion
Stored settings remain only in your browser until you remove the Extension or clear its extension storage.
10. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will post the updated policy on this page and update the “Last Updated” date.
11. Contact Us
If you have any questions about this Privacy Policy, please contact us at:
Email: info@dkit.cz