Your data never leaves your device.

The text, files, and configuration you paste into any OpsCanopy tool are processed locally, inside your own browser tab. They are never sent to us or to any third party, and they are never stored after you close the tab.

We do not run user accounts, we do not require sign-up, and we have no database of your activity.

Each tool is a small program that runs as client-side JavaScript (or WebAssembly). When you paste a log line, an alert rule, a CIDR list, or any other input, the computation happens on your machine. The results you see are produced locally and disappear from memory when you navigate away.

Because the work is local, the tools also keep working offline once the page has loaded.

We do not collect the contents of your inputs or outputs. We do not use advertising cookies, cross-site trackers, or fingerprinting. We do not sell, rent, or share personal data, because we do not gather it in the first place. Our only measurement is the cookieless-by-default analytics described below.

Any preference the site remembers — such as your light/dark theme or language — is stored in your browser’s local storage on your device and is never transmitted to us.

Everything OpsCanopy remembers is kept in your browser’s local storage on your device, under a handful of named keys you can inspect and delete at any time. None of it is transmitted to us. Today those keys are:

theme — your light or dark theme choice.

oc-analytics-consent — your analytics opt-in choice from the toggle on this page.

oc-m90-v1 — your Mission 90 Days DevOps progress: which days and missions you have marked done in this browser.

oc-m90-backup-meta — when you last backed up that progress (and whether you dismissed the backup reminder), so the Mission 90 hub knows when a reminder is worth showing.

opscanopy:tools:sort — how you last sorted the tools catalog.

oc-roadmap-… (one key per learning roadmap) — which topics you have checked off on that roadmap.

oc-guide-…-pos (one key per guide) — your last reading position in that guide.

oc-tools-v1 — tools you have pinned, and the last few you have used, so the "Jump back in" and "Your tools" shelves can show them.

oc-last-v1 — the last input you typed into a tool, restored automatically the next time you open that same tool. Never used on the four tools whose input may be a secret — JWT Decoder, Hash Generator, Base64 Encoder/Decoder, and the Env Example Checker.

oc-snap-v1 — snapshots you explicitly chose to keep with a "Save snapshot" button, so you can return to that exact input later. Available on every tool, including the four above, since saving one is your own deliberate action.

oc-handoff-v1 — a one-time handoff when you follow a "Decode as JWT" or similar link between two tools. It lives in this tab only (sessionStorage, not localStorage) and is deleted the instant the destination tool reads it — never carried in the page URL, so it never ends up in your browsing history.

Clearing your browser’s site data removes all of these. Mission 90 progress can survive a clear via the backup file or code from the Mission 90 hub.

OpsCanopy is served as static files from a hosting provider and content-delivery network. Like virtually all web hosts, those providers may keep short-lived, standard request logs (for example an IP address and browser user-agent) to deliver pages, mitigate abuse, and keep the service secure. These logs are operational and are not used to profile you.

We use Google Analytics 4 to understand which tools and guides are actually useful: page views plus a handful of anonymous product events (for example “a result was copied on this page” or “a Mission 90 day was marked complete”). These events carry only the page path — they never include anything you type or paste into a tool.

By default, analytics runs in cookieless “consent denied” mode: no analytics cookie is set and no persistent identifier is stored on your device unless you explicitly opt in with the toggle below. You can change your choice at any time on this page, and the site works identically either way.

Beyond the analytics script described above, we keep external dependencies to a minimum — fonts are self-hosted and pages load no other third-party code. We do not embed advertising networks or social tracking pixels.

If this policy changes, we will update the date shown at the top of this page. Continued use of the tools after an update means you accept the revised policy.

Privacy questions are welcome. The best way to reach us is through our public GitHub organization — see the Contact page for the link.