Contact LocalDoc Support
Have questions regarding client-side privacy, suggestions for new tools, or technical feedback? Reach Amaad Mazari directly — founder, engineer, and solo developer of LocalDoc.
Tool usage, bug reports & feedback.
support@localdoc.orgVulnerability audits & zero-upload verification.
security@localdoc.orgAverage response turnaround.
< 24 Business HoursFrequently Asked Inquiries
Are my files really processed 100% on my device without uploads?
Yes, absolutely. LocalDoc leverages modern WebAssembly (Wasm) and HTML5 Canvas technology to execute all parsing, compression, rotation, and photo generation routines strictly within your browser tab's sandbox memory. You can verify this independently by opening your browser's Developer Tools (F12) → Network tab and observing that 0 bytes of document payload are transmitted.
Can I use LocalDoc for enterprise, legal, or commercial document processing?
Yes. Law firms, healthcare clinics, accounting practices, and surveyors frequently use LocalDoc because our zero-upload architecture satisfies stringent GDPR, privacy regulation, and client-confidentiality compliance standards without requiring third-party data processing agreements (DPAs).
What is the maximum file size supported by LocalDoc tools?
Because processing runs in your computer's RAM rather than on a shared server, there are no artificial file size caps imposed by bandwidth costs. You can process PDFs and image batches as large as your device's available memory allows (typically several hundred megabytes smoothly on modern laptops and smartphones).
How can I request a new client-side document tool or report an edge-case bug?
Submit your request using the form above or email us at support@localdoc.org. For open-source contributions, feature suggestions, or vulnerability disclosures, you can also engage directly on our GitHub repository.
How to Write an Effective Bug Report
A clear bug report helps us fix issues faster. When reporting a problem with any LocalDoc tool, please include the following information:
- Which tool is affected — e.g. Compress PDF, CNIC Photo Maker, Document Scanner.
- Your browser and version — e.g. Chrome 126 on Windows 11, or Safari 17 on iPhone 15.
- File type and approximate size — e.g. a 4MB DOCX file. Do not attach actual documents.
- What you expected to happen — the result you were trying to achieve.
- What actually happened — the error message, crash, or unexpected behaviour observed.
- Steps to reproduce — a numbered sequence of actions that reliably triggers the bug.
Submitting a Feature Request
We welcome community-driven tool suggestions. To give your request the best chance of being implemented, please describe:
- The document or file type you want to work with (PDF, DOCX, image, etc.).
- The specific operation you want to perform, such as removing blank pages or OCR for Urdu text.
- Your use case — why you need this feature and how frequently you would use it.
- Whether a client-side, zero-upload implementation is important to your workflow.
Support Scope & Response Times
Acknowledged within 24 business hours. Critical crashes patched within 48 to 72 hours of reproduction confirmation.
Logged and reviewed monthly. Popular requests with strong use cases are prioritised for upcoming releases.
Email security@localdoc.org directly. We follow responsible disclosure and respond within 12 hours.
Check our FAQ page first — most common questions are answered there in detail.
Privacy Note: All contact messages are handled privately by the LocalDoc team. We never share your email address or inquiry details with third parties. Please do not attach sensitive documents to support emails.