Cookies

Current cookie status

The current site does not render advertising slots. Google Analytics 4 is deployed but remains optional: the site runtime does not initialize it unless the stored analytics choice is exactly granted. Advertising storage, ad user data and ad personalization remain denied.

A browser-provided Global Privacy Control signal is treated as an automatic analytics refusal. It replaces a previously stored analytics grant with denied; Do Not Track is not automatically interpreted as the same signal.

Ordinary browser requests, TLS negotiation, HTTP headers, server logs, caching, same-origin API calls and the consent choice create or use technically necessary protocol or browser data. They are not marketing cookies and are described in the privacy policy.

Analytics must not receive pasted headers, certificates, EDID data, DNS values, IP addresses, URLs, domains, subnet plans, results or other user-entered tool content.

Local storage

admintoolkit.io uses browser local storage for interface preferences. The theme mode key is admintoolkit-theme-mode.

The theme value is stored on the device and is used only to keep the selected light or dark mode across visits. It is not used for advertising, cross-site tracking, user identification, account matching, or profiling.

Local storage is controlled by the browser. It stays available to pages from the same origin until the user clears it, the browser removes it, private browsing ends, or site data is otherwise reset. Clearing it resets the visual preference but does not affect the ability to use the tools.

Some tools may keep temporary state in the page while it is open, for example parsed input, selected options, or current result panels. That page state is meant for usability during the session and should not be treated as durable storage.

External services

Some tools can make explicit live requests after a user action, for example DNS lookups, TLS certificate retrieval, HTTP header checks, Geo-IP/ASN, or a Google Maps embed after a separate map opt-in. The public IP page requests only its same-origin IP context on page load; Geo-IP/ASN and the map require separate clicks.

Those third-party services may apply their own cookies, local storage, request logging, abuse-prevention checks, rate limits, or similar technologies when their pages, APIs, maps, or embeds are requested. admintoolkit.io does not control the storage behavior of those external providers.

Live requests are not the same as ordinary page rendering. A pasted header, domain, host name, IP address, or URL may stay local in one tool and be sent to an external lookup service in another. The relevant button, label, or result text should be used to judge whether the action is local or live.

If the input is confidential, do not use live lookup features unless the disclosure to the involved provider is acceptable for your case.

Analytics, advertising and consent

After consent, Google Analytics 4 may set analytics cookies such as _ga or related property-specific identifiers, depending on browser settings and Google's implementation. They support measurement and do not store tool input values.

The choice is stored locally as admintoolkit-analytics-consent. To withdraw consent, clear that value or all site data, reload the page and choose “Decline”. Subsequent site-triggered Analytics initialization then remains off; withdrawal does not recall data already sent.

When Global Privacy Control is enabled, the site records denied automatically and does not offer or initialize analytics for that page load.

Google AdSense may be added later, but it is not active in this site version. Any future advertising deployment requires a separate policy and consent review against the behavior actually deployed at that time.

A policy update does not retroactively mean that advertising or analytics cookies were active before it. The tags actually deployed, the consent state and the browser behavior at the relevant time are decisive.

Necessary storage

Some storage or protocol behavior can be necessary for security, routing, caching, abuse prevention, TLS delivery, same-origin API protection, or basic browser operation. This can include server-side logs, cache headers, request metadata, and browser-managed state.

Necessary storage is kept as small as practical. The goal is to run technical tools with predictable behavior, not to build user profiles.

Managing storage

Users can clear cookies, cache, local storage, and site data through their browser settings. Clearing local storage resets the color theme preference and any temporary site state the browser kept for this origin.

Private browsing modes, content blockers, browser privacy settings, DNS filters, and enterprise policies can change how storage and external requests behave. If a tool does not remember the theme or a live lookup does not load, local browser policy is one of the first things to check.

For questions about this policy, use the contact details in the legal notice or privacy policy.