Clear tools with limited data collection

Browser tool input

The Slug Generator, JSON Formatter and Validator, UTM Campaign URL Builder, Hreflang Generator and Validator, and HTML, CSS & JavaScript Playground process the information you enter locally with JavaScript running in your browser. Their input is not uploaded to Foxger, and none of these tools needs an external API or backend to produce a result. The UTM builder parses destination text without visiting its URL. The hreflang tool validates URL structure and language settings without fetching or crawling any submitted page.

The Case Converter, Word & Character Counter, Text Compare / Diff Checker, and Text Cleaner also process text locally. Case conversion, language-aware counting, cleaning, and comparison run through JavaScript bundled with the Foxger page. The diff package used for comparisons is bundled locally; neither text is sent to that package's publisher or a third-party comparison service.

Foxger does not intentionally save that input in server storage, browser local storage, session storage, IndexedDB, cookies, or the Foxger page URL. As with any website, your own browser, device, or extensions may handle information according to settings outside Foxger's control.

Copying places output on your device’s clipboard only after you press a Copy button. Foxger does not request permission to inspect your clipboard. When you explicitly paste into Text Compare or Text Cleaner, the page handles only that pasted text locally so it can retain CRLF or LF line-ending information that a textarea would otherwise normalise. JSON, hreflang, Playground, Case Converter, Word Counter, Text Compare, and Text Cleaner download actions create files locally through a temporary browser Blob URL. These actions do not upload tool input or output to Foxger. The browser decides how to handle the file.

Code Playground processing and preview

The Playground's CodeMirror editors and its HTMLHint, CSSTree, and Acorn checking packages are bundled with Foxger and run in your browser. HTML, CSS, JavaScript, complete-document imports, diagnostics, console messages, and generated downloads are not intentionally uploaded to Foxger or another service. Code stays in memory for the current page and is not saved in local storage, session storage, IndexedDB, cookies, the Foxger page URL, or a Foxger account.

Preview execution happens in a restricted iframe with an opaque origin. The iframe allows scripts but does not receive same-origin access to Foxger. Its generated document includes a restrictive Content Security Policy and browser safeguards intended to restrict common external scripts, stylesheets, images, fonts, frames, workers, network APIs, navigation attempts, and form submissions. User JavaScript runs only after you select Run all code; automatic preview uses HTML and CSS without executing the JavaScript editor.

Normal use with ordinary learning code is designed not to fetch remote resources. The importer reports and skips external or unsupported resources rather than downloading them. Download HTML creates a local browser file through a temporary Blob URL, which Foxger revokes after use. Foxger does not keep a server copy of the file.

These restrictions reduce access and data flow, but browser sandboxing cannot guarantee that arbitrary JavaScript is harmless or prevent every possible side effect. A synchronous endless loop can still make the browser tab unresponsive. In some browsers, hostile code may also attempt to replace its own preview frame and initiate a remote navigation request. The Playground is intended for ordinary code that you understand or trust and is not a malware-analysis environment.

Appearance preference

When you choose System, Light, or Dark in the site header, Foxger may save that choice in your browser's local storage under the key foxger-theme. The value is limited to system, light, or dark so the same appearance can be restored when you reload or visit another Foxger page.

This preference stays in your browser. It is not tool input and is not used for advertising or cross-site tracking. Slug text, JSON, campaign details, hreflang entries, Playground code, case-conversion text, writing samples, compared drafts, and cleaned text remain unstored by Foxger's application code.

Optional external support

Foxger's support page contains an ordinary link to Buy Me a Coffee, an external service. Foxger does not embed Buy Me a Coffee scripts, widgets, payment forms, remote button images, or other resources during normal page viewing. Buy Me a Coffee receives a visit only after you choose to follow that external link.

Buy Me a Coffee's own privacy, payment, and terms practices apply after you leave Foxger. Foxger does not receive card or payment details. This support integration adds no Foxger cookies, browser storage, analytics, or tracking; foxger-theme remains the only expected Foxger local-storage key, and tool input remains unstored.

Accounts, advertising, and tracking

Foxger does not require an account and does not include advertising trackers or analytics scripts. Foxger's application code does not set non-essential cookies, so a cookie consent banner is not shown.

Hosting and security logs

Foxger is hosted using Cloudflare Workers and Cloudflare's static asset delivery. Cloudflare may process standard technical information needed to deliver and protect the site, such as an IP address, browser or user-agent details, requested URL, request time, and security events.

The handling and retention of infrastructure logs are subject to Cloudflare's services, configuration, and policies. Foxger does not use those logs to intentionally capture the text or code entered into Foxger’s browser tools because normal tool processing does not add that input to page or asset requests. Requests for tool pages and locally bundled scripts, editor packages, analyzers, or the diff package remain ordinary Foxger asset requests and may appear in those routine logs, but text entered after a page loads is not part of those ordinary requests.

Scope and limitations

These practices reduce unnecessary collection, but they are not a promise of absolute anonymity or a legal guarantee. Normal internet requests still reveal technical data to the services involved in delivering a website.

Foxger cannot promise complete isolation for every possible program or guarantee that a browser, browser extension, device, or operating system will handle information exactly as Foxger's application code does.

Text tools cannot understand whether pasted material is secret, personal, or sensitive. Even with local browser processing, avoid placing secrets into any website unless you understand and trust the browser, device, extensions, and surrounding environment.

Changes to this page

Foxger's privacy practices may be updated as new tools or features are added. If a future feature needs different data handling, this page should be revised to explain the change, and its last-updated date will be changed.