Privacy Policy
Effective September 2026
The short version: we cannot see your data. Every tool on DevWorkBench runs entirely in your browser. Inputs are never uploaded, transmitted, logged or stored on any server. If you copy a result and it ends up somewhere else, that is your browser doing exactly what you told it to do.
1. What runs where
All processing — JSON parsing, Base64 encoding, hashing, diffing, regex matching, UUID generation and URL encoding — happens in your browser using JavaScript. Closing the tab deletes everything except the small preferences described below. The site requires no network requests to perform any tool operation.
2. What we store on your device
The only things we ever save are stored in your browser's localStorage (a small, device-local storage area that never leaves your machine):
- Your theme preference (dark / light).
- A short list of recently used tools (for convenience, cleared on demand).
- Your cookie consent choice (stored only so we respect it on future visits).
- A local entitlement claim for the paid tier, when it launches (see section 6).
None of these values are sent anywhere. They live on your device only and you can clear them at any time from your browser settings.
3. Cookies
The tools themselves set no cookies. Every utility runs locally in your browser, so using the site's core features requires no cookies whatsoever. The only things stored on your device before any choice are local preferences (section 2) and a short-lived region cookie so we can show the right privacy controls.
When you first visit, a banner asks how you'd like to handle optional data collection, with two choices of equal prominence:
- Essential only: no analytics, no ads. Nothing but the local preferences in section 2 is stored, and we remember that you chose this.
- Accept all: enables aggregate analytics (Google Analytics) and ads (Google AdSense) as described below.
Your choice, together with a timestamp and the policy version, is recorded on your device for record-keeping, and you can change it at any time via Cookie settings in the footer. In the EEA, the UK and Switzerland, Google's certified consent platform (Privacy & messaging) presents a more detailed, per-purpose dialog before any ad or analytics personalization runs.
4. Where your data could go
Nothing you type into a tool is ever transmitted — to us or anyone else. The only data that can leave your browser is the standard usage information the optional services below receive after you accept, described in their own policies:
| Storage / service | Purpose | Provider | Duration |
|---|---|---|---|
| df_region | Regional privacy controls (strictly necessary) | DevWorkBench | 7 days |
| devworkbench:consent | Your consent choice + timestamp (localStorage) | DevWorkBench | Until you clear it |
| theme, recent tools, plan | Local preference (localStorage) | DevWorkBench | Until you clear it |
| _ga, _ga_*, _gid | Aggregate analytics (after consent) | Google LLC (US) | Up to 24 months |
| AdSense / funding choices | Advertising + consent messaging (after consent / per CMP) | Google LLC (US) | Per Google's policies |
Third parties we work with: Google LLC, which operates Google Analytics and Google AdSense. Both may set cookies, collect standard device and usage data (IP address, user agent, pages visited) and may transfer that data to the United States, in accordance with Google's privacy policy and the EU–US Data Privacy Framework. We do not select or share tool inputs with anyone — ever. The parties are listed here as required by Google's EU User Consent Policy.
We fund the free tier with unobtrusive ads in dedicated slots on tool pages — never blocking your work. Ads are disabled until both the site owner configures advertising and you accept. You can opt out of personalized advertising via your Google Ads Settings, and non-EU visitors can always switch to “Essential only” from the footer.
5. Our internet presence
The site is served by a hosting provider's edge and origin infrastructure. Like any web host, that provider processes standard web request metadata (your IP address, user agent, requested URL) in server logs to run the service and maintain security. This is infrastructure-level logging and is unrelated to tool inputs, which never reach a server in the first place.
6. Paid tier (future)
When a paid tier launches, payment details will be handled entirely by our payment processor (e.g. Stripe); we never see or store your card details. Until that happens, a locally stored flag is used only for development/demo purposes and cannot unlock higher limits or ad-free browsing on the live site. When billing ships, entitlements will be verified server-side before higher limits or an ad-free experience activate, so a locally typed flag can never grant paid features.
7. Children and sensitive data
The service is intended for developers and technical users of all ages. We do not knowingly collect personal information from anyone, because — to be blunt — we do not collect information from anyone at all.
8. Changes to this policy
If we ever need to change how the site works, this policy will be updated and the effective date above will change. Because our core promise (local processing) is unlikely to change, material changes of this privacy posture would be announced prominently.
9. Questions
If you have any questions about this policy, visit the About page or send a message via the contact page.
Manage cookies
Re-open the consent banner to review your choice. Analytics and ads only run after you accept them.