[ DEV STUDIO v1.0 ]|[ MEMORY: EPHEMERAL // ZERO DISK ]
[ PRIVACY GUARANTEE ]
</>DEV STUDIO
ARCHITECTURAL PRIVACY GUARANTEE

PRIVACY POLICY // ZERO PAYLOAD RETENTION

Effective Date: November 2026 • 100% In-Browser Volatile Memory Architecture

[ ARCHITECTURAL CORE: 100% CLIENT-SIDE EXECUTION ]

All JSON Web Token decoding, cryptographic hash calculations (MD5, SHA-1, SHA-256, SHA-512, CRC32), regular expression matching, Base64/URL encoding/decoding, and CRON expressions execute strictly inside your local browser runtime memory (JavaScript V8 / Web Crypto API / HTML5 FileReader). Your sensitive API tokens, passwords, private keys, test strings, and uploaded files are NEVER uploaded to backend servers, NEVER written to disk, and NEVER shared with any third party.

1. Sensitive Data We Never Collect Or Transmit

  • We do NOT transmit or record your JWT tokens, auth headers, or token claims.
  • We do NOT inspect or store passwords, secret keys, or cryptographic salt strings.
  • We do NOT store files, images, or documents dropped into the Base64/Hash generators.
  • We do NOT save regular expressions, search queries, or evaluated candidate text.
  • We do NOT use persistent profiling cookies, session cookies, or ad trackers.

2. Anonymous Telemetry & Operational Metrics

To monitor infrastructure health, prevent denial-of-service abuse, and verify operational uptime, our backend accepts lightweight, anonymous telemetry metrics via non-blocking background beacons:

  • Action Label: An anonymous event identifier (e.g. `jwt_decode`, `base64`, `regex_test`, `hash_gen`, `cron_parse`).
  • Tool Name: The feature toolset invoked (e.g. `jwt`, `base64_url`, `hash`, `regex`, `cron`).
  • Client IP Address: Derived from standard reverse proxy headers (`CF-Connecting-IP`, `X-Forwarded-For`) for rate limiting and network security auditing.
  • Client User-Agent: Truncated browser engine metadata for platform compatibility.

CRITICAL PRIVACY SPECIFICATION: Telemetry beacons contain ZERO payloads, ZERO token strings, ZERO file contents, and ZERO hash pre-images.

3. Local Browser Storage & Session Lifecycle

Dev Studio operates entirely ephemerally. When you close or refresh your browser tab, all volatile runtime memory containing tokens, strings, and hashes is instantly purged by your operating system garbage collector.

4. Open Verification & Security Auditing

Developers can inspect their browser's DevTools Network panel (F12) at any time to verify that zero request payloads containing their sensitive strings or tokens are dispatched across the wire.