Your tool inputs stay on your device.
DevPantry is designed for working with images, tokens, and test data without sending that content to a DevPantry application server.
Privacy policy · Last updated October 30, 2026
Tool inputs
Images, JWTs, schemas, and generated data are processed in your browser.
Usage analytics
Google Analytics and Cloudflare Web Analytics help us understand visits and tool usage. Tool inputs are not included in our custom events.
Browser storage
The theme, collaboration drafts, and analytics identifiers may be stored in your browser.
How DevPantry handles data
What stays in the browser
Image editing, background removal, PDF processing, mock-data generation, JSON conversion, and JWT decoding process their inputs locally. These tools do not upload input files or tokens to a DevPantry processing API.
What we collect
No account is needed to use the tools. We use Google Analytics and Cloudflare Web Analytics to measure visits, device/browser information, referring sites, and tool usage. Our custom completion events contain a tool identifier and an action such as copy or download—not file contents, file names, JSON, JWTs, or generated output. Page URLs sent by our Google Analytics integration omit query strings and URL fragments. Advertising personalization and Google signals are disabled in that integration.
Google Analytics may use cookies to distinguish visits. Google and Cloudflare also process technical request information to deliver their services. Our Google Analytics integration respects the browser’s Do Not Track setting. DevPantry currently serves no advertising.
Network features
Font and icon previews request assets from their providers. The social-preview URL fetch sends the URL you enter to our metadata-fetch service. The collaborative editor encrypts document updates in your browser, then relays and stores the encrypted updates through a Cloudflare Durable Object so other participants can synchronize. Its room key is derived locally from the password. These features need a network connection even though file editing and token processing happen locally.
Feedback
Feedback is submitted through Formspree, including your message and any optional contact details you provide.
Browser storage
The site stores interface preferences locally. The collaborative editor may save its document in IndexedDB for local persistence. Analytics cookies can also be present. Image processing and JWT inspection do not intentionally save their inputs to browser storage. Shared JSON links place the JSON in the URL fragment, so anyone you give that link to can read the payload.
Your choices
You can clear the theme preference through your browser’s site-data controls. Do not enter secrets into any web tool unless you trust the browser and device you are using.