Privacy Policy

1. Overview and Scope

This Privacy Policy governs how DevToolsHub ("we", "our", "the site"), operated by Pankaj Kumar, collects, uses, and discloses information when you visit www.devtoolshub.info. It applies to all visitors regardless of location, including residents of the European Economic Area (EEA), the United Kingdom, and the State of California.

We are committed to full transparency. This policy is structured so you can jump directly to the section relevant to your jurisdiction or concern using the Quick Summary sidebar on this page.

---

2. Data Controller

The data controller for DevToolsHub is:

• Name: Pankaj Kumar
• Entity type: Individual operator / sole proprietorship
• Location: Bangalore, Karnataka, India
• Contact: [email protected]

For EEA and UK residents: we do not have a formal EU/UK representative under Article 27 GDPR at this time as the site does not systematically target EEA/UK data subjects and processes only anonymous usage data. Any privacy enquiries may be directed to the email above and will receive a response within 30 days.

---

3. What DevToolsHub Does Not Collect

DevToolsHub itself does not collect accounts, credentials, or tool inputs. Specifically:

• No user registration or account creation is required or offered.
• No text you paste into any tool is logged, stored, or retained in any database by us.
• No personal identifiers (name, email, IP address, device fingerprint) are stored by DevToolsHub's own infrastructure.
• No profiling or automated decision-making using your data is performed by DevToolsHub.
• Third-party services we embed (analytics, advertising, session recording) may collect data independently — each is disclosed fully below with opt-out mechanisms.

---

4. How Tool Processing Works

Tools on this site fall into three categories, based on where the actual computation happens:

• Client-side (browser-only) — these execute entirely within your browser using JavaScript and browser-native APIs (Canvas, Web Crypto, or a WebAssembly OCR engine loaded from a CDN). Your input never leaves your device. Tools: Color Picker from Image, Image to Text (OCR), UUID Generator.
• Blazor Server circuit (server-side, no API call) — these tools run in-memory on the same live connection that renders the page. Your input is transmitted to our server over that connection to be processed, held in memory only for the duration of your active session, and discarded when the session ends. It is never written to disk, a database, or a log file, and no third-party service receives it. Tools: JSON Formatter, JSON to C# Class/Record Generator, XML to C# Class Generator, Text Case Converter, Word & Character Counter, Number Base Converter, CSS Gradient Generator, CSS Formatter, XML Formatter, JSON to TypeScript, .gitignore Generator, IP/CIDR Subnet Calculator, Fake Data Generator, Timezone Converter, Date Difference Calculator, appsettings.json Environment Diff, Image to Base64, Base64 to Image, Connection String Builder & Validator, SQL Table to C# Entity Generator, LINQ to SQL Converter, Csproj Analyzer & Cleaner, EF Core Migration SQL Explainer, C# to JSON Sample Generator, ASP.NET Core Route Tester, NuGet Package Version Conflict Explainer, Dockerfile Generator for .NET, Minimal API Endpoint Scaffolder, PNG to SVG Converter, SVG to PNG Converter. For PNG to SVG and SVG to PNG specifically: pasting markup or a data URL directly keeps the conversion entirely client-side, but using the file upload button streams that file's bytes to our server over this same connection (standard Blazor Server file upload behavior) before the result is generated — the same in-memory-only, session-scoped handling described above applies to that upload either way.
• API-assisted — these send your input over HTTPS to the DevToolsHub API (hosted on Microsoft Azure) to perform the operation server-side, then return the result. The API does not log request payloads. Minimal operational logs (HTTP method, status code, response time) are retained for up to 24 hours for infrastructure monitoring and then automatically deleted. No user identifiers are linked to these logs. Tools: Regex Tester, JWT Decoder, JWT Generator, JWT Secret Generator, Password Generator, Text Compare, Markdown Preview, SQL Formatter, YAML Formatter, HTML Formatter, Base64 Encoder / Decoder, Timestamp Converter, JSON Diff Tool, CSV ↔ JSON Converter, HTML Minifier, CSS Minifier, Cron Expression Generator, Color Picker + Converter, URL Encoder/Decoder, HTML Entity Encoder/Decoder, String Escape/Unescape, Hash Generator, Lorem Ipsum Generator, QR Code Generator, Barcode Generator, URL Parser, Unix Permissions Calculator, JSON ↔ YAML Converter, C# ↔ VB.NET Converter.

