100% Client-Side: Your files and tokens never leave your browser.

Privacy Policy

Effective Date: 2026-11-22 (UTC) • Architecture: 100% Client-Side Processing

The Short Version

All files, tokens, and payloads are processed 100% locally in your browser and never transmitted to any server. We use cookie-free, anonymized pageview analytics (Umami) solely to count aggregate tool usage.

1. Zero Payload Transmission or Server-Side Logging

All five DevPayload utilities—Parquet Inspector, Base64 Calculator, JWT Expiration Calculator, LLM Token Calculator, and Regex Match Counter—execute entirely in client-side JavaScript. There are no file upload endpoints, backend databases, or server-side logs of your inputs. Any JWT, Base64 string, Parquet file, prompt text, or regular expression you enter stays strictly inside your browser's local memory.

2. Local Browser Storage

DevPayload uses browser storage strictly for local user experience preferences:

  • localStorage: Stores your dark/light theme preference (devpayload-theme).
  • sessionStorage: Temporarily passes input from the homepage Quick Auto-Detect box to a tool page and immediately deletes the entry once read, so sensitive tokens never appear in URLs or browser history.

3. Cookie-Free, Anonymized Analytics (Umami)

We use Umami Cloud—a privacy-focused, cookie-free, GDPR-compliant analytics service—solely to count aggregate pageviews and high-level tool navigation clicks (such as which tool page was opened). Umami does not set tracking cookies, does not collect personally identifiable information, does not track you across websites, and never receives any of your files, tokens, or text payloads.

4. Independent Verification

You can independently verify our zero-upload guarantee at any time by opening your browser's Developer Tools Network tab while dropping a Parquet file or decoding a JWT. Only anonymized pageview/event pings to Umami occur; zero payload bytes ever leave your device.