Get in touch.

We read every message sent to our team. For bug reports, developer collaborations, or security disclosures, reach out through the channels below.

Direct Channels

Response Timeline

[CONFIRM: Expected reply time (e.g. within 2 business days)]
We prioritize responsible security disclosures, severe bug reports, and academic research correspondence.

What to include in a bug report

When reporting unexpected behavior or client-side crashes, please include the following diagnostic details so we can reproduce the defect accurately:

  • Operating system & build: (e.g., Windows 11 Build 22631, macOS Sonoma 14.5, Ubuntu 24.04).
  • Runtime environment: Browser name and exact version (for web tools like Canvas Convert Pro), or Microsoft Store package version.
  • Reproduction steps: Clear step-by-step instructions from application launch to the failure state.
  • Test file details: File format extension, approximate file size, and codec details (please never send confidential or sensitive personal files).
  • Expected vs. actual behavior: What should have happened versus what occurred on your screen.
  • Browser console logs: Any red error trace visible in DevTools (F12) console tab.