Privacy Policy

This Privacy Policy applies to the pages and tools on the DevKitLab website. It covers user input, generated output, browser preferences, files selected by users, and routine technical information produced when the website is accessed.

DevKitLab is a utility website, not an account-based software service. Core tools can usually be used without registration, login, or creating an account.

Many DevKitLab tools are designed to run directly in your browser, including text processing, JSON formatting, JSON conversion, Base64 encoding and decoding, URL encoding and decoding, color tools, image tools, QR code generation, password generation, hash generation, ID generation, and date or time conversion.

When a tool can complete its task locally, your input is processed in the current browser session. The tool itself does not need to upload that input to a server in order to work.

Tool input may include text snippets, JSON, CSV, URLs, images, colors, timestamps, tokens, generated data, or other content you choose to paste, enter, or select. Unless you have reviewed the risk and the use case, you should avoid entering production secrets, private keys, real passwords, regulated personal information, payment data, or customer records.

Generated output is usually displayed on the page so you can copy or download it. Downloaded files are generated or saved locally by your browser after you choose to download them.

Some tools allow you to select files, images, or PDF documents from your device. These tools are intended to process selected files in the browser where possible, such as image compression, image conversion, image metadata viewing, Base64 conversion, EXIF removal, PDF merging, PDF page reordering, and other file utilities.

When a file-based tool is described as local or browser-based, the selected file is processed in your browser session and is not intentionally uploaded to DevKitLab servers for that tool to work. The result may be displayed on the page or downloaded by your browser after you choose to do so.

A selected file remains under your control. You should still be careful when processing sensitive files, because browser-side tools may read, display, transform, or generate copies of the content you provide.

DevKitLab may use localStorage or similar browser storage features to remember interface preferences, such as theme selection, language preference, and sidebar state. These preferences are stored in your browser on your device.

You can clear this data through your browser settings. Clearing site data may reset the related interface settings to their default state.

DevKitLab’s core tool experience does not rely on user accounts. The website may use cookies, local storage, browser storage, log data, basic analytics, error monitoring, and similar technologies to provide the website, remember preferences, understand aggregate usage, detect errors, prevent abuse, and improve page performance.

DevKitLab loads Google AdSense services to prepare for or support advertising that helps maintain the free tools. When Google ads are served, Google and other third-party vendors may use cookies, web beacons, IP addresses, device information, browser information, advertising identifiers, and similar technologies to serve ads, limit ad frequency, prevent fraud and abuse, measure ad performance, and provide personalized or non-personalized advertising according to user settings, consent choices, and applicable law.

Google’s use of advertising cookies can allow Google and its partners to serve ads based on a user’s visits to DevKitLab and other websites. You can use Google Ads Settings to turn off personalized advertising. Some choices may also be available through applicable industry opt-out pages or third-party vendor websites.

DevKitLab uses Google’s Consent Management Platform (CMP) to request and manage consent for advertising cookies and related technologies before serving ads to users in the European Economic Area, the United Kingdom, and Switzerland. Whether ads are personalized depends on a user’s location and choices.

You can manage, block, or clear cookies through your browser settings. Blocking cookies may affect some website features, preferences, analytics, or advertising behavior. You can also read Google’s advertising privacy explanation to understand how Google uses advertising-related data: https://policies.google.com/technologies/ads.

• Google Ads Settings
• How Google uses advertising data

The current network-dependent tools are IP Lookup, DNS Lookup, SSL Checker, and SPF/DMARC Checker. They are different from text, image, and file conversion tools that run fully in the browser.

When you use one of these tools, the domain name or IP address you enter, together with the request details needed to perform the lookup, is sent to the DevKitLab API service at api.devkitlab.com. The service performs the requested lookup and returns the result to your browser. Do not enter personal data that is unrelated to the lookup.

• Do not treat browser-generated example values as production secrets unless your own system also handles secure storage, rotation, authorization, and auditing.
• Do not paste private keys, live access tokens, production passwords, regulated records, or customer data into utility tools unless you have reviewed the risk.
• Browser-side processing can reduce unnecessary uploads, but it does not replace your organization’s security, compliance, or data handling policies.
• Generated code, converted data, and downloaded files should be reviewed manually before they are used in production.

DevKitLab is intended for technical, educational, and everyday utility use. It is not directed at children and does not intentionally collect personal information from children.

This policy may be updated as DevKitLab changes. Important changes will be reflected by updating the date on this page and revising the relevant sections.

If you have a privacy question about DevKitLab, or want to report unclear data handling language in a tool, email support@devkitlab.com.