Contact Us
Got a technical issue? Want to suggest a feature or need a brand-new tool? Send us an email at contact@rtcd.io, or fill out the form below. We'd love to hear from you, and we typically respond within 24 to 48 hours.
How Can We Help?
Bug Reports & Technical Support
Noticed a tool misbehaving or facing an issue while running a process locally in your browser? Let us know the exact symptoms so we can debug and patch it up quickly.
Feature Requests & Optimizations
Have an idea for a new web utility or a performance improvement? We are constantly expanding our toolkit and love executing on highly requested features from our users.
General Feedback & Inquiries
Tell us what you love or where we can improve. We are also open to business collaborations, advertising opportunities, and partnership inquiries that align with our platform.
Privacy & Architecture Questions
Curious about how our zero-upload architecture keeps your data 100% local? If you have questions regarding data sovereignty or our privacy implementation, drop us a line.
Review This Before Reaching Out
Check Our Self-Service Resources First
To get an immediate answer, we highly recommend reviewing our documentation before sending a message:
- Dedicated Tool FAQs: Scroll to the bottom of any specific tool page to find answers tailored directly to that utility.
- Privacy Policy: Read our comprehensive privacy documentation to understand exactly how we ensure your files never leave your machine.
- Terms of Service: Review our terms to learn more about the guidelines and conditions for using our platforms.
Keep Your Messages Secure
Since our tools operate entirely in your browser without uploading your files, we have no backend access to your data. When describing your issue, please DO NOT include any personal, confidential, or sensitive financial information in the form or email.
Help Us Diagnose the Issue
If you still need to reach out, please ensure your message includes the specific tool name, a clear description of the problem, and any error messages. Because local-first applications rely heavily on your client-side hardware, knowing your exact browser and operating system is highly critical for our team to reproduce and fix the bug.