privacy

Your code stays on your device.

The workbench is designed so routine code cleaning, formatting, conversion, and analysis happen inside the browser.

What the application stores and sends.

Workbench input

Pasted code and local files are processed by browser JavaScript and Web Workers. They are not submitted to the PHP application.

Local browser storage

The application can store the current draft, theme, and editor layout in localStorage on your device. Clearing site data removes those values.

Server requests

The web server receives normal request metadata needed to deliver pages and static assets, such as IP address, requested path, browser user agent, and timestamps.

Stripe Checkout

Starting a contribution creates a server-side Stripe Checkout Session and redirects to Stripe. Payment details are entered on Stripe's hosted page, not this site.

Optional advertising

Google AdSense code is loaded only when the site operator configures a publisher ID. When enabled, Google's own privacy and advertising technologies apply.

Offline cache

A service worker caches public application assets. Sensitive checkout endpoints and Stripe session pages are explicitly excluded from offline caching.

Icon delivery

Font Awesome CSS and font files are loaded from the version-pinned jsDelivr CDN. The CDN receives normal request metadata, but the code entered in the workbench is never included in those requests.