Contact DevUtilKit

Use support@devutilkit.com or the contact workflow for bug reports and policy-related requests.

1. Introduction

DevUtilKit is a free developer tools platform maintained by a small independent team focused on practical daily workflows for engineers, analysts, and technical operators. If you need help, we want to hear from you. You can contact us for bug reports, feature requests, questions about how a specific tool works, documentation corrections, and privacy or data handling inquiries. We currently provide support through email so requests can be tracked clearly and answered with enough technical detail. Typical response time is 2 to 3 business days, although complex issues may require follow-up questions before we can confirm a resolution path.

2. General Contact

For all general inquiries, email support@devutilkit.com. We aim to respond within 2 to 3 business days. If your request relates to a specific page or tool, include the exact URL and a short summary of what you were trying to do. This helps us route your message quickly and reduces back-and-forth before technical review starts.

3. Reporting a Bug

If a tool is not working correctly, a detailed bug report helps us reproduce and fix the issue quickly. Vague reports such as "it does not work" are difficult to act on because they do not isolate the failure path. The more specific your report is, the faster we can validate, diagnose, and deliver a fix or workaround. Please include concrete reproduction data whenever possible so the team can confirm behavior in a matching environment.

- Tool name (e.g. JWT Decoder, SQL Runner, JSON Formatter)

- The exact input you used (or a representative sample)

- What output you expected and what you actually received

- Your browser name and version, and your operating system

Email subject format: Bug: [Tool Name]. Send to support@devutilkit.com. If sensitive data is involved, please redact personal records, tokens, and credentials before sending your sample.

4. Feature Requests

We welcome suggestions for new tools and improvements to existing ones. The most useful requests describe the real problem you are trying to solve, not just a feature label. For example, saying that you need a reliable way to convert cron expressions into human-readable schedules is more actionable than saying add more tools. Requests with context such as team workflow, expected input/output format, and current pain points help us prioritize roadmap items that create measurable value for developers. Send feature requests to support@devutilkit.com with subject format: Feature Request: [Tool or description].

5. Privacy and Data Inquiries

For questions about what data DevUtilKit collects, requests to access or delete your data under GDPR, or concerns about how information is handled across browser-side tools and server-backed endpoints, contact us directly through the privacy channel. We treat privacy requests as a high-priority support class and aim to respond within 5 business days. To accelerate handling, include the route involved, date of access, and a clear explanation of the request scope so we can provide an accurate and complete response. Subject: Privacy Request. Send to support@devutilkit.com.

6. Security Vulnerabilities

If you discover a security vulnerability in DevUtilKit, please report it responsibly instead of disclosing it publicly before remediation. Responsible disclosure gives us time to investigate, reproduce, mitigate, and deploy a fix without exposing users to avoidable risk. Send your report to security@devutilkit.com with subject Security Vulnerability. We aim to respond within 72 hours with an acknowledgment and next steps.