Technical Support & Direct Engineering Contact
No automated phone trees. No offshore support farms reading scripts. Real developers inspect your bug reports, review stack traces, and verify system integrity.
Direct Contact Routing
Send your message to the specific inbox monitored for your inquiry type.
Technical Support & Bugs
Browser rendering defects, WebAssembly errors, broken calculations, or missing statutory form clauses.
Security & Vulnerabilities
Responsible disclosures, unexpected network call reports, Content Security Policy flags, or audit reviews.
Enterprise & Self-Hosting
Air-gapped internal installations, custom legal templates, school site packaging, or commercial partnerships.
Generate Browser Diagnostic Snapshot
Reporting a broken tool? Click below to test your local WebAssembly engine, memory buffer speed, and screen metrics. We never extract personal identification or document content. Copy and paste the resulting text straight into your support email.
Inquiry Triage & Resolution Framework
Understand how our engineering team handles incoming requests and where to direct time-sensitive issues.
| Inquiry Type | Target Channel | Required Information | Resolution Window |
|---|---|---|---|
| Broken Tool or Crash | support@rapiddoctools.com | Tool URL, file size, console error text, browser diagnostic snapshot | 24 to 48 Hours |
| Security Vulnerability | security@rapiddoctools.com | Proof-of-concept steps, affected URL, raw network traces | Under 24 Hours |
| Self-Hosting / Intranet | business@rapiddoctools.com | Organization scale, isolated intranet setup, target operating systems | 1 to 2 Business Days |
| Statutory Form Request | support@rapiddoctools.com | Specific US State or Canadian Province, official statutory citation | 3 to 5 Business Days |
| Lost or Unsaved Document | Self-Service Only | No recovery possible. Files exist solely in volatile client device RAM | No Server Records |
Four Things to Check Before Submitting a Bug Report
Resolve common client-side processing hiccups immediately without waiting for an email response.
Inspect Browser Console Errors
Press F12 or Cmd+Option+I. Check the Console tab. Red error lines like Out of Memory or CSP Block help us pinpoint code breakages within minutes.
Verify PDF Password Status
Encrypted or password-protected PDF files cannot be manipulated locally without entering the decryption key first. Remove owner locks before reordering or converting pages.
Mobile RAM Limits (iOS Safari)
iOS Safari limits browser tabs to roughly 1 GB of volatile RAM. Processing high-resolution scans or multi-hundred-page PDFs on older iPhones can trigger silent tab reloads. Test the file on a desktop browser.
Disable Strict Script Blockers
Extensions that forbid WebAssembly execution or Canvas image reads will stop in-browser conversion dead in its tracks. Whitelist RapidDocTools to allow local binary execution.
Engineered in Khulna, Serving Global Users
RapidDocTools is developed and maintained by Md Al Mamun Galib, a mechanical engineer and software builder based in Khulna, Bangladesh.
We believe in accountable software. You do not have to wonder who maintains this code or trust vague marketing claims. All document utilities run client-side, allowing anyone with Chrome DevTools to verify our zero-upload architecture independently.
Entity & Physical Address
- Legal Entity
- Rapid Doc Tools
- Physical Location
- Khulna, 9100
Division of Khulna, Bangladesh - Primary Operating Markets
- United States, Canada, United Kingdom & Worldwide
- Primary Support SLA
- 24 to 48 Hours (Monday – Friday, GMT+6)
Frequently Asked Support Questions
Straight answers about document retrieval, error triage, and response protocols.
Explore Documentation & Dedicated Hubs
Access free, client-side tools and architectural documentation across our major suites.