Local YAML editing with optional assistance.

Last updated: 29 October 2026

This policy covers YAML File Tools, operated by Ship It! Software Limited. It also covers the separately installed desktop editor and optional browser extension usage statistics, described below. Website, desktop and extension practices are separate.

Local file handling

Selected files, pasted YAML, parsed values, and generated downloads are processed locally in your browser. Local editing does not intentionally transmit file names, keys, values or contents to our servers. Read-only Query document evaluates JSONata locally in a dedicated worker and creates a separate JSON result download; queries do not call a model service. Query drafts and results stay in the open workspace. Optional assistance is a separate explicit action described below. The sample is embedded in the application. Static reference navigation keeps original attached YAML/JSON documents, an explicitly captured current-source snapshot and JSON Schema text in this session only, within explicit size and attachment limits. F12, Follow reference and Cmd/Ctrl-click use the same local resolution path. Temporary safe JSON projections support local resolution; selections map back to original source. Explicit reference-document URI bases and attachments are not saved in schema preferences or automatically included in assistance. It performs local Worker resolution without fetching schema URLs or reading filesystem paths. Existing normalized schema preferences remain separate; restoring them does not reconstruct original source.

Optional YAML assistance

When configured, Assistance sends your goal and source text you explicitly select and include through this product's server to OpenRouter and the configured model provider. The interface shows the included text and configured model identifier. Attached schemas, local resources and unselected source are not automatically sent. Checking availability sends no document contents. Avoid including sensitive information you do not want those services to process. Service providers receive ordinary network information and apply their own processing and retention terms; no fixed provider retention period is promised here. The server requests restricted data collection and zero data retention; unavailable provider admission fails closed.

Desktop versions that offer a local provider can send the explicitly checked source and goal to an Ollama service on your computer at 127.0.0.1:11434 instead. The app does not install Ollama or download models. Refresh lists eligible downloaded models; Connect admits the selected model. The interface names the processing destination, and changing it clears prior context consent and drafts. Your service controls processing beyond that endpoint; use a downloaded model and disable cloud features when local-only processing is required. Availability depends on the installed version and platform, and this does not describe every current store release.

Generated source changes remain untrusted drafts. They must match the selected original text and pass local language and configured schema validation. Source, revision, selection, schema and processing-destination changes invalidate context consent and review authority. Apply is explicit and undoable, and does not save the source file. Cancelling prevents a later local Apply but cannot retract information already transferred. Provider credentials remain server-side. Local editing works without assistance; installed app and extension releases may have different feature availability.

Local recovery and preferences

Opening a file, pasted input, sample, or new document stores the original input in browser-local IndexedDB when available. Each recovery entry expires after 30 minutes. Expired entries are ignored and cleaned up on later use; expiry does not guarantee immediate physical deletion. Clearing this site’s browser data removes stored recovery entries. If storage is unavailable, the original input is held in memory for navigation in the current tab.

Input handoffs above 64 MiB in total stay in the current tab without copying the whole source into browser storage. This recovery-storage threshold is separate from each tool’s file-size limits. Reopen the original after refreshing, and download changes before closing the tab.

Edits and editor state stay in the open tab when you return to a marketing page and choose Resume. Refresh first restores the original input. The source editor can separately keep local source snapshots after a short idle delay. Preview a matching recovery copy before explicitly restoring it as an undoable source edit; recovery does not overwrite the original file or restore file permissions. Unapplied form drafts are not included. Source recovery offers expire 24 hours after the last backup, while expired bytes can remain until explicitly discarded or site data is cleared. Storage and quota limits apply; failed replacement retains the previous snapshot and displays a notice. Download important work separately. Closing a tab releases its live editor state but does not itself delete IndexedDB entries. Appearance and editor preferences may also be saved locally. Attached schema data, filename/document assignments, opaque attachment identities and explicitly reviewed modeline provenance use the existing local schema preferences. Modeline provenance stores the identifier and header line, not another copy of YAML source. Modeline suggestions never fetch URLs or filesystem paths and never apply automatically. A replacement attachment invalidates a reviewed assignment until explicitly reselected or reviewed again.

