Skip to main content
kitlocal.dev

Privacy Policy

This policy explains what happens to your data when you use KitLocal. Most utilities run in your browser. Some features use our servers or external services; the details below explain the difference and the choices available to you.

contact@kitlocal.dev

Local processing by default

Most text, conversion and generation tools work in your browser. Some editors save drafts on this device.

Clear server exceptions

Network checks, URL imports, SSL utilities and AI features can send submitted data to a server.

Your data, your choices

Clear saved site data, manage advertising preferences, or contact us about your privacy rights.

1. Who we are and what this policy covers

KitLocal is a collection of developer utilities operated by the KitLocal maintainers. This policy covers this website and its tool endpoints. For privacy enquiries, contact contact@kitlocal.dev. See also our Terms of Service.

You can use the tools without creating an account. External websites, advertising partners and service providers have their own policies for data they receive.

2. Inputs, files and local processing

For browser-based tools, processing happens on your device: for example, formatting pasted JSON, converting text, generating identifiers and many cryptography utilities. Those local operations do not submit their input or output to KitLocal servers.

Choosing a local file reads it into the tool in your browser unless you use a connected feature described below. Clipboard buttons read or write data when you use them, subject to browser permissions. Downloaded results are saved by your browser.

Some editors automatically save drafts locally. Closing a tab does not necessarily remove an input. Use the editor’s clear action where available, or clear all site data in your browser, especially on a shared device.

3. Features that send data to a server

Local processing does not apply to every tool or action. Running the following features sends the relevant inputs to our servers and, where needed, another service. Importing a URL is a server request even inside an otherwise local formatter.

Do not submit production secrets, confidential documents, private URLs or personal data that you are not authorised to share. Private keys submitted to SSL matching and API keys submitted to the key tester leave your device. Use test credentials where possible.

