Last updated: 2026-09-20
Contact: [email protected]
DozeTab does not send anything anywhere. No servers, no analytics, no accounts. Everything it remembers stays on your computer, or moves only through your own Chrome sync — never through the developer.
Keep several sites in one side panel. Close it and reopen — you are where you left off.
DozeTab makes no network requests of any kind. No fetch, no XHR, no analytics SDK, no telemetry, no crash reporting, no server.
Verified by searching the entire source tree for fetch(, XMLHttpRequest, outbound http(s):// calls, and every common analytics SDK (Google Analytics, Sentry, Mixpanel, Amplitude, PostHog, Segment) — none exist. The only place xmlhttprequest appears in the code is as a filter value inside Chrome's built-in declarativeNetRequest API, which only rewrites headers on requests your browser already makes to sites you open — it does not create requests of its own.
The developer cannot see any of your data. None of it is ever sent, so there is nothing to see.
| Kept | Where it lives | Leaves your computer? |
|---|---|---|
| Which sites are open in the panel and their addresses | This computer only | No |
| Panel layout and sizes | This computer only | No |
| Desktop or phone choice per site | This computer only | No |
| Saved page state (see below) | This computer only | No |
| Saved sets of addresses ("presets") | Your Chrome account sync | Only between your own signed-in Chrome browsers |
| Buttons you made yourself | Your Chrome account sync | Only between your own signed-in Chrome browsers |
Chrome sync is Chrome's own feature, moving data between browsers you are signed into with your own Google account. It never reaches the developer.
So a slot comes back exactly where you left it, DozeTab keeps:
Limits:
| Limit | Value |
|---|---|
| Sites kept | 50 max |
| Age kept | 30 days max, then dropped |
| Fields per page | 60 max |
| Characters per field | 20,000 max |
| Total size | 4 MB max |
Oldest data is dropped first once a limit is hit.