Privacy Policy
Last updated: April 2026
What gets stored
Your settings (suspend timer, whitelist, preferences) are saved using Chrome's built-in storage APIs. Settings go to chrome.storage.sync so they follow your Chrome profile across devices. Stats and saved sessions use chrome.storage.local. Tab timestamps use chrome.storage.session, which Chrome wipes when the browser closes. None of this is ever sent to a third-party server.
Permissions
Drowzy requests only the permissions it needs to do its one job:
tabsListing, suspending, and restoring browser tabs.storageSaving your settings and sessions locally.alarmsPeriodic checks for inactive tabs (every 60 seconds).contextMenusRight-click menu options for suspend and whitelist.scriptingInjecting a small script to detect unsaved form data before suspending a tab. Opt-in only.sidePanelDisplaying Drowzy in Chrome's side panel.<all_urls>Optional host access, requested on-demand only when you enable Form Protection or Suspended-Tab Marking. Never requested at install. Revocable anytime.
Your data
Because nothing leaves your browser, there's no dashboard, no account, and no way for us to see what you've done with Drowzy. If you uninstall Drowzy, Chrome offers you a chance to send optional feedback (reason for uninstalling, browser, OS) through a separate web page; that submission is explicit and goes to an anonymous form. You can skip it by closing the tab.
Contact
Questions, concerns, or data requests? Email drowzyextension@gmail.com.