Data sent when you use a connected feature. Ordinary page delivery and performance measurement are described separately below.
FeatureData sentWho receives it
Import from URLThe URL you submit, including its path and query parameters, and the document returned by that URL.KitLocal servers fetch the document from the target website. Available in JSON, XML, SQL, GraphQL and web formatters and the universal converter.
DNS and domain checksDomain name, IP address, record type and lookup options.KitLocal servers and DNS resolvers. Propagation and DNSSEC checks can contact Cloudflare, Google Public DNS and Quad9; domain availability also uses registration services.
WHOIS / RDAP, including bulk lookupThe domain names, IP addresses or autonomous system numbers you submit.KitLocal servers and the relevant domain or Internet number registries through RDAP or WHOIS. Results may contain publicly available registration information.
SSL / TLS checks and decodingHost and port for remote checks; certificate, certificate signing request (CSR), and any private key entered for key matching.KitLocal servers. Remote checks also connect to the target host. Certificate / CSR decoding and key matching run on our server, rather than entirely in your browser.
Website analysis and MAC lookupThe URL or host being analysed, or the submitted MAC address.KitLocal servers; website analysis also contacts the target website. MAC lookup uses a server-side vendor dataset.
AI token calculatorYour text or messages, selected provider and model, and token estimate settings.KitLocal servers for every count. OpenAI counts use a tokenizer on our server. Anthropic and Google counts send the text to the selected provider when that integration is configured.
OpenAI API key testerThe API key you explicitly submit.KitLocal servers, then OpenAI to check access to its model list. The tester does not save the key in browser storage or an application database.
Email authentication and MTA-STS checksDomain name and optional DKIM selector you submit.KitLocal servers and public DNS resolvers (plus https://mta-sts.<domain>/.well-known/mta-sts.txt for MTA-STS policy inspection).
HTTP redirect and header checkersTarget URL and HTTP method (HEAD or GET).KitLocal servers and target hosts along the redirect chain. Sensitive response headers such as Set-Cookie and Authorization are stripped before returning results.
My IP and request header inspectorYour HTTP request IP address, proxy geo headers, and non-sensitive request headers.Read statelessly in memory by KitLocal servers solely to display back to you with Cache-Control: no-store. Sensitive headers (Cookie, Authorization, API keys) are omitted and nothing is logged or persisted.

4. What stays in your browser

We use local storage for your theme, sidebar state, bookmarks, recently opened tools, search history, feedback selections and drafts in supported editors. These values are not synchronised to a KitLocal account. Language is selected through the page URL; the site does not set a language preference cookie.

Clear site data through your browser’s privacy or site settings to remove these values. This resets saved preferences and drafts. Older installations may retain storage entries under the former OmniKit name; clearing all site data removes both old and current entries. Blocking local storage can prevent these convenience features from working.

5. Technical information and server logs

Loading pages or calling a server tool exposes ordinary connection information to our hosting infrastructure, such as IP address, requested URL, time, browser headers and response status. Our server uses IP-based, in-memory request counters to limit abuse.

Some website analysis and failed URL-fetch requests write operational logs containing the submitted URL, a request identifier, timings or error details. URLs and query parameters may therefore appear in logs. Avoid putting credentials or other sensitive content in a URL. Local-only processing is separate from these server requests.

6. Performance measurement

KitLocal integrates Vercel Speed Insights to understand loading speed and responsiveness when enabled by the hosting service. Metrics include page route and URL, Web Vitals and element attribution, network speed, browser, device type, operating system, country and event time.

Vercel describes these measurements as anonymous and not intended to identify visitors or reconstruct browsing sessions. This is performance monitoring, not a recording of editor contents. See Speed Insights privacy documentation and Vercel’s Privacy Notice.

7. Sponsorships and third-party scripts

KitLocal does not load third-party ad-network scripts, real-time bidding trackers or advertising cookies. When sponsorships are enabled, selected non-sensitive pages display at most one static sponsor card rendered directly by KitLocal.

Clicking a sponsor link opens the sponsor’s website in a new tab with standard rel="sponsored noopener" attributes; from that point, the destination site’s own privacy policy applies. Sponsorship cards are never rendered on legal pages or tools marked sensitive.

Sponsorship cards are currently disabled on this deployment.

8. Storage and privacy controls

Because KitLocal sets no advertising or analytics cookies, no cookie consent banner is required to use the tools. Theme, bookmarks, recent tools and editor drafts live only in your browser’s localStorage.

You can clear local preferences and drafts at any time using a tool’s Clear button or your browser’s site-data settings. For questions about privacy controls on this site, contact contact@kitlocal.dev.

9. Why data is used and when it is shared

We use submitted data to run the feature you request, technical records to deliver and protect the service, performance metrics to improve usability, and correspondence to answer enquiries. Advertising, if enabled, supports the service.

Recipients can include our hosting provider, the services and target sites listed above, and providers handling correspondence. We may disclose relevant information when required by law or necessary to address abuse and protect rights. KitLocal does not operate a tool-input data brokerage or sell your pasted documents. Advertising partners’ use of identifiers may qualify as a sale or sharing under some privacy laws; the advertising choices above remain relevant.

Where applicable law requires a legal basis, processing may rely on providing the service you request, legitimate interests in security and service improvement, legal obligations, or consent for optional processing where required. The basis and rights depend on the purpose and your location.

10. How long information is kept

Local preferences and drafts remain until you remove them or your browser clears storage. Ordinary tool request handlers process inputs for the requested operation; the application does not create an account-based archive of submitted inputs or API keys. This does not mean all requests leave no trace: logs, caches and external providers are separate.

WHOIS / RDAP results can be reused from an in-memory cache for five minutes. Successful and not-found WHOIS responses allow a shared cache freshness period of 15 minutes and stale revalidation for a further hour. DNS propagation responses can be cached for 60 seconds. Cache lifetimes control reuse and are not a promise of immediate physical deletion.

Hosting logs, performance records, provider records and correspondence have separate retention arrangements. Their duration depends on provider settings, the need to diagnose problems or resolve an enquiry, and applicable legal obligations. We do not promise a single deletion deadline for those records. Contact us for information about a particular request.

11. International processing

Hosting and external services may process information outside your country. Their locations, safeguards and retention practices depend on the provider and the service used. Provider policies explain their handling of transfers; contact us if you need details about a particular KitLocal request.

For AI services, see the privacy policies of OpenAI, Anthropic and Google. Submitting text for token counting does not by itself establish how a provider retains or otherwise uses it; the provider’s applicable API terms and policies govern that processing.

12. Security and sensitive information

We use technical measures such as input validation, restrictions on outbound requests and request limits to protect the service. No website or storage method can guarantee absolute security. Browser extensions, other users of a shared device and third-party scripts can affect the privacy of data on a page.

Use local or offline tools for material that must not leave your device. If you believe you exposed a credential, revoke or rotate it with its issuer. Report security or privacy concerns privately to contact@kitlocal.dev; do not post keys or personal data in public issue trackers.

13. Your privacy rights

Depending on your location and the processing involved, you may have rights to access, correct, delete or obtain a copy of personal data, restrict or object to processing, withdraw consent, or opt out of certain advertising-related sharing. You may also complain to your local data protection authority.

Email contact@kitlocal.dev with your request and enough context to locate the relevant interaction, such as the tool and approximate time. Do not send passwords or API keys. We may need proportionate verification and will respond within applicable legal time limits. Some rights have exceptions. We cannot retrieve or erase data stored only in your browser; clear that data on your device.

14. Children’s privacy

KitLocal is intended for a general developer audience and is not directed at children under 13, or a higher minimum age where local law requires it. We do not knowingly seek personal information from children. A parent or guardian who believes a child submitted personal information can contact contact@kitlocal.dev.

15. Changes to this policy

We may revise this policy as features, providers or legal requirements change. The date at the top identifies the latest revision. Material changes will be described on this page, and any additional notice or consent required by applicable law will be handled separately.

16. Contact us

For questions about this policy, privacy requests or reports of a data exposure, write to contact@kitlocal.dev. Describe the issue without including confidential tool inputs, private keys or other secrets. Please use this private channel rather than a public feedback issue.