---

5. Cryptographic Keys, Tokens, and Sensitive Strings

Several tools are designed to handle security-sensitive input: JWT tokens, cryptographic hashes, Base64-encoded credentials, password strings, and API key values. What happens to that input depends on which processing category (Section 4) the tool falls into:

• Image to Base64 / Base64 to Image (Blazor Server circuit): processed in-memory on the server during your active session only. Not sent to any third-party API, and never written to disk or a log file.
• Connection String Builder & Validator (Blazor Server circuit): database server names, usernames, and passwords you enter or paste are processed in-memory on the server during your active session only, and discarded when the session ends. Not sent to any third-party API, and never written to disk or a log file.
• JWT Decoder, JWT Generator, JWT Secret Generator, Base64 Encoder / Decoder, Password Generator, String Escape/Unescape, and Hash Generator (API-assisted): your input is sent over HTTPS to the DevToolsHub API to perform the operation, then discarded. The raw input text is not written to any log — only the operation type and a success/failure status are recorded for monitoring, retained for 24 hours.
• No analytics payloads: Google Analytics 4 event data includes page URLs, click positions, and session metadata only. Tool input values, JWT payloads, hash pre-images, and password strings are never passed to GA4 event parameters or to Microsoft Clarity's session recording.
• Practical recommendation: Avoid pasting live production tokens, private keys, or credentials from real systems into any online tool — including this one. This applies with extra weight to the API-assisted tools above, since your input does cross the network to our API (over HTTPS, never logged) rather than staying purely in-session. Use development or test credentials where possible.

---

6. Cookies and Local Storage

The table below lists every cookie and local storage entry set by DevToolsHub and our third-party partners.

6a. First-Party (DevToolsHub)

6b. Google Analytics 4

6c. Microsoft Clarity

6d. Google AdSense / DoubleClick

6e. Cookie Consent (EU/EEA Visitors)

If you are visiting from the European Economic Area, the United Kingdom, or any jurisdiction with cookie consent requirements, the following applies:

• Strictly necessary cookies — the ASP.NET antiforgery token (.AspNetCore.Antiforgery.*) and theme preference cookie (dth_theme) are exempt from consent requirements because they are essential for the site to function correctly.
• Basic analytics cookies (GA4: _ga, _ga_*, _gid) are set by default under our legitimate interest (Article 6(1)(f) GDPR) in understanding anonymized visitor counts and page popularity. GA4 is configured with IP anonymization and no ad-personalization signals. You may object to this processing at any time using the opt-out links below, or turn it off in the cookie preferences panel.
• Enhanced analytics cookies (Clarity: _clck, _clsk) — session recording and heatmaps — require your consent and stay off until you explicitly enable them in the cookie preferences panel.
• Advertising cookies (AdSense / DoubleClick: IDE, test_cookie) are used to serve personalised advertisements and require your consent under GDPR. Google manages consent via the IAB Transparency and Consent Framework (TCF) and may display a consent dialogue on your first visit if you are in a TCF-applicable region. You can withdraw consent at any time at Google Ads Settings.

Opt out of analytics or advertising cookies:

• GA4: Install the Google Analytics Opt-out Browser Add-on
• AdSense personalised ads: Google Ads Settings or AboutAds.info
• All NAI member networks: optout.networkadvertising.org

Clear all cookies and localStorage via your browser:

• Chrome: Settings → Privacy and security → Clear browsing data → Cookies and other site data
• Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data
• Safari: Settings → Privacy → Manage Website Data → Remove All
• Edge: Settings → Privacy, search, and services → Clear browsing data → Cookies and other site data

---

7. Analytics — Google Analytics 4

What it collects: Page URLs visited, session duration, events (button clicks, tool usage), browser type, operating system, approximate geographic region (country/city — not precise location), and referring URL. Input values you type into tools are never included in any GA4 event.

Why we use it: To understand which tools are most useful, where users experience friction, and to make informed decisions about which new tools to build.

Lawful basis (GDPR): Legitimate Interest (Article 6(1)(f)) — we have a legitimate interest in understanding how the site is used in order to improve it. GA4 data is anonymised and aggregated; no personal decisions are made based on it. You can object at any time using the opt-out link above.

Data processor: Google LLC — governed by the Google Privacy Policy. Data may be transferred to Google servers in the United States under Standard Contractual Clauses.

---

8. Session Recording — Microsoft Clarity

What it collects: Mouse movements, click positions, scroll depth, and page interactions in anonymised heatmap and session replay form. Clarity is configured to mask all text input fields — it does not capture keystrokes, passwords, or tool input content.

Why we use it: To identify usability problems — for example, discovering that users are clicking a non-interactive element or abandoning a tool after a particular step.

Lawful basis (GDPR): Consent (Article 6(1)(a)) — Clarity stays off by default and only loads once you explicitly enable "Enhanced analytics" in the cookie preferences panel. You can withdraw consent at any time from the same panel, or via your browser's Do Not Track signal or a privacy extension.

Data processor: Microsoft Corporation — governed by the Microsoft Privacy Statement.

---

9. Advertising — Google AdSense

What it does: Google AdSense serves display advertisements on this site. By default, Google serves personalised advertisements using cookies and browsing history (interest-based advertising). If you opt out, Google will serve non-personalised advertisements instead — ads are still shown but not based on your personal interests or browsing history.

Lawful basis (GDPR): Consent — personalised advertising requires your consent under GDPR. Google manages consent through the IAB Transparency and Consent Framework (TCF). If you are in the EEA/UK, Google's consent banner may appear on your first visit. You can change your consent at any time at Google Ads Settings.

Data processor: Google LLC, publisher ID ca-pub-1618916037375814. Governed by the Google Privacy Policy. To opt out of personalised advertising globally, visit aboutads.info or optout.networkadvertising.org.

---

10. Data Retention Schedule

---

11. GDPR Rights for EEA and UK Residents

If you are a resident of the European Economic Area or the United Kingdom, the General Data Protection Regulation (GDPR) grants you the following rights. To exercise any of these rights, email [email protected]. We will respond within 30 days.

---

12. CCPA Rights for California Residents

If you are a California resident, the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), grants you the following rights:

• Right to Know (§1798.100): You may request disclosure of what personal information we collect, use, disclose, and sell. As stated above, DevToolsHub itself does not collect or store personal information. Third-party services (Google, Microsoft) may collect data as described in their own privacy policies.
• Right to Delete (§1798.105): You may request deletion of personal information we have collected. We hold none. For third-party data, use the opt-out links provided in each service's section above.
• Right to Opt Out of Sale or Sharing (§1798.120): DevToolsHub does not sell personal information. Displaying interest-based advertising via Google AdSense may constitute "sharing" under CPRA. You can opt out at Google Ads Settings.
• Right to Non-Discrimination (§1798.125): We will not discriminate against you for exercising any CCPA right. All tools remain free and fully functional regardless of your privacy choices.
• Right to Correct Inaccurate Information (§1798.106): Not applicable — we do not maintain a profile of your personal information.

To submit a CCPA request, email [email protected] with the subject line "CCPA Privacy Request". We will respond within 45 days as required by law.

---

13. Children's Privacy

DevToolsHub is a developer utility site intended for adults and professional use. We do not knowingly collect any personal information from children under the age of 13 (COPPA), or under the age of 16 where required by applicable law (GDPR Article 8, UK GDPR). If you believe a child has submitted personal information through this site, please contact us immediately and we will take steps to identify and delete it.

---

14. International Data Transfers

DevToolsHub's infrastructure is hosted on Microsoft Azure (region: Central India / Southeast Asia). Third-party services (Google Analytics, Microsoft Clarity, Google AdSense) may process data on servers located in the United States and other jurisdictions. Google and Microsoft participate in the EU-U.S. Data Privacy Framework and use Standard Contractual Clauses (SCCs) approved by the European Commission for international transfers from the EEA/UK.

---

15. Changes to This Policy

We may update this policy when we add new tools, change infrastructure providers, or in response to changes in applicable law. Material changes will be reflected on this page with an updated "Last updated" date. We recommend checking this page periodically if you have privacy concerns. Continued use of the site after a policy update constitutes acceptance of the revised policy.

---

16. Contact and Complaints

For any privacy-related question, request, or complaint, contact us:

• Email: [email protected]
• Response time: Within 30 days for GDPR requests; within 45 days for CCPA requests
• EEA/UK supervisory authority: You may also contact your national data protection authority directly

Related policies