Data Handling and Responsible Use

Data handling varies by tool class. Browser-side utilities stay local where possible, while backend-assisted features apply bounded controls.

1. Two Categories of Tools

DevUtilKit tools fall into two categories based on how they handle user input. Understanding which category a tool belongs to is important when you work with sensitive data, regulated data, or internal operational records. Some tools run entirely in your browser and do not require server-side processing, while others require backend execution to provide database-backed functionality. This page explains those categories, what is and is not retained, and how logging, analytics, and advertising systems are scoped so users can make informed decisions before entering data.

Category A consists of browser-side tools where input never leaves the browser. JSON Formatter, JWT Decoder, Base64 Converter, URL Encoder/Decoder, UUID Generator, Timestamp Converter, Cron Interpreter, Regex Tester, and CSV to JSON all process data in JavaScript running in your active browser tab. When you paste content into these tools, the transformation logic executes locally on your device. No tool input is transmitted to DevUtilKit servers as part of standard usage. You can confirm this by opening browser DevTools, switching to the Network tab, and watching outgoing requests while using any of these tools.

Category B is backend-assisted processing, currently represented by SQL Runner. SQL Runner sends the query text you enter to the DevUtilKit backend, where it is executed against a sandboxed read-only database path. The result set is returned to the browser for immediate display. Query text and result data are not stored after the response is sent, and DevUtilKit does not log query content. SQL execution remains constrained by statement validation, timeout rules, and request limits that are documented in the Security page and enforced in runtime behavior.

2. What DevUtilKit Does Not Store

DevUtilKit does not store SQL queries, JWT tokens, JSON payloads, Base64 strings, URL-encoded strings, regex patterns, CSV data, or other user input entered into tool interfaces. There is no persistent query history, no saved SQL result archive, and no user-associated activity timeline that tracks individual tool payloads over time. Because the platform does not use a user login/account system, there is no identity-linked storage layer for tool inputs. In practice, this means your working content is transient for interactive usage, and when you close the browser tab, locally processed tool data is gone.

3. What Is Logged

DevUtilKit server access logs include technical metadata needed to operate and secure the service: IP address, timestamp, HTTP method, requested URL path such as /api/sql-runner, HTTP status code, and response size. These logs are retained for 30 days and then deleted through normal retention processes. Their purpose is limited to abuse detection, rate limiting support, and diagnosing service errors. Access logs do not include the content of SQL queries, tool input payloads, or tool output data. In other words, operational observability is focused on request-level metadata rather than user-provided content.

4. Analytics Data

Google Analytics collects aggregate usage information such as page views, session duration, pages visited per session, browser type, operating system type, screen resolution, and anonymized IP address. This data helps us understand how users navigate the site and which tools are most useful so we can prioritize improvements. Analytics processing and storage are performed by Google LLC under Google's data processing terms. DevUtilKit does not use analytics as a content storage layer and does not access individualized tool input data through analytics events.

5. Advertising Data

Google AdSense may set cookies in your browser and collect behavioral signals to support ad delivery and ad personalization. This advertising data is collected and processed by Google LLC. DevUtilKit does not receive or store ad targeting profiles or user-level ad preference data. Users who do not want personalized ads can opt out through adssettings.google.com or use browser-side controls such as the Google Analytics Opt-out Add-on, depending on the type of tracking they want to limit.

6. Third-party Processors

DevUtilKit uses two processor categories: Google LLC for Google Analytics and Google AdSense, and the hosting/infrastructure provider that serves the site and runs the SQL Runner backend service. The hosting environment processes server access logs as described above but does not access tool input content as a persistent dataset. DevUtilKit does not sell, rent, or share user data with any other third party outside these stated operational processors.