Ordinary web request data

Loading pages, policies, scripts, styles, and the favicon sends normal technical request data to Cloudflare, such as IP address, browser details, requested path, time, and security signals.

Purposes, cookies, and analytics

Request data is used to deliver and secure the site and diagnose availability. This website release does not set analytics cookies, create advertising profiles, or run product analytics.

Service providers and retention

Cloudflare hosts and protects the Worker and may process and retain request logs under its own operational policies. We retain only the technical information available through that service for as long as reasonably needed for security and reliability.

Security and choices

Browser-local processing limits exposure but no browser or network service is risk-free. You can avoid processing sensitive YAML here, clear this site’s browser data, download your edits before closing the tab, or use an offline tool.

YAML Editor desktop app

The separately installed desktop editor processes selected files and edits on your device and writes outputs to the destinations you choose. This desktop measurement is separate from the website and browser extension.

Desktop releases incorporating the 25 October 2026 reliability update send bounded usage events to PostHog for app starts, successful document opens, the first successful edit of a document, and successful saves. Earlier installed releases retain their previous measurement until updated. Sentry receives application lifecycle and unexpected error diagnostics. Reports include fixed app, installed-version, platform, build-provenance, action, source and outcome categories, with sanitized technical diagnostics. They exclude file names and paths, document contents, schemas, field or column names, cell values, SQL, credentials and arbitrary error text. Debug builds suppress routine remote telemetry; locally built release packages can report development-tagged activity. A failure to deliver a report does not prevent local editing.

Desktop usage measurement uses a random app-scoped installation identifier kept in local app storage and a fresh session identifier per launch. Unavailable identifier storage uses a session identifier instead. Identifiers are not derived from an account, hardware, operating-system identity or documents, and PostHog person-profile creation is disabled. Sentry and PostHog receive ordinary network information, including IP addresses, when reports are sent; their configured desktop collection endpoints are in the United States. PostHog can retain IP addresses and derive approximate location without requesting precise device location. Random identifiers do not make reports anonymous.

Updated desktop apps also keep bounded local lifecycle and panic-category logs for troubleshooting, without document contents, paths or arbitrary error text. Clearing local app data can remove local diagnostic logs and the routine installation identifier; it does not erase reports already received.

Operational analytics and diagnostics are retained as reasonably needed for reliability, security and legal obligations, subject to provider retention controls; no fixed remote retention period is promised here. There is no in-app routine-analytics switch. You can clear local app data or restrict telemetry connections using your device controls while local editing remains available. The website and extension keep their separate measurement practices described elsewhere in this policy.

Optional browser extension usage statistics

If you enable optional usage statistics in an extension version that offers this setting, the extension sends limited usage events to PostHog in the United States to help us understand use and reliability. Share usage statistics is off by default in extension Options. Local file tools work when it is off. Firefox versions also require the browser’s optional technical and interaction data permission before sending events.

Events count workspace opens, successful file opens, exports and failed file opens. They include fixed product, browser and extension version fields and a random installation identifier created and stored on your device only after you opt in. They exclude file contents, file names, URLs, searches, edits and raw error messages. We do not use session replay, automatic interaction capture, analytics cookies or referrer collection.

PostHog receives ordinary network information, including your IP address, when an event is sent. IP-based location enrichment is disabled for these extension events. A random installation identifier does not make the reports anonymous. Events are retained according to our PostHog project retention settings, subject to earlier deletion under provider controls or an applicable request.

Turning Share usage statistics off stops future events and deletes the local installation identifier. It does not delete events already received. Enabling it again creates a new identifier. This setting applies only to the separately installed extension and does not change website or desktop settings.

Changes

We may revise this policy as the utility changes. The date above identifies the current version. Material behavior changes will be reflected here.

Use of the utility is also subject to the Terms.