How DevPocket actually handles your data

How DevPocket actually handles your data — not a marketing claim.

DevPocket is a static site with no backend server and no database. That is not a design choice made for this page — it is the actual architecture, and it is why the claims below can be specific instead of vague. Where a tool cannot honestly make the same claim, its page says so.

What is processed locally

Every tool on DevPocket — JSON, XML, SQL and YAML formatting, JWT decoding, diffing, hashing, cron parsing, mock data generation, and the rest — runs as JavaScript in your tab. Your input is read into memory, transformed, and rendered back to the same page. It never leaves the browser process.

What is sent externally

Nothing you type or paste into a tool is sent while you work. The page shell — the JavaScript/CSS bundles and the Inter font from Google Fonts (fonts.googleapis.com, fonts.gstatic.com) — loads once per visit regardless of what you do afterward. No tool currently calls an external API — if one ever needs to, its page will carry a "Needs network" badge instead of "Runs locally" and state exactly what is sent and why. The feedback form below sends what you write in it, and only when you press its Send button.

Feedback form

The feedback form (in the header and the footer) sends what you typed into it only when you press Send. What goes out is exactly its fields: the kind of feedback, your message, your email if you chose to give one, and the page address unless you untick it — never the input of the tool you were using. It is delivered to [email protected] through Web3Forms (web3forms.com), a form-to-email service, and is used only to read and answer your feedback.

Error monitoring

None. There is no Sentry, Bugsnag or similar service wired in, so a JavaScript error in your browser is never reported anywhere — you would only see it in your own DevTools console.

Local storage

A few small preferences live in your browser's localStorage, scoped to devpocket.in: your theme choice, the paths of your last few visited and favorited tools, the sizes you've dragged split panes to, and the time zones you picked on the timestamp converter. None of it holds the text, tokens or files you paste into a tool — only UI state and tool paths. IndexedDB is not used. Clear it any time via your browser's site data settings.

Service worker / offline

DevPocket registers a service worker so it works offline and can be installed as an app. It caches the site's own files only — the HTML, JavaScript, CSS, icons and the Inter font — so tools open without a connection. It never sees or stores anything you type or paste, and it sends nothing anywhere. You can inspect or remove it under Application → Service workers and Cache storage in DevTools.

How to verify this yourself

Open your browser's DevTools (F12, or Cmd/Ctrl+Shift+I), switch to the Network tab, and use any tool — paste a JSON payload, decode a JWT, generate a hash. Reload the tab list if it's filtered. While you type or paste into a tool, nothing fires: no request carries your input in its body, headers or URL. That is the claim, and it is checkable in under a minute without trusting this page at all.

Found a tool that doesn't match this description? That would be a bug — .

FAQ

Is there error tracking?

No. There is no error reporting service, so a JavaScript error in your browser is never reported anywhere — you would only see it in your own DevTools console.

What is stored in my browser?

Your theme choice, your favourite tools, the tools you opened recently and your split-pane widths — all in localStorage, all readable by you in DevTools under Application. Tool inputs are never written there.

How can I verify any of this myself?

Open DevTools, go to the Network tab, clear it, then type or paste into any tool. If your input were being uploaded, a request would appear as you type. None does.