Fieldkit FAQ

No. Tool logic runs as JavaScript in your browser. Fieldkit does not send your pasted payload to a Fieldkit server for formatting, encoding, or generation. Closing the tab clears what was on the page. See the Privacy Policy and About pages.

Fieldkit does not keep a server-side history of tool inputs or outputs. Advertising and analytics partners may retain visit-related data under their own policies. Browser cookies and cache follow your browser settings.

Client-side tools mean your pasted content is not processed on Fieldkit servers. Visiting the site still involves ordinary web requests (and, when ads load, third-party ad scripts). Privacy for tool input and privacy for page visits are related but not identical.

Display ads fund hosting and maintenance so the tools can stay free without signup. The publisher ID used on the site is ca-pub-7627561201008761. Core actions (format, convert, generate) are not gated behind a paywall or “watch an ad” wall.

Fieldkit does not upload tool input to Fieldkit for processing. Ad networks operate as third parties with their own scripts and policies. Do not paste secrets into any web page you do not control end-to-end if policy or compliance forbids it.

Modern evergreen browsers (current Chrome, Firefox, Safari, Edge) are the target. Tools rely on standard APIs such as JSON.parse, TextEncoder/btoa patterns, and clipboard where available. Very old browsers without ES6-era JavaScript may fail silently or partially.

After a page and its scripts are cached, many tools keep working without a network for the conversion itself. First load still needs the network. Ads and consent prompts may not work offline. There is no dedicated installable offline app package.

Each page does one job. Examples: the JSON tool is strict JSON (no comments/trailing commas); cron follows common five-or-six-field expressions but is not a full ops scheduler; regex uses the browser’s JavaScript regex engine, which differs from PCRE or Rust regex in places. Read the explainer on each tool page for “what this tool does not do.”

No. Fieldkit is a set of static pages, not a hosted API. For pipelines, use libraries in your language or local CLI tools. The JSON guide and cron guide describe concepts you can reapply outside the browser.

Use the Contact page. Include the tool name, browser, and steps. Feature ideas should fit the browser-only, no-account model.

Start with Pretty-printing JSON safely and Cron expressions in practice. More guides may appear as tools grow.