Thirteen local tools
Subnets, email headers, chmod, passwords, JSON/YAML, Base64, URLs, JWT, SHA checksums, regex, diff, cron and epoch time run in browser memory. These tools do not upload inputs, files or results to the diagnostics API. Static HTML, JavaScript, CSS and icons are still fetched from the workspace host.
Three live diagnostics
DNS Explorer, Email DNS Policy and HTTP Inspector send your submitted target to the configured diagnostics API only after you submit. The API then contacts a resolver or inspected public server. Those services can observe queries, connection metadata and targets. HTTP URLs can contain sensitive query values: remove credentials and tokens before submitting.
The browser omits credentials, does not automatically retry requests, and accepts only bounded, validated reports. Cancellation stops waiting in the browser; it cannot undo a request already received by the API or target.
What is stored
Only your light/dark theme preference is saved by our first-party frontend, under domos-theme in local storage. The public site and workspace are separate origins, so their preferences may differ. We do not save tool inputs, results, secrets, or automatic history to local storage, session storage, cookies, IndexedDB, or URLs.
Explicit copy and download actions place data on your clipboard or in your downloads. Browser extensions, clipboard managers, operating-system services and synced folders are outside the tool's control. We do not promise they will erase that data.
Contact form: Microsoft-hosted, not local
The Contact Us page embeds a form hosted at forms.cloud.microsoft. When the form loads, your browser connects to Microsoft and exposes network metadata such as your IP address. Answers you submit are stored in Microsoft Forms for the form owner to review; they are not processed by our diagnostics API or covered by the browser-local tool promise.
Microsoft Forms may use its own cookies or storage and is governed by the Microsoft Privacy Statement (new tab) and the form owner's sharing and retention settings. Clearing a tool workspace does not delete form responses. Please do not send passwords, access tokens, confidential inputs, or other sensitive information. The embed is present only on Contact Us, never in a tool workspace.
Clear means clear this workspace
Clear / reset removes in-memory inputs and results from the current interface and cancels active client work. Restored pages are reset where browser lifecycle events permit it. This is not forensic erasure, secure memory wiping, clipboard clearing or deletion of previously downloaded files. Browser-managed restore behavior can vary.
No third-party workspace code
Workspaces load no advertising, analytics, external fonts or third-party scripts. Navigation is a full document navigation, not a client-side router that carries scripts from the public site into a tool. Local pages have production connection policies that prohibit API connections; live pages allow only the configured API origin.
Advertising is off
We have not added advertising or analytics to our first-party public pages. The embedded contact form is a Microsoft-hosted service with its own policies, as described above. A future sponsorship layout can reserve labeled space without loading an advertiser. Real advertising needs a separately reviewed publisher integration, approved publisher ID, and consent approach appropriate to the audience and jurisdictions. A simple consent cookie would not establish universal compliance.
Hosting and operational metadata
Serving static pages and performing live diagnostics necessarily exposes network metadata such as IP addresses to the participating hosts. Frontends do not instrument or log tool inputs. Hosting-provider and API operational retention must be reviewed separately; this page does not claim that all infrastructure logs are absent.