Get in Touch with Our Team

Whether you encountered an unexpected parsing error, have an idea for a developer utility that should be added, or have privacy and security questions, our team is directly available.

How to Submit a Detailed Bug Report

To help us reproduce and resolve parsing or encoding discrepancies quickly, please include:

• The exact tool name and URL (e.g., JSON to XML Converter).
• A sample input payload that caused the failure (ensure no private credentials or secrets are attached).
• The expected output according to the relevant standard (RFC) versus the actual output produced.
• Your browser version and operating system (e.g., Chrome 128 on macOS / Windows 11).

Direct Message Composer

You can use this helper to format an email draft directly:

Responsible Security Vulnerability Disclosure

We prioritize the security of our users and welcome vulnerability reports from ethical security researchers. If you identify a potential security issue (such as a Cross-Site Scripting vector or prototype pollution in our client-side parsing routines):

• Send your findings directly to lcsoftarte@gmail.com with the subject line [Security Vulnerability Disclosure].
• Please provide a minimal proof-of-concept (PoC) and sufficient technical details to enable our engineering team to reproduce and validate the finding.
• We pledge to acknowledge receipt within 24 hours and provide an estimated remediation timeline. We kindly ask for reasonable time to deploy a patch before public disclosure.

Frequently Asked Questions About Support