Your operational data stays under your control.

Tool data

ObservKit’s calculators, converters and validators run in your browser. Values you enter—such as log volumes, cron expressions and YAML manifests—are not sent to an ObservKit application server for processing.

ObservKit may save safe calculator parameters, UI preferences, pinned tools and recent tool paths in localStorage on this device. YAML, secrets and pasted technical content are never persisted.

Site analytics

ObservKit does not currently use Cloudflare Web Analytics or any other third-party analytics script to measure traffic. Its only first-party measurement is the product telemetry described below. The site is delivered through Cloudflare, which processes ordinary connection data to deliver and protect it and may set technical or security cookies, such as __cf_bm (bot management), under its own terms. ObservKit does not use these services to read the content entered into its tools. If analytics are added in the future, this notice will be updated before they are enabled.

Product telemetry

To understand which features are actually useful, ObservKit can record a small number of product events through its own endpoint, telemetry.observkit.com, stored in Cloudflare Workers Analytics Engine. This is privacy-minimized product analytics without persistent user identifiers.

Each event only contains fixed categories:

• Feature used, for example “report opened”, “scenario saved” or “compare enabled”.
• Tool, for example Splunk, Elasticsearch or Log Storage.
• Where it happened: home page, Capacity Planning hub, tool, report or command palette.
• Source category: direct, search, internal or external, derived from the referring address of the current page load. The address is classified in your browser and then discarded; it is not used to follow visits over time.
• Timestamp, added when the event is stored.

ObservKit does not record calculator inputs or results, scenario names or contents, YAML, cron expressions, timestamps you enter, report or Markdown content, clipboard content, full URLs, query parameters or referrers. Product telemetry does not create cookies and does not use localStorage, sessionStorage, visitor IDs, session IDs or other persistent identifiers. Events are sent without cookies or the page address. The endpoint does not store IP addresses, User-Agent strings or location. Like any web request, delivering the event still passes through Cloudflare’s network, which processes ordinary connection data under its own terms.

If your browser sends a Global Privacy Control or Do Not Track signal, ObservKit does not send product telemetry at all. This is a voluntary ObservKit behavior, not a statement about any specific law.

Workers Analytics Engine retains these events for three months. They are only used in aggregate, as event counts such as how often reports are opened per tool.

Search visibility

The site is configured with standard search metadata and Google Search Console so public pages can be discovered and monitored in search results.

Advertising

ObservKit includes Google AdSense advertising code. Whether ads are actually shown can depend on Google’s approval of the site, your region, your consent choices and other factors, and in some regions Google may show a consent message before ads or advertising cookies are used.

Where advertising is served, Google may process browser and device information and may use cookies or similar technologies where permitted and, where required, with consent, under Google’s own policies. Advertising is separate from ObservKit’s product telemetry and from the data you enter: ObservKit does not send calculator inputs, Saved Scenarios or report contents to Google for advertising, or to its product telemetry.

Accounts

ObservKit has no user accounts, login system or newsletter tracking. If these practices change, this notice will be updated before the change applies.

Third-party infrastructure

The website is delivered through OpenAI Sites and Cloudflare. Their services may process ordinary connection data such as IP address, browser information and request timing to deliver and protect the site.

Questions

For privacy questions, use the project’s public contact channel when one is listed. Do not include secrets, credentials or sensitive production data in a support message.