Codepackr

Contact & Feedback

Questions, bug reports, tool ideas, and feedback about CodePackr are welcome. The primary contact email is codepackr@gmail.com. You can also use the contact form on this site.

A secondary email address, tnavkum@gmail.com, is listed for the same purposes. The project is operated from Chennai, Tamil Nadu, India by Naveen Kumar T.

How to Reach Us

Email codepackr@gmail.com for bug reports, requests for new tools, questions about privacy or data handling, and legal notices. The secondary address tnavkum@gmail.com can be used as well. Both addresses are monitored as part of the independent project.

An on-site form is available if you prefer not to open your email client. Messages sent either way are read. There is no guaranteed response time; responses depend on the nature of the message and available time.

What to Include in a Report

For the most useful bug report or question, include the full URL of the tool you were using, the browser name and version, a short description of the steps you took, what you expected to happen, and what actually happened.

If a sample input helps explain the issue, include a non-sensitive example of what you pasted or selected locally. Never send passwords, API keys, private certificates, personal health data, or other confidential material. Tool inputs stay in your browser; there is no need to transmit them unless they are required to describe a non-sensitive failure.

Privacy and Legal

Questions about how tools process data, cookies, or advertising can be sent to the same addresses. Legal notices should also go to codepackr@gmail.com. Because tools run client-side, most privacy questions can be answered by noting that inputs are not uploaded.

The operating location is Chennai, Tamil Nadu, India. Source code for the site is publicly available at https://github.com/coolnaveen99/codepackr.

Other Notes

If you are writing about a tool that involves EDI standards or image metadata, mention the specific standard or format so the context is clear. Screenshots of the browser console can be helpful when a script error appears, provided they do not contain sensitive values.

Messages are read as part of maintaining the independent project. Suggestions for new categories or improvements to existing tools are especially useful when they describe a concrete workflow that is currently awkward.